Hi, Simon, I just ran into the same issue going from 3.0.6 to 3.0.10. I fixed it by re-running SetPermissions.pl script, but instead of targeting /opt/otrs (which, per instructions in UPGRADING is a symoblic link) I targeted the actual directory, /opt/otrs-3.0.10
Voila, things started working. I've opened http://bugs.otrs.org/show_bug.cgi?id=7748 Best, -at P.S. Here are my notes on my upgrade troubles: We just upgraded from 3.0.6 to 3.0.10 using the source tar ball. otrs came up as text only after the upgrade, so I checked the httpd error log and copied over the following after seeing gobs of HTTP 404 not founds: cp -rp /opt/otrs.save.most.recent.backup/var/httpd/htdocs/skins/Agent/default/css-cache/ /opt/otrs/var/httpd/htdocs/skins/Agent/default/css-cache/ cp -rp /opt/otrs.save.most.recent.backup/var/httpd/htdocs/js/js-cache/ /opt/otrs/var/httpd/htdocs/js/js-cache/ cp -rp /opt/otrs.save.most.recent.backup/var/httpd/htdocs/skins/Agent/ivory/css-cache/ /opt/otrs/var/httpd/htdocs/skins/Agent/ivory/css-cache/ Now our OTRS site comes up pretty but still does not work: clicking on the page elements does not do anything, and I do still see some 404 Not Founds in the error log: "GET /otrs-web/js/js-cache/CommonJS_a030e1015ec8f794ebfc487d740ab5ca.js HTTP/1.1" 404 339 "GET /otrs-web/js/js-cache/ModuleJS_5053768fc48162ed00f359bb1510c2ac.js HTTP/1.1" 404 339 "GET /otrs-web/js/js-cache/CommonJS_a030e1015ec8f794ebfc487d740ab5ca.js HTTP/1.1" 404 339 "GET /otrs-web/js/js-cache/ModuleJS_5053768fc48162ed00f359bb1510c2ac.js HTTP/1.1" 404 339 Looks like the web site is not working because I am missing some javascript... and then we noticed files under /opt/otrs did not have the correct permissions. On a hunch, I reran the setpermissions script targeting the /opt/otrs-3.0.10 directory rather than /opt/otrs, and now it works great! Best, -at On Tue, Aug 23, 2011 at 7:42 AM, Simon GARESTE <simon.gare...@scilab.org> wrote: > Hi, > > I have a problem concerning the upgrade from 3.0.4 to 3.0.10. I think I did > all the differents steps described on the UPGRADING file, but I end up on a > page without any css. On chromium, it indicates that my browser is too old, > on chrome I got the page, I'm (apparently) connected, but no css nor js. The > console of the debugging tool of chrome indicates that I have a 404 not > found on the css-cache file CommonCSS, on the js-cache files ModuleJS and > CommonJS, and so (I guess it induces) I have 3 uncaught type errors in > index.pl, about Objects that have no method Ready. > I did delete the cache, using the bin/otrs.DeleteCache.pl, so how comes? > > Thank you, > > Simon > > -- > Simon Gareste > Support& Development Engineer > -- > Consortium Scilab > Digiteo > Domaine de Voluceau > Rocquencourt - B.P. 105 > 78153 Le Chesnay Cedex > -- > > --------------------------------------------------------------------- > OTRS mailing list: otrs - Webpage: http://otrs.org/ > Archive: http://lists.otrs.org/pipermail/otrs > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs > --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
