Error.log after install 2.02

FWIW, those error log entries regarding not being able to copy files during upgrade should be ignored if you are using the traditional distribution. If you are using advanced, then it would be a problem.

Quote from: splittingred at Sep 20, 2010, 07:11 PM

Can you detail the steps you’re taking to get this? Are you clicking on ’Download Extras’ or on "Add New Package"?

Add New Package -> Select a Provider -> choose modxcms.com -> Next ->

Sometimes it will work correctly and go on to the Package Retriever the first time, although at the top of the tree it always says "Provider" and not "modxcms.com". But if I leave the Package Retriever window (no matter how), the second time I repeat the above steps it will do nothing after clicking Next. Sometimes the modxcms.com provider is preselected in the drop-down; sometimes not; doesn’t matter.

I can clear the MODx cache, clear the MODx permissions, logout of MODx, clear the browser cache, and close the browser. When I start it all back up, often it will work correctly the first time, but sometimes it will fail right away. What always seems to fix it is a page refresh. When it fails, the browser js errors above are reported.

I usually do the following after upgrading from GIT:

-Security/Flush Permissions
-Clear cache for the browser I use
-Disable compress css(System Settings): compress_css=No
-Disable compress js(System Settings): compress_js=No

..and finally if the above fails

rename or delete the cache folder(core/cache). This way MODx needs to generated it again.

I don’t know exactly why I do the above but seems to be working