Annual Documentation Survey

Do you have 4 minutes to help us improve our documentation? Please take our annual survey!

Skip to end of metadata
Go to start of metadata

We're testing Builder 3, and love it so far. Unfortunately we can't seem to get it to recognize our 2x backup file when we upload it. Has anyone else had any problems with this? Regardless of how many we try, we still get the "No 2.0 space theme configs found." message.

  • No labels

7 Comments

  1. Unknown User (gfraser)

    You'll need to copy the /config folder across from your old install, then restart Confluence and try the import. The latest beta includes a much requested feature to automatically associated the imported configs with their spaces.

  2. Unknown User (stephend333)

    I cannot find any documentation that explains the process of exporting and importing layout config files and CSS files between two instances of Confluence and Theme Builder 3.0. Do you have any? Its for a client and I don't want to reinvent the wheel if already done.

    Forgive me if not precisely on topic but close enough I hope you agree (smile)

    1. Unknown User (gfraser)

      If you're using Theme Builder 2.x, just copy the /config folder from old to new instance.

      If you're using Theme Builder 3.x, go to Administration > Theme Administration > Backup Tab - you'll find options there to backup all layouts which can then be imported using the Backup Tab on the new instance.

      We've not got round to documenting theme admin screens yet, however we're in the process of taking on a bunch of new staff to get things moving more swiftly...

      1. Unknown User (stephend333)

        Thanks Guy. Aware of process just wanting the documentation. We'll do and pass on to you when done if you can use - simple step by step process is all really (smile)

        1. It should be noted that there is a bug in 3.0.0 (which I am working on for 3.0.1) whereby it isnt importing the hierarchical structure correctly .. to workaround this, import the layouts then manually rearrange them into the correct structure, then import the layout data a second time.

          1. Unknown User (stephend333)

            Thanks Alain - really useful to know. Just to make 100% sure, the hierarchy you refer to concerns the case where you might have several layouts with some being derived of a parent layout - correct? Also, is it absolutely essential to import the layout data a second time?

            1. Yes it is the structure of the hierarchy that gets messed up ... I have fixed this in 3.0.1 ... if this is proving a problem for you now then create an issue and I will attach a snapshot ahead of the planned release next week.