[All Adaptavist Apps]
Builder 4.0.0 is now generally available, you should use the version on the Downloads page in preference to this prerelease version
Our Early Access Programme (EAP) allows interested parties to try out the latest development releases of Theme Builder, prior to the final stable release. As such, you should not use EAP releases in production environments - they may contain bugs or partially complete functionality.
Builder 4.0.0 removes usage of the problematic ext-js library and adds builder resources and zipped layout backups
Requires confluence 3.1
Upgrading to Builder 4.0.0-M8 or later will cause customised dashboard information to be 'lost', you should use the rebuild tool on the backup tab of builder admin to import the builder 3.x dashboard content to the new layout structure
Don't forget to upgrade to latest Page Information Tools and Content Formatting Macros plugins as those also have new releases for Confluence 3.1.
Builder 4.0.0 is beta grade software, you use it at your own risk
Requires confluence 3.1
Please report any issues that you find to tracker.adaptavist.com
33 Comments
Unknown User (epohl)
What is the target release date for version 3.4?
Unknown User (amoran)
At this time there is no confirmed release date ... rigid schedules == buggy software
Unknown User (epohl)
I realize nothing is rigid or confirmed and won't hold you to it, but are we talking more like December 09 or April 10? I'm having trouble with the builder-favicon macro and Confluence 3 and thought I'd ask before trying to create menu link aliases, which I don't really understand how to do If 3.4 is looking to be released soonish, I don't have to wrestle with the aliases.
Unknown User (amoran)
The extraneous p tags in confluence 3.0 are caused by the changes that atlassian introduced to the way that they interpret the return value of the isInline method on a macro ... in confluence 3.1-m5 atlassian have deprecated this method, which I can only assume means that they are implementing a fix for their ill-advised changes to the renderer in 3.0
To put it more simply the changes to the way that macros behave are caused by issues within confluence not within the macros themselves ... atlassian are working to fix the issues that they introduced in 3.0, and we hope that they will get it right for 3.1!
One workaround is to wrap things in a {span} tag, but that's not nesseacrily workable depending on your content.
Unknown User (hboer1965)
Hi,
encountered an annoying problem with M6, against 3.1-rc1. At the end of loading a page or blogpost, a popup saying A server error has occured is shown.
It only occurs if the {pagetree2} macro is used somewhere on the page/blogpost/panel.
In the logfile, an error stack can be found:
It happens with FF3.5, IE7 and Chrome.
If you need more information, please let me know.
Regards, Herman.
Unknown User (papaya)
Exactly the same happens here - so it seems to be a general issue...
Any ideas for a workaround would be greatly appreciated
If any information (logfiles, system environment etc.) that exceed Herman's posting should be helpful, please let us now.
Best regards.
Unknown User (hboer1965)
Hi Papaya team,
A very basic workaround: I replaced the {pagetree2} macro with {pagetree].
Regards, Herman.
Unknown User (papaya)
Hi Herman,
well, that was quick
Thanks a lot!
Best,
André
p.s.
we opened a ticket for that issue: https://tracker.adaptavist.com/browse/BSUP-2261
Unknown User (amoran)
Thanks for the bug report ... it would be better placed in a forum post, however it will be fixed in the next release.
Unknown User (papaya)
Hi Alain,
just to get this right: "It would be better placed in a forum post" because it's not yet released?
However, thanks a lot, this issue is already fixed with the M7 snapshot of the theme builder.
Best regards from Germany & thanks again...
André
Unknown User (amoran)
What I mean is .. bug reports really belong in their own threads in the forum .. otherwise you end up with pages like the pagetree2 macro which is 98% comments ... this is not useful since it makes it harder to find information.
Much better is to put each thread in it's own page on the forum, that way it is stored in more easily digestible chunks ... it also means that the comments wont get vaped and lost - I don't know if you noticed but I added a 'trim comments' action to builder for this very reason
Unknown User (sshenker)
Any Idea when Version 4 will be ready. We would like to deploy Confluence 3.1 as soon as possible to our test environment prior to deployment to production
Unknown User (amoran)
We are hoping to release builder 4 in Q1 2010
Unknown User (angela_burrows@putnam.com)
How do I get the normal dashboard back? I installed 4.0.0 and it got wiped out, but couldn't get the dashboard to look right, so I uninstalled 4.0.0 and installed 3.3.6, but the dashboard is still empty. I'm running confluence 3.1.
Unknown User (amoran)
3.3.6 is not compatible with confluence 3.1, install 4.0.0-M7 or earlier and follow the instructions in the red box at the top of this page - 4.0.0-M9 contains a rebuild that will do this for you.
Unknown User (angela_burrows@putnam.com)
I followed those instructions, the issue is, I don't want to use a theme builder theme on the dashboard. I'd like it to be the default Confluence Theme. Is there a way to get it back?
Unknown User (amoran)
Set the global theme to be the default theme, and then use the builder theme in those spaces that you want to be builder themed.
http://confluence.atlassian.com/display/DOC/Themes+Overview
Unknown User (sbpe)
Hi Alain
I have similar problems in my Confluence 3.1 (after upgrading from 3.0.2 to 3.1) Somewhere up here it is stated "Builder 4.0.0 is beta grade software"
When do you release builder 4 to Confluence 3.1 ??
Unknown User (amoran)
When it's ready
We have no set date for release, we expect that it will be some time during Q1 2010.
Unknown User (conflman)
Hi,
I think I have found another issue:
The historyfunction isn´t working. I am using this code in a panel:
Cheers and a nice weekend
Unknown User (gina.fevrier@numarasoftware.com)
We have a 30-day trial for Confluence 3.1. I manually installed Theme Builder 4.0.0-M10 to Confluence. But none of the themes showed up – just the Default. I uninstalled it, then installed 4.0.0-M5. But that didn't work either.
Is there a way to get a trial of Theme Builder, and which version should I install? There were links to a License FAQs on your site, but the links were broken.
Thanks.
Unknown User (amoran)
Builder is FREE, however it doesn't include any pre-made themes, you need to use your own creativity for that!
Now that 4.0 allows users to create layouts that include image elements we hope to see some submissions of sample layouts from the community, eventually leading to a layout repository similar in concept to the Atlassian plugin repository.
If you can tell us where you found links to the license faq's then we will remove them since builder is no longer a paid-for product.
Unknown User (gina.fevrier@numarasoftware.com)
Alain,
Thanks for the super-fast response! Here's one of the broken links for Licensing FAQs: http://www.adaptavist.com/display/Builder/Downloads
I'll install 4.0 again and try to create a theme. I hope I can find some sample themes as well.
Gina
Unknown User (c.aliaga@cgiar.org)
We have a trouble with the macro - page-info:title - with the Confluence V 4.0.0-RC1
Does anybody know the workaround or solution ?
Error formatting macro: page-info: java.lang.NoSuchMethodError: com.atlassian.confluence.core.ContentEntityObject.getRealTitle()Ljava/lang/String;
Thanks.
Christian
Unknown User (o.palomino@cgiar.org)
I have the same problem with the macro: page-info:title. I have installed the last version to Adaptavist Theme Builder 4.0.0-RC1 but the problem isn't solved.
Error formatting macro: page-info: java.lang.NoSuchMethodError: com.atlassian.confluence.core.ContentEntityObject.getRealTitle()Ljava/lang/String;
Thanks for your support.
Omar
Unknown User (gfraser)
The page info macro is from Page Information Tools plugin, not Theme Builder. Please upgrade to latest Page Information Tools plugin.
Unknown User (nhsoft.yhw@gmail.com)
Page Information Tools plugin's version is 1.3 - Stable
confluence version is 3.1
theme builder version is 3.3.6-conf28
but from confluence log files, i found the error exist
Caused by: java.lang.NoSuchMethodError: com.atlassian.confluence.core.ContentEntityObject.getRealTitle()Ljava/lang/String;
at com.adaptavist.confluence.builder.BuilderVelocityHelper.getOpenSearchTitle(BuilderVelocityHelper.java:730)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke(UberspectImpl.java:389)
at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:378)
at com.atlassian.confluence.velocity.introspection.UnboxingMethod.invoke(UnboxingMethod.java:31)
at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:270)
... 114 more
Unknown User (o.palomino@cgiar.org)
Dear Guy,
Thanks for your reply. I have installed the plugin v 1.3 and the problem with the macro page-info:title is solved.
The plugin is in: http://www.adaptavist.com/display/AtlassianConfluence/Page+Information+Tools+Plugin
Regards,
Omar
Unknown User (kichap)
I installed themebuilder 4.0 in confluence 3.1, created a space and applied the theme created in themebuilder 4.0.
But after applying the theme and then navigating to the homepage of the space, I am logged out of confluence. Disabled compatibility macros,
installed content formatting plugin, Page information plugin. Do I have to install any other plugin along with themebuilder 4.0
so that I don't have to face this problem.
Unknown User (amoran)
It is highly unlikely that builder will cause authentication issues, I would suggest that you need to be looking at your logs to find out what's going wrong with your auth, and that the timing of this problem is purely coincidental.
Unknown User (macandron)
What about the new Move Dialog and Permissions Dialog? I created aliases for them but activating the Move link just refreshes the page and activating the Permissions link drops me onto the Page Information page. How am I supposed to use these functions? Have they been taken into account in RC2?
BR,
Jonas
Unknown User (amoran)
The problem will be being caused by the way that the jQuery enhancements are applied to the links being incompatible with the hmenu library, you should be able to get the links to work if you apply them directly to the panel.
We intend on replacing hmenu in a future release however we need to get 4.0 out there ASAP since at the moment there is nothing available for people using confluence 3.1
Unknown User (macandron)
Hmm... I'm not sure I understood you. I tried taking the links out of the {menubar} and placing them directly in the page title panel. The code looked like this:
I also tried changing the compound-menuitem to a menulink, to no avail. The code looked like this:
But the behavior of the links stayed the same. Did I do something wrong?