Test Upgrading from 1.x to 2.x

[CaMer0n]

Should work, more testing needed, not crucial for alpha

[Moc]

Testing is in progress, thanks Cameron 👍

[STR82U]

Got through to the dbase updates/upgrades but ended up with the "Forum" update failing due to:
"Fatal error: Call to undefined function update_forum_08() in /home/picture/public_html/e107_plugins/forum/forum_update.php on line 1073"

Custom theme and coding made it hard to tell but the core theme looked ok, gallery functioned, plugins seemed to be fine but not many installed. Going to make more detailed list later after the next test.

Site tested by swapping out public_html files and moving custom folders over.
Going to test this again after a backup can merge the files and see how much easier it is.

SUGGESTION: When there's a dbase update with (Must be run first) - Put that at the top so people see it, maybe draw more attention to to that particular update v1 to v2.

[STR82U]

Second upgrade test was prepared by merging a backup copy of public_html with the current V2 GitHub build.

Had to uninstall cl_widgets plugin BEFORE swapping the original public_html for the V2 folder. An error I forgot to copy. Trying to reinstall it stopped this run of testing.

Got through to the dbase updates/upgrades.
System told me which folders to delete from the plugins folder.
Ended up with the "Forum" update failing due to: "Fatal error: Call to undefined function update_forum_08() in /home/picture/public_html/e107_plugins/forum/forum_update.php on line 1073"

While the cl_widgets plugin was uninstalled the front end looked normal using the core theme; contact page, forum, front page, gallery, a few others but no changes in admin (changed theme before changing to V2_merged folder.

Will make another go of it later and leave the plugin uninstalled.

[STR82U]

ROUND 3: Testing today with a simple V1.0.2 that uses "Kubrick" as the site theme - no fancy plugins.
The upgrade was prepared by merging a backup copy of public_html with the current V2 GitHub build.

Clicked to update dbase > Update from 1.x to 2.0 (Must be run first) > Successful: asked to remove old folders:
Before continuing, please manually delete the following outdated folders from your system:
/e107_plugins/compliance_menu
/e107_plugins/counter_menu
/e107_plugins/other_news_menu
/e107_plugins/powered_by_menu
/e107_plugins/sitebutton_menu
/e107_plugins/userlanguage_menu
/e107_plugins/usertheme_menu

2nd update from: "Update from 1.x to 2.0 (Must be run first) > Success
Update: Add additional/missing core settings > Success
Update: Calendar Plugin > Success (added a new tab/sitelink for calendar that was bad - http://www example com/{e_UPLOAD}e107_plugins/calendar_menu/calendar.php )
Update: Statistic Logging > Success (Adding Link: Visits with url [{e_PLUGIN}log/stats.php?1] and perm everyone) - added link that was bad - http://www example com/{e_UPLOAD}e107_plugins/log/stats.php?1

At this point the PUBLIC view of the site is normal except for the demo news item getting added to the front page may have reset the "Front Page" settings. Changed "Front Page" settings to "Welcome Message" successfully.
At this point the ADMIN view of the front end is missing the lower half of pages > investigating >> this error may have been caused by the MENU ITEM private_msg (PM) with visibility set to "Admin" - plugin was installed and still is. Removing then reading the menu item causes the error to reappear to admins in the front end.

NOTES:

3 Times the FF browser (once with Chrome) cache was cleared and the Admin logged back in, the dbase update notice reappears: "There is a database update available, please click button to install ..." and performed Update from V1 to V2. The 4th cache clear and admin login showed no updates available. Logging in to admin with other browsers confirms this.
The above notice came back one more time in FF after cleaning the dbase manually using phpMyAdmin (failed logins and spam news items) - all the repeated dbase updates were only for "Update from 1.x to 2.0 (Must be run first)" > Success every time.

Error Log Had This To Say (dots removed from URLs to prevent links):
[Sat Jan 12 08:23:05 2013] [error] [client 168.6.225.225] File does not exist: /home/example/public_html/e107_images/bbcode/table.png, referer: http://www example com/e107_admin/cpage.php?mode=menu&action=edit&id=5
[Sat Jan 12 08:21:24 2013] [error] [client 168.6.225.225] File does not exist: /home/example/public_html/e107_web/js/bootstrap/css/images, referer: http://www example com/e107_admin/cpage.php?mode=menu&action=edit&id=5
[Sat Jan 12 08:21:24 2013] [error] [client 168.6.225.225] File does not exist: /home/example/public_html/e107_images/bbcode/table.png, referer: http://www example com/e107_admin/cpage.php?mode=menu&action=edit&id=5

After ALL upgrades and fresh installs (not just this one), OPERA browser kicks out this JS error:
"Uncaught exception: ReferenceError: Undefined variable: SyncWithServerTime"
(there was not much more detail than that, I'll create an Issue later if it doesn't come out first).

Happy with this upgrade - going to leave it in place.

[STR82U]

Round 4: Tested Jan. Saturday 12 2013 - Upgraded a V1.0.2 to V2 after minor preference and plugin changes before the upgrade.

No Issues.

[STR82U]

Round 5: Tested on Jan. Sunday 13 2013 - Upgraded a 0.7.24 to V1.0.2 to V2 - SITE HAS CUSTOM HTACCESS
original site install date: Sunday 18 June 2006 - 14:34:54

The upgrade from 0.7.24 to V1.0.2 left the admin area with a non-default admin theme, changed to Jayya and then Core with acceptable results. Public side of site seemed unaffected.

The upgrade from V1.0.2 to V2 was in line with current expectations; updated dbase one, removed deprecated folders, updated dbase 2nd time, updated core settings, then repeated requests from system to repeat "Update from 1.x to 2.0 (Must be run first)".

AFTER ALL UPGRADES:

Banner Plugin - isn't a plugin on the live site this upgrade was done from and had to be installed. No functionality returned to frontend and the Update Banner page doesn't display anything from the /e107_images/banner/ directory ("Banner Image" button doesn't open the dropdown selections) - personally this can be overcome with shortcode BUT may have been avoided with more time spent after upgrading to V1.0.2 - this is acceptable to me. Other conditions that apply are that this theme replied on custom hacks over the years.

Front end custom htaccess works except one type of conflicting rewrite from a deprecated plugin goes 404 (FURL Still Installed but htaccess works for 95% of pages in this small site). Text editor "find and replace" can fix that.

Other plugins installed in original site include: Content Management, The e107Helper Project, ADD This, e107_mobile, Page Creator (For Noobs) and Wrap.

NOTE: This was a successful test - nothing lost due to core or default files.

[CaMer0n]

If there are repeated requests to "update from 1.x to 2.0" - please enable debugging and take note of what is causing the request to be triggered. Ideally, the update should only need to be run once.

[STR82U]

"please enable debugging and take note of what is causing the request to be triggered" - Understood.

[CaMer0n]

Closing this for alpha1. We can open another for alpha2.