Support » Fixing WordPress » Adding Class to Post Template in Query Loop Block

  • Hi. I tried adding a class in the Advanced settings of a Post Template part of a Query Loop Block. I expected the class to be added to each individual post item (li.wp-block-post). But it was added to the parent UL container instead (ul.wp-block-post-template).

    – Is there any way to attach class(es) to the individual .wp-block-post list (LI) elements instead of the parent UL?

    – Super Bonus: I might ultimately need an additional iterative class added to each post item (e.g, .class-01, .class-02, .class-03, etc.). Any direction here would be most helpful.


    • This topic was modified 3 months, 2 weeks ago by t-p. Reason: Moved to Fixing WordPress from Developing with WordPress
Viewing 3 replies - 1 through 3 (of 3 total)
  • No, unfortunately that is not possible either. You could only develop something like that in a separate Gutenberg block.

    What is your goal of the whole thing?

    Thread Starter KennyLL


    Hmm, bummer. The goal is to animate those individual post items – maybe have them fade in one-at-a-time or something. For the CSS/JS solution we’re using, we need specific class(es) on the element that needs to be animated.

    I’m not sure we would want to re-engineer the entire Query Loop Block just for something like this.

    – Would I need to develop a javascript method of attaching the classes to those elements or something?

    You can also use hooks in Gutenberg to change blocks. It is not necessary to develop everything from scratch.

    If you want to give all query loops an additional class in general, the hook blocks.getSaveContent.extraProps should be sufficient. Minimal example, untested:

    const enableBlocks = [
    import classnames from 'classnames';
    const addClassToQueryLoop = ( extraProps, blockType, attributes ) => {
        // Do nothing if it's another block than our defined ones.
        if ( !enableBlocks .includes( ) ) {
            return extraProps;
        return extraProps.className = classnames(extraProps.className, 'your-extra-class');

    Alternatively, you can of course specify that each editor should enter this class manually in the CSS Classes field under Extras.

    If you do not want to add this class to every QueryLoop, you would have to add a tick. This would have to be added as an attribute to the query loop via the hook blocks.registerBlockType. And as a field via Hook editor.BlockListBlock. Examples can be found in the manual:

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.