The upload directory and its contents is not discussed in this process, however I've found it can just be dropped in over the top of the newly created directory. This is the correct way? -- Scott 20-Jan-2008
- Hi Scott - there were numerous bug reports about image failures that were all due to configuration issues, so the /upload/ directory was added to installs so that the setup process could default all values for the upload settings, and only those users who had a reason to use a different directory would need to change things. Hope that makes sense. -- Ryan 19-Jan-2008 23:28 PST
- Well I was really referring to the process of migrating your previously uploaded file(s), because they would've been deleted in accordance with the upgrade instructions. I thought that perhaps something might be needed in the instructions, perhaps at or after step 7. -- Scott 20-Jan-2008
- Good point. You're right, the upgrade instructions need to be updated to mention that if you're using /upload/ to store files that you should back up that directory prior to upgrading and restore it after the upgrade is complete. Thanks for catching that. -- Ryan 20-Jan-2008 07:48 PST
- No problem. Glad I could help. -- Scott 20-Jan-2008 15:07 PST
The content of StyleSheet is set to a new default version during ugrade. Probably this should be noted in the upgrade instructions as well because in my case the creation of a new stylesheet with our changes and the upgrade changes merged in was the most time consuming part. --HB 05-Mar-2008 04:34 PST
- Thanks, I'll add a note. My hope is that in a future version the system stylesheet can be split from the customizable stylesheet so that user changes won't automatically be overwritten - that's been on the to-do list for a while, so hopefully it will get done during one of the next several releases. -- Ryan 05-Mar-2008 07:17 PST
- I our case an 'automatic' upgrade might be difficult, beause we also modified the 'system' part of the stylesheet to get different logos for our different virtual wikis and some other things (example). --HB 05-Mar-2008 08:03 PST
Archived from the Feedback page:
JAMWiki 0.6.3 beta 1
Here's the first beta for 0.6.3 - there isn't a lot pending for the final release, so barring surprises a final release might be ready soon. This release mostly contains minor bug fixes as well as a host of new and updated translations:
- Upgrade to Spring Framework 2.5.
- Fix a CSS issue that hid diffs from IE6 browsers.
- Use correct virtual wiki when forcing login from a non "en" virtual wiki.
- ...and more.
I realize that there are some outstanding requests and bug reports, but at this point there are enough worthwhile fixes queued that it seems to make sense to push a release. With the holidays approaching I'm not sure whether that release will happen before the end of the year, but barring surprises it shouldn't take more than two weeks to go through some final testing and get everything packaged and documented. As always, testing and bug reports are much appreciated. -- Ryan 21-Dec-2007 21:39 PST
- Again, I should learn never to predict release dates. There was a MySQL issue that I was worried about, but it doesn't seem to be easily reproducible so barring further surprises the 0.6.3 release will probably happen this weekend. -- Ryan 08-Jan-2008 22:09 PST