|
|
History
| Log In
|
|
|
|
Yeah, it's on our radar. I haven't had time to determine how much is broken yet. I know that it doesn't work with the new default theme. Not sure if there are other issues also...
We are had to revert back to 2.7 because the Scaffolding macros stopped working -we were using the new default screen.
we are using Plugin Version: 2.7-dr9 thanks Joseph Hi all,
When I export a page in PDF in 2.8, the layout of the page is different than a page exported in PDF in 2.7 (espacially the panel and table-data which are marcos of scaffolding)... Do you know if it's because scaffolding is not yet compatible with the version 2.8? Thanks a lot. Cheers, I'm not certain, however if it is purely layout and not error messages, I would guess that it's due to changes in Confluence. Is the layout different for pages which do not have Scaffolding data in them also? If it's something which seems to be Scaffolding-specific, it's probably worth creating a specific issue for the problem, and attaching some screenshots as well for reference.
Well, I've sort of worked around the 2.8 compatibility issues.
First, when I discovered that the editscaffold action was missing, I uninstalled, intending to reinstall, which I've found often gets things registered properly. Uninstall went smoothly, but then there was no more Scaffolding Plugin listed in the plugin repository. It seems Atlassian has heard my complaints about incompatible plugins in this case (but the Attachment Checkout Plugin remains!). So I poked around, found this Jira issue, voted and watched it.... Then I went and manually uploaded the latest version again. Now the editscaffold action reappeared! But the page is Real Ugly, with lots of leftover cruft that doesn't belong – like the wiki markup info panel making the whole "edit this page name" line takeup half the screen. My solution: Add a little user macro which supplies JavaScript which hides the offending cruft. I'm still incrementally removing cruft, but it's to a point it appears to be usable – so we (narrowly) avoided having to revert back to 2.7. Here's my initial cut at a {fix-scaffold} macro; I'll try to get back to post a more complete solution later: <script type='text/javascript'> (no body, HTML output, of course). That'll suppress it when you're in "Edit Layout" mode, but I'm nearly always editing a live template there... but I can probably fix that up. (These live templates are where I'm sticking this user macro...) There's a couple of javascript errors on the page, but they don't seem to interfere with function, at least not in any essential way. David,
Is there any expected time frame that you have targeted for the compatibility update with 2.8? Our very large Enterprise implementation of Confluence heavily relies on Scaffolding but we need to get to 2.8 so we can work through some serious scalability problems. Current Scaffolding experience at 2.7.3 1. Page with Scaffolding takes 43 sec to load 1 out of 3 time (<4 sec the other two) and cache is cleared at the browser level between each test 2. Same page takes 25 sec to Save after an 'Edit' (no data changed)....1 out of 3 time (1.5-2 sec the other two) and cache is cleared at the browser level between each test Thanks...and we do love the function of Scaffolding Ben Bob Kern's "patch" above works really well. I created a {fix-scaffold} macro and reference it in the top of all my scaffold temples.
I've noticed that whenever I access the scaffold template directly, I get an "undefined page" created by "Anonymous" in the root of my space. I get a new "undefined page" whether I save changes or cancel changes to the template. This seems to be unique to scaffold because other templates don't exhibit this behavior. Is anyone else noticing this? Has there been any activity on fixing this? I've a client for whom this would be a very useful plugin, but the same client wants Confluence 2.8. If this needs somebody to work on it, I might be able to lend a hand.
The fix version 2.7-dr9 is available for download already (http://www.customware.net/repository/download/attachments/2095/scaffolding-plugin-2.7-dr9.jar
 ), but I guess it's not fixed there, is it? I'm not certain why 2.7-dr9 was specified as the fix version - Confluence 2.8 came out after dr9's release, and has not yet been fixed. We are working on Scaffolding at the moment, but, as always, it has to fit in between other projects. As such, no firm ETA is available yet.
David,
What's your estimate for complexity of this task according to your experience and above mentioned issues? And another one question: Do you plan to make Scaffold compatible with Confluence 2.8 when Confluence 2.9+ will be released? Thanks! In developer time, it's probably about a week's work, but that's primarily because I'm also working on other plumbing stuff underneath. Each release of Scaffolding tends to be a couple of months apart, so I try to get as much into each one while as I can while work's being done. Otherwise, it lies fallow while other overdue plugins get attention... As for an ETA, I can make no guarantees...
That said, if someone wants to do a quick hack of the current release to get it working as is in 2.8, go right ahead. That would be a much shorter task, but I can't spend the time on it right now personally. I'd suggest creating a branch of the current tag version, rather than working on the trunk, since I'm screwing around in there fairly seriously at present... If someone puts their hand up I'm happy to set it up and check the release when its done. And to answer your other question, yes, 2.8 will be supported. I'm hoping that the other changes I'm working on will make it easier to make transitions between Confluence versions in the future, even with Atlassian changing their theme majorly three releases in a row... David ....Thanks very much...greatly appreciated
Cool. Will that new version work with Confluence 2.9 too, or is further work needed for that?
Thanks, David!
Could you please announce release date for that sweet 3.0.0 version? Looking forward to trying this update... thank you very much!! Very helpful!
Great
 Looking forward to try it out. The release of 3.0.0 cannot be too far away, when all issues in this release have been fixed, right? 3.0.0 will not support Confluence 2.9, unfortunately - that is scheduled for 3.1.0. 3.0.0 should be out on Monday, assuming there are no more late-breaking critical bugs.
|
||||||||||||||||||||||||||||||||||||||||||||
 |
|
Task
Resolved
Major
Confluence 2.8 compatibility
I just figured I'd make a 2.8 version off your existing, fixed Confluence 2.7 compatibility task.
While I have not personally tried it, I'm told by http://jira.atlassian.com/browse/CONF-11513