Loading Profile...
Scaffhold failure on 2.10.3
We just upgraded our wiki to 2.10.3 after testing on a secondary box. When we got to edit any pages using the macro "Livetemplate" we are dumped into the core wiki mark-up where the call to the template is. The scaffhold data displays correctly on the page before hitting edit. After dropping into edit mode, if you hit cancel the browser locks-up and the only recourse is to use the back button to go back to a stable page view. If you hit "save" you get a wiki error message that says the page does not exist. This is a major problem as we depend highly on scaffhold pages. using the preview tab while in editing mode also correctly displays all the scaffhold data.
I’m very very concerned
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company has acknowledged this problem.
-
Inappropriate?Hi Robert,
We logged this one already during our testing and are looking at to twhat the underlying cause/change is.
http://getsatisfaction.com/customware...
regards,
-Rob -
-
Inappropriate?My best estimate is a week at this stage. We also just upgraded our website (http://www.customware.net) to 2.10.3 to assist with the testing
I’m determined
-
Inappropriate?Hi,
We are in the progress of upgrading confluence verison 2.6 to 2.10.3. We have used conveyor library in couple of our custom plugins .
In 2.10.3 we are facing the below error in any one of the custom plugin including scaffolding plugin whenever we starting the server.
There was a problem loading the module descriptor: org.randombits.confluence.conveyor.ConveyorListener.
java.lang.IllegalStateException: Bundle is uninstalled
After reinstalling the affected plugin then everything looks good until next restart. Sometimes the conveyor used plugins get into disabled mode after restarting.
We have tried all the options mentioned in this topic above. Still the issue exists.. Could anyone help on this issue?1 Comment
Add a comment
This solves the problem
-
I'm not sure what the specific problem would be. Have you checked the server logs to see if there is a more detailed stack trace? You may need to turn on the 'atlassian-confluence.log' by uncommenting some settings in WEB-INF/classes/log4j.properties' and restarting the server.
EMPLOYEE
