latest GIT .. lots of bugs

[willem010]

using the git version of this morning i updated 2 sites..

one site was running the old v1 e107 .. that got stuck in upgrade process one site was already updated to v2, just copied the new git files. \ this comment is edited on each find

upgrade v1 site (site 1)

• keeps yelling my fb_like plugin isnt compatible (my own fork, it should be ok.. runs without notice or errors on other v2 site.. ). hitting disable plugin does noting but refresh the page.

  \ found out: it was showing an older version number in the pluginmanager the updated fb_like plugin needed to be updated in the plugin manager, got that sorted now.

• ERROR on download tables during conversion to v2 (showed only once)
• stuck in the upgrade process, UPGRADE_01 (system log shows: Update from 1.0 to 2.0 executed Start version: 2.0.0 (git) ) running debug shows Update required in update_routines.php on line 1509 (Import 159 Download File(s) and 0 Public File(s) into Media Manager)

• some menu's not showing (while showing ok in menu manager)

  \ manually changed database, cleared cache,and cookies removed and reinstalled plugins. menus are showing now .

• old media not found/ known to new system

  \ chmodding media folder worked here, media now has both avatars and newspost images

• seo urls empty. probablty due to not finishing upgrade to v2?
• contact page, user pages empty. \ removing obsolete folder /e107_themes/templates fixed this.

(site 2) same git version on already updated v2 site: (which was running ok on yesterdays code ... )

• cant open several admin functions, (f.i. system log, plugin manager and more refirects to index page directly) **fixed by changing from session type login to cookies
• media no longer showing when using SEF urls
• performance .. very slow. \ banlist?

The version from yesterday was a lot more stable and didnt have all these errors.. please revert.

[willem010]

what about a message (for those hard to move installations) instructing the admin where to move the files manually ? all you would need is a scan for the files on the new location to check if it's been done.

[Moc]

@willem010 Can you try another test upgrade please, using the latest files on Github? Focus on the update procedure again as the 'download files' process has now been optimised. Hopefully this help with the "freezing and high cpu" thing you experienced.

[willem010]

i will have to setup a new server for this, and copy about 24gb download data.. that will take me some time ;)

[Moc]

@willem010 Whoops.. Well it would be much appreciated anyhow :)

I'm pretty sure this particular issue can be closed now. Any outstanding problems should be submitted in new separate issues.

[willem010]

.. upgrade works faster now. (not much tho .. took about 8 mins to complete, but i think this was on a faster server.)

anyway, this seems to work ok now. keeping it closed.