[#SCAFF-250] {set-data} causes read-only exception - Adaptavist Public Issue Tracker

Confluence Extension: Scaffolding Plugin

{set-data} causes read-only exception

Created: 10/Sep/08 02:16 PM Updated: 12/Sep/08 06:42 AM

Component/s:

{set-data}

Affects Version/s:

3.0.0

Fix Version/s:

3.0.1

Time Tracking:

Not Specified

Environment:

Confluence 2.8.0, Scaffold 3.0.0, Java 1.5

Description

« Hide

I'm using Scaffold 3.0.0 - I copied a scaffold template from one space to another, then I moved some pages that reference a scaffold using live-template to the new space. The pages use set-data elements on the top, and the live-template on the bottom for user input.

The set-data elements are returning the following error:

Error formatting macro: set-data: java.lang.UnsupportedOperationException: This storage object is read-only

This error is followed by the actual value stored by set-data.

All

Comments

Work Log

Change History

Sort Order:

[ Permalink | « Hide ]

Stephen Morad added a comment - 10/Sep/08 02:24 PM

Actually, it appears that {set-data} causes this error to be generated anywhere it is used (even in the space where it used to be working), so set-data must be broken in 3.0.0.

[ Permalink | « Hide ]

David Peterson added a comment - 11/Sep/08 12:48 AM

I've set this to be looked at for 3.0.1. Could you please post your {set-data} markup so I can confirm? Thanks.

[ Permalink | « Hide ]

Kevin Menzies added a comment - 11/Sep/08 07:08 AM

we experience the error with very simple markup i.e. {set-data:RMType|hidden=true}Service Component{set-data}

Refreshing the page will sometimes resolve the error and then other times cause the error (I haven't recognised a pattern to this)

Confluence 2.9.0, Scaffold 3.0.0, Java 1.5.0

Note that I haven't been able to reproduce on a different Confluence 2.9.1, Scaffold 3.0.0, Java 1.5.0_05 environment.

[ Permalink | « Hide ]

David Peterson added a comment - 11/Sep/08 08:11 AM

Hmm. Ok, Scaffolding isn't tested on Confluence 2.9 at all, although your original report said you were using Confluence 2.8, so there's probably something screwy in how it's being saved. I have an idea what is probably causing the problem, but I'll have to track down the actual spot where it's happening.

[ Permalink | « Hide ]

Stephen Morad added a comment - 11/Sep/08 01:49 PM

Actually, I'm the one using this on Confluence 2.8.0. My markup is also as simple as it gets:

{set-data:Variable}Value of Variable{set-data}

Thanks for changing the summary. I assumed the problem was related to moving a page, but relaized after creating the bug report that it was happening everywhere, even on newly created pages.

[ Permalink | « Hide ]

David Peterson added a comment - 12/Sep/08 06:42 AM

This has been fixed in the next release.