-
Posts
-
Hi,
I’d like to be able to select specific products to display in blogposts without having to make categories for it every time. The same would be awesome for the masonry element this would be a really dope function so you could insert related articles nicely into posts and pagesI posted it here because the Feature Request page has been out of commision for over a year I guess? :-P
Hey joax,
Sorry for the very late reply and thanks for your request, so I understand further, are you displaying a “product grid” element in a “post” type?
Are you using the Advanced Layout Builder for “post” types, or are you using the ALB shortcodes in a “post” type?
Is this like you have a blog post and you would display a product in it, such as a “related” product or a “spotlight” product?
Will these be changed often or will each post be set with a product once?
Do you have any mockups?As for using the masonry as a “related articles” container, the built-in related posts element uses the post “tags” to determine the related posts, the masonry element also lets you choose posts by the tag, so this would be the solution.
I imagine that you are using the masonry at the bottom of a post, showing perhaps 3 items that are “related”, am I understanding correctly?
Do you have any mockups?Best regards,
MikeHa.. my reaction is even sloooower.. man…
What I mean is that I would like the possibility to select 1 (or more) specific products or posts.. let’s say I have a book publishing company and I write a blog article with a bit of background on the book and the author and I want to insert that specific book into the blogpost.. Now I can do that by creating a tag or category for that purpose only and select that one as I insert the product grid (or masonry element) in the blogpost.. but it’s not very neat :-P and the taxonomies become very polluted if I’d make that a daily practice :-P can’t imagine Google liking that very much
Hi,
Thank you for the feedback your explanation helps, I recently helped someone who wanted a specific “highlighted” product in each post which they would manually add via a woocommerce shortcode with a specific product ID, in this thread the direct woocommerce shortcode was a better solution than the ALB shortcode. This sounds like what you are describing.
So specificly, is it the layout of the masonry element, as in what the css is doing, or is it the control of the content that is the appeal of the masonry element in your case?
If it is the control of the content, then the power of the element is in that it can query the database and display a filtered result, based on a relationship, in this case “tags or categories”, but specifying a specific post ID for the element to show seems like it is not using the query and is only a container for the css.I bring this up because I envision the backend of the masonry element with a specific post field to enter multiple IDs to show, but in a broad use of the element these multiple IDs probably belong to a “group” (tags & categories) anyways.
*I understand that you don’t want to use tags or categories, but if a query is used then a relationship would need to be created.So I’m happy to submit a feature request to allow specific item IDs in the masonry element, the main issue I see for the “product” example is that the woocommerce shortcodes does this now, not counting the “layout” (css). Did I miss something else?
Best regards,
MikeSorry I see I didn’t reply anymore.. I probably got distracted while typing my reply ^_^
But You’re correct.. the WC shortcode would work yes but it breaks the style and the ease of use is completely gone.. this would work for me but I woundn’t feel comfortable telling my clients to do this :-P
- You must be logged in to reply to this topic.