OpenEdit User ForumWelcome to the OpenEdit User Forum. Whether you are newbie or a seasoned expert, the OpenEdit User Forum is our virtual water cooler where we commune to share ideas and publish information about new and existing features. We also make regular posts to our blog. You must be registered and logged in to post a new comment or topic. If you require dedicated support to your OpenEdit project, please visit our Web Site & Application Maintenance page for access to our online issue tracker. Ask. Answer. Enjoy. Upgrade Woes...I clicked the "Ok" button today to upgrade the OpenEdit editor and I now get this when attempting to login:
Posted by James Carman Wed, Jun 25 2008 8:47 AM
|
Most Recent Posts
Adding custom properties to Users/Groups
(1 comments)
Versions
(3 comments)
OE Toolbar - Upload New File
(2 comments)
Latested stable build
(1 comments)
How much RAM does one instance of openedit requires?
(4 comments)
Save Permissions link not working
(1 comments)
Bug in Spring plugin.xml sorting
(0 comments)
Translations Dropdown
(1 comments)
Could not find bean named Search
(4 comments)
Creating Objects with Velocity
(2 comments) Archive
Log in
Syndicate:
|
||||||||||||||||||||
Copyright 2008 OpenEdit Inc. All rights reserved. last modified: Jun 25 2008

Did the webapp reload ok? Make sure it reloaded. If that does not fix it please list your jar files in WEB-INF/lib/
The webapp is running (www.tmmaa.com). I just can't login to do edits/maintenance.
Thats odd. Looks like your users are missing. Make sure there is a good /WEB-INF/users/* folder.
What about the "Could not find bean named TabModule"? Should I maybe have upgraded "core" first?
The users directory looks okay to me:
-rw-r--r-- 1 root root 535 2007-10-28 13:02 cathy.carman.xml
-rw-r--r-- 1 root root 532 2008-03-27 16:24 jim.carman.xml
-rw-r--r-- 1 root root 404 2008-03-21 13:52 kurt.streutker.xml
-rw-r--r-- 1 root root 397 2007-10-29 17:13 ryan.petrie.xml
-rw-r--r-- 1 root root 539 2007-10-29 08:59 steve.napier.xml
Oh ok.
The editor upgrade will automatically upgrade the core as well.
Did you restart the web site after the upgrade? Make sure Tomcat really does stop when you stop it.
Make sure there are no duplicate JARs as well - that could cause this if it's loading an older jar from the lib dir. This is a common problem on windows boxes.