Page History

If you're using MySQL database, you may encounter the following issue:

Code Block

java.lang.RuntimeException: There was a problem evicting or flushing a PluginData object at com.atlassian.confluence.plugin.persistence.hibernate.HibernatePluginDataDao.saveOrUpdate(HibernatePluginDataDao.java:65) caused by: net.sf.hibernate.exception.GenericJDBCException: could not insert: com.atlassian.confluence.plugin.persistence.PluginData#3375106 at net.sf.hibernate.exception.ErrorCodeConverter.handledNonSpecificException(ErrorCodeConverter.java:90) caused by: com.mysql.jdbc.PacketTooBigException: Packet for query is too large (3063507 > 1048576). You can change this value on the server by setting the max_allowed_packet' variable. at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:2691)

To resolve this issue, simply increase the max_allowed_packet setting in your MySQL config to 4M using the command line shell as follows:

Code Block
shell> mysql --max_allowed_packet=4M

See Also: PacketTooBigException.

In Theme Builder 3.0 and above, a new feature adds pop-up access key hints at the top of the page. In normal use, these hints will not been seen however there are a couple of things that cause them to be displayed...

If you have disabled CSS or are using a browser which does not support CSS, the links will always be shown - this is expected behaviour and is required for compliance with accessibility laws throughout Europe and other parts of the world.

If you have disabled the "Builder Default CSS" option in the CSS Tab, you will need to add some "Custom CSS" to make the hints work properly as follows:

Code Block
#accessKeys { margin: 0; padding: 0; } #accessKeys dt { margin: 0; padding: 0; position: absolute; top: -9999px; left: 0; } #accessKeys dd { margin: 0; padding: 0; } #accessKeys dd a { position: absolute; top: -9999px; left: 0; } #accessKeys dd a:focus, #accessKeys dd a:active { background-color: #3556a2; color: #fff; top: 0; font-size: 1.2em; padding: .5em; }

For more information on the Access Keys feature, see the related blog post.

Many Confluence macros are developed for use only on wiki pages and blog posts. However, Theme Builder allows you to use macros within the theme layout in which case they get rendered throughout the entire space causing errors to appear when those macros find themselves in unexpected places.

To solve this issue, use the builder-show macro, for example:

Code Block
{builder-show:context=page,blogpost} ... your macros here ... {builder-show}

That will only show the macros when you are viewing a wiki page or blog post, and hide them everywhere else preventing the errors from appearing.

This issue affects Confluence 2.7.1 and above. To solve, add the following to the custom CSS for your layout

Code Block
.hidden { display: none; }

Reason:
Confluence 2.7.1 and onwards uses an external attachments.js rather than inline javascript, the older inline code modified the display property of the <TR>'s class directly. The new code in the external file adds another class, "hidden", to the <TR>. This class is not defined by confluence inline or in any CSS files, this issue also affects the default confluence theme, and is not caused by Theme Builder.

Atlassian changed the structure of tabs in Confluence 2.6.0 and above - if you're still using Builder 2.x then there are two options to solve this:

The easiest option is to upgrade to Builder 3.0 or above which has more dynamic support for changes to Confluence and it's style sheets.

Note: If your link properties window is distorted, you should first upgrade to Confluence 2.6.2 which fixes several bugs found in Confluence 2.6.0 and 2.6.1.

If you want to continue using Builder 2.0.x, you can add the following CSS to the bottom of the "Custom CSS" setting in Theme Configuration:

Code Block

/**** 2.6 tabs ****/ .tabnav, .comment .tabnav { border-bottom:1px solid #3C78B5; display:inline; float:left; font-size:10pt; font-weight:bold; list-style-position:outside; margin:0pt; padding:0pt; width:100%; } .after-tabnav { clear:both; } .tabnav li.tabs { display:block; float:left; list-style-image:none; list-style-position:outside; list-style-type:none; margin:0pt 0pt -1px 10px; } .tabnav .tabs a { background:#3C78B5 none repeat scroll 0%; border-color:#3C78B5 rgb(60, 120, 181) -moz-use-text-color; border-style:solid solid none; border-width:1px 1px medium; display:block; float:left; margin:5px 0pt 0pt 3px; padding:5px 5px 4px; text-decoration:none; } .tabnav .tabs a:link, .tabnav .tabs a:visited { color:#FFFFFF; } .tabnav .tabs a:hover { background:#003366 none repeat scroll 0%; border-color:#003366; color:#FFFFFF; } .tabnav .tabs a.current { background:white none repeat scroll 0%; border-bottom:1px solid white; color:black; } .tabnav .tabs a.current:link, .tabnav .tabs a.current:visited { color:black; } .tabnav .tabs a.current:hover { background:white none repeat scroll 0%; border-bottom:1px solid white; color:black; } .tabnav .spaceActionLinks { display:block; float:right; margin:0pt; } .tabnav .spaceActionLinks a { border:0pt none; display:inline; float:left; font-weight:normal; margin:1px 3px; padding:8px 5px 3px; text-decoration:none; white-space:nowrap; } .tabnav .spaceActionLinks a span { text-decoration:underline; } .tabnav .spaceActionLinks a:link { color:#003366; } .tabnav .spaceActionLinks a:visited { color:#003366; } .tabnav .spaceActionLinks a.current { color:black; } .tabnav .spaceActionLinks a.current span { text-decoration:none; } .tabnav .spaceActionLinks a.current:link { color:black; } .tabnav .spaceActionLinks a.current:visited { color:black; } .tabnav .nontabs { display:block; float:left; margin:5px 0pt 0pt 3px; padding:0pt; } .tabnav #markupTab, .tabnav #wysiwygTab, .tabnav .tabs #previewTab { font-size:9pt; font-weight:normal; margin:8px 0pt 0pt 3px; padding:3px 5px 2px; } .tabnav #spacesLabel { float:left; margin-top:5px; padding:4px 6px; } .tabnav-box { border-bottom:1px solid #3C78B5; border-left:1px solid #3C78B5; border-right:1px solid #3C78B5; padding:8px; }