[opencms-dev] Open CMS Upgrade to 8.0.2 - Issue

[Dawn Louis]

Hi Michael,

Thanks for the prompt reply and that worked for me.

As you pointed out , I had an older version of the lucene jar in my '/lib'
which was causing the issue. I removed it and the upgrade to 8.0.2 process
was successful.
I checked the 'update.log' in the WEB-INF/logs folder and there are no
errors.

Also I imported the packages that were exported before the upgrade process.
That process was also a success.

However there are a few issues in this upgraded system,

1. I'm getting a page not found when clicking on some of the images and .pdf
files. This issue is happening only in the upgraded system.
Scenario :  I have a file 'safari_logo.gif' inside
'/sites/default/ZA/Documents/Images/' folder. In the 'Offline' view, I'm
able to click on this image and view it. But when the 'Online' view is
selected, I'm getting a page not found exception. The URL being fired is
'http://localhost:8080/export/sites/default/ZA/Documents/Images/star-alliance-logo.jpg'.
Could you please advise as to why the system is searching the file inside
the '/export/sites/default' folder instead of '/sites/default' folder ? Due
to this error, Im not able to refer to any of the images kept inside the CMS
system from my application.

2. In the upgraded CMS system, when I click on the 'help' button, Im getting
some 404 exceptions like,
http://localhost:8080/export/system/modules/org.opencms.workplace.help/jsptemplates/help_body.jsp.html_499178748.html
http://localhost:8080/export/system/modules/org.opencms.workplace.help/resources/search.js
http://localhost:8080/export/system/modules/org.opencms.workplace.help/resources/close.png
All these are pointing to the 'export' folder again. How can we configure
the system so that it takes the resources from the '/system/modules/'
instead of '/export/system/modules' folder ?

3. The login page and the further pages had a broken style. This was
resolved by manually placing all the '.css' files in the
'export\system\workplace\commons\style' folder. Here also, the export folder
comes into play.

Could you please advise as to why this is happening in the upgraded system ?

Regards,
Dawn Louis













Michael Emmerich-2 wrote:
> 
> Dawn,
> 
>> 	I have an application deployed in Jboss 5.1.0, MYSql database with Open
>> CMS
>> 7.5.2.
>> In order to upgrade the application to CMS 8.0.2, I had copied the UPDATE
>> folder and WEB-INF folder(in the opencms_upgrade_to_8.0.2.zip) to the
>> applications root folder.
>> The following are done,
>> 1. Modified the existing opencms.properties file to have the value of
>> wizard.enabled=true.
> 
> Ok, this is correct.
> 
>> 2. The index generation was disabled by removing the entries in
>> cmsupdate.ori file, as was specified in the readme.txt file.
> 
> This will save a lot of time during the upgrade. However, you should not 
> forget to rebuild the search indexed after the update is completed and 
> the system is running again.
> 
>> 3. Deleted the occurrences of the entry
>> "USERPREFERENCES_workplace-generaloptionsuploadapplet at
>> java.lang.Boolean=false" (as mentioned in
>> http://lists.opencms.org/pipermail/opencms-dev/2011q2/035708.html)
> 
> This is not required any more. It was a bug in the Updater of OpenCms 
> 8.0.0, and is fixed now.
> 
> 
>> The servlet container was started and after hitting the URL
>> http://localhost:8080/applicaitonname/update/, the following error is
>> obtained in the update.log inside the WEB-INF folder,
>> java.lang.NoSuchMethodError:
>> org.apache.lucene.analysis.standard.StandardAnalyzer.<init>(Lorg/apache/lucene/util/Version;)V
>> 	at
>> org.opencms.search.CmsSearchManager.getAnalyzer(CmsSearchManager.java:531)
>> 	at
>> org.opencms.search.CmsSearchManager.getAnalyzer(CmsSearchManager.java:751)
>> 	at
>> org.opencms.search.CmsSearchIndex.initialize(CmsSearchIndex.java:1061)
>> 	at
>> org.opencms.search.CmsSearchManager.initSearchIndexes(CmsSearchManager.java:1884)
>> 	at
>> org.opencms.search.CmsSearchManager.initializeIndexes(CmsSearchManager.java:1090)
>> 	at
>> org.opencms.search.CmsSearchManager.initialize(CmsSearchManager.java:1069)
>> 	at org.opencms.main.OpenCmsCore.initConfiguration(OpenCmsCore.java:1223)
>> 	at org.opencms.main.OpenCmsCore.upgradeRunlevel(OpenCmsCore.java:1816)
>> 	at org.opencms.main.CmsShell.<init>(CmsShell.java:447)
>> 	at org.opencms.setup.CmsUpdateThread.run(CmsUpdateThread.java:143)
>> 	${user}@${project}># Turn echo on
>> 	${user}@${project}>java.lang.NullPointerException
>> 	at org.opencms.main.CmsShell.executeCommand(CmsShell.java:760)
>>
>> Could you please advise as to what was done wrong?
> 
> It seems as if your system still accesses the "old" .jar files. The 
> lucene search was updated to a newer version which result in some code 
> changes in OpenCms.
> 
> So check if the old lucene .jar files in your /lib folder are 
> overwritten by versions that have a file size of 334 bytes. Those are 
> "empty" .jar files.
> 
> Best would be if you post a listing of your /lib folder here (ls -la) 
> were the file sizes are shown.
> 
> 
> -- 
> Kind Regards,
> Michael.
> 
> -------------------
> Michael Emmerich
> 
> Alkacon Software GmbH  - The OpenCms Experts
> http://www.alkacon.com - http://www.opencms.org
> 
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://lists.opencms.org/mailman/listinfo/opencms-dev
> 
> 

-- 
View this message in context: http://old.nabble.com/Open-CMS-Upgrade-to-8.0.2---Issue-tp32295544p32310210.html
Sent from the OpenCMS - Dev mailing list archive at Nabble.com.