Blog

  • 2024
  • 2023
  • 2022
  • 2021
  • 2020
  • 2019
  • 2018
  • 2017
  • 2016
  • 2015
  • 2014
  • 2013
  • 2012




Fixed with Confluence 6.14.1!

 

The issue CONFSERVER-52504 has been fixed with version 6.14.1 of Confluence.

The Problem

Happen to see this message as a response to your request to save a Confluence page?

An error occurred while trying to save the requested page.r

And this in the log on the server?

com.mysql.jdbc.MysqlDataTruncation:
Data truncation: Data too long for column 'STRINGVAL' at row 1


Not being able to save a page is quite annoying.

Serenity now! (wink)

A Cause

You may have hit CONFSERVER-52504 where the number and order of the macros on your page hits the magic number to prevent Confluence from saving your page.

This is an issue for pages with a larger number of macros. Since the projectdoc Toolbox provides blueprints that already employ a large number of macros, chances are that you hit this problem sooner.

A Workaround

Unfortunately the issues is rated with severity minor. So there is a good chance for this problem to not go away any time soon.

What you need to do to get your page saved is changing the number and order of your macros. Note that for the calculation that produces the issue the occurrence number of the same macro is not important. Each type of macro is only considered once. What counts is the length of the macro name and its position in the list of macros of this page. So you need to adjust the name and position to work around the problem.

What often works for me is adding the Cheese Macro (since this is typically not already on the page) within a macro that hides it (since I do not want to have the cheese macro rendered on my page).





Link

Link

Posts

  • No labels