Archived topic
Post listing - Getting CSS associated with orginal block post CSS
9 replies · Started by Marc on January 16, 2023
Hello,
I am trying to get a list of custom post type entries in a page, with for each the main image and the content of the post.
I tried using GB Query Loop Block, and a custom PHP function with a shortcode.
Both are working, except the CSS associated with the blocks i used in the blocks of the custom post content. (for exemple, here is the listing page http://psychomotricite.legraindeweb.com/publications/, but the text "Las salas de psicomotricidad, su importancia ..." has no css, when it does on its page : http://psychomotricite.legraindeweb.com/publication/psicomotricidad/ )
Is there a way to get the css associated with blocks of a post (with post Id for example) ? Or maybe to load all CSS from all GB elements at once on every page, even if it is less efficient ?
Let me know if it is clear, and thanks in advance for your response (and maybe this question should be more a GB related question, i can move it if it is)
Thanks
Marc
Hi there,
does the query loop container a Post Content ( core ) block ?
Hi !
Yes it does. I haven't found any other block to grab content in that loop, is there ?
I am going to run this past Tom to see whats possible, as i am not sure it is ...
Thanks
We have marked this as a bug, so at this time its not possible to get the CSS to auto render.
The only "manual" solution i can think of would be to use GB Pro to create Global Styles and apply those on the single post. Then use the developers tools to copy out the global styles and load them across the site.
Thanks for the feedback.
Marked as bug, it means this could be working in a future version ? That would be fixed via GB Pro ?
Indeed it works fine with Global Style, thanks for suggesting it. I will think now on what is easier for the users.
Marked as bug, it means this could be working in a future version ? That would be fixed via GB Pro ?
Yeah, its definitely something we want to fix, and ideally in the free version if possible.
Ok thanks.
So last question, is there a way to follow the status of this 'bug' ? To let me know if it get solved.
For sure, you can track it in our github issues: