It appears that the 'Page' option under 'Selectors' column in v2 custm module field types presents the user with a list of landing pages to select, yet the 'Blog' selector only allows the user to select an entire blog - not an individual post.
for anyone landing here through googling how to add a blog selector: the Page selector field also searches blogs and allows you to add blogs. Now ideally I would love this field to be limited to only search blogs so that you don't end up fetching pages with the blog_by_id function...
Absolutely baffled that this is still an issue. If you have a selector for all website pages and a selector for a blog as a whole, why isn't there a selector for a specific blog post? Definitely needs to go into the pipeline.
You just have to find the blog post id. I would like to know if there is a better way to find this, but if you go to the details page for any page or blog post then look at the url, the second number is the blog post id:
Thanks - but would actually be easier to get them to paste a link rather than getting the user to find an ID. I was hoping to avoid that though - since the blog posts will be HubSpot content it makes sense that the dropdown behave the same way for the user that the Page selector does.
Oct 4, 201812:09 PM - edited May 31, 20195:03 AM
Key Advisor
Blog post selector field - v2 custom modules
I wouldn't know who to ask about that.
If you could dynamically create choice fields then you could loop through the blog posts to create a drop down out of the titles. I used the choice field from the docs and it doesn't give errors, but it also doesn't include the choice field in the module preview so if it does apply it to the page it would be outside the module. Just like the page selector field, the original choice module isn't the same as the custom module's choice field.
Other than that I would say you are left with the text field or blog post id.