getText Error formatting internationalized string

[StefanL]

Hi,

has anyone a tip, what the cause of the following error might be?

2011-07-27 11:06:33,301 ERROR [http-80-15] [confluence.util.i18n.I18NBean] getText Error formatting internationalized string with key: "net.customware.confluence.plugin.linking.incoming-links.param.separator.desc" and params: null
– referer: http://xyz.de/pages/viewpage.action?pageId=32636933&replyToComment=32800771&#comment-32800771 | url: /plugins/macrobrowser/browse-macros.action | userName: xxx | action: browse-macros
2011-07-27 11:06:33,363 ERROR [http-80-15] [confluence.util.i18n.I18NBean] getText Error formatting internationalized string with key: "net.customware.confluence.plugin.linking.orphaned-links.param.separator.desc" and params: null
– referer: http://xyz.de/pages/viewpage.action?pageId=32636933&replyToComment=32800771&#comment-32800771 | url: /plugins/macrobrowser/browse-macros.action | userName: xxx | action: browse-macros

Regrads,

Stefan

[Adam Laskowski · Accepted solution]

This is more of a general approach to working with plugins that are throwing errors in the logs and not specific to the Linking Plugin, but here goes!

First, check that your plugin is compatible with your current version of Confluence. You can find the Plugin version by going to Browse >> Confluence Admin >> Plugins. If you are using the Universal Plugin Manager (bundled in Confluence 3.4+), you can use the Upgrade tab to determine this in the Plugins view. If not, check out the compatibility matrix here.

If your plugin is up to date and still throwing errors, try removing the persistent plugin cache directories from the Confluence home folder (will require a shutdown of the instance):

• <confluence-home>/plugin-cache
• <confluence-home>/plugins-osgi-cache
• <confluence-home>/plugins-temp
• <confluence-home>/bundled-plugins
• <confluence-home>/bundled-plugins_language

Restart your instance and see if the issue persists when you use the Macro Browser. If so, you will want to follow Sergey's advice and contact CustomWare.

[Sergey Markovich]

Looks to me like an issue with CustomWare's plugin.

You can contact their customer support at http://www.customware.net/contact-us.html or probably they'll find your question here and answer.