Skip to end of metadata
Go to start of metadata

Hi, we are upgrading to Confluence 3.02 (No 3.1 because the theme builder is not compatible yet). We are having the builder-spacetitle problem where the macro appears to add <p> tags before and after the title when placed into a page. I read on here that upgrading to Builder 3.3.6 should fix the problem but it has not. we are using the 3.3.6-conf210 release.

Any suggestions for correcting this problem?

Thanks.

Kate

  • No labels

9 Comments

  1. Upgrade to confluence 3.1 which fixes the bug that causes the errant <p> tags ... the problem is in the renderer not in builder.

    Builder 4 supports confluence 3.1.

    1. Unknown User (katerk)

      Well, that's good we wanted to go to 3.1 but Builder 4 wasn't ready. Is Builder 4 now production ready?

      Kate

  2. Unknown User (jlowry)

    Try wrapping the other text in the block in a span macro:

    {span}Some words etc..{span}{builder-spacetitle}{span}More words etc..{span}
    
    1. Unknown User (katerk)

      No, that didn't work. Still getting the extra lines.

      1. Unknown User (jlowry)

        Please could you paste the code you are using in the panel.

        1. Unknown User (katerk)

          It isn't in a panel, just on a page. Does the builder-spacetitle have to be used in a panel now? It has worked fine all along through the 2.X versions we've had.

          Kate

          1. The builder-* macros are intended for use within builder panels ... hence the naming convention, by prefixing these macros with builder- we intend to convey that they should be used within a builder panel.

            If the span trick isn't working for you then you are likely using an outdated version of content formatting, failing that you need to upgrade your confluence to work around the bugs in the wiki-markup renderer.

            1. Unknown User (katerk)

              Thanks, wrapping it in a panel worked. Is Builder 4.0 Production ready? We really want to upgrade to Confluence 3.1 but we need the Builder themes.

              Thanks.

              Kate

              1. That depends on your use-case ... if you are just using builder for theming and not actively editing layouts, or don't mind putting up with layout editing & builder-admin rough edges then you can use builder 4 as it stands.

                If you need end-users (space admins) to be editing layouts in IE then you probably want to wait for the final release.