Loading...
 
Architecture / Installation

Architecture / Installation


10.5->11.1 Login page blank

posts: 9 USA

I was trying to upgrade from 6.2 to 12.0 and found there is an error in the upgrade script. That is documented by another person. So I set my sights on 11.1. Going to it directly partially succeeded. The site had almost all the data but when I tried to log in, all I got was a blank page. Thinking it was a problem with the DB upgrades I started going through the upgrades one by one.

6.2->6.13 Good
6.13->9.7 Good
9.7->10.5 Good
10.5->11.1 Fails with a blank login page.

We are now running 10.5 but I really want to get to 12.0.

Has anyone else seen this? Is there a fix?

posts: 3656 United States

LOTS of changes from 6 to 12.

  • Did you run Tiki Server Check to make sure your host can support 12?
  • Are you using a custom theme? There were lots of theme and template changes.
  • Did you turn on Tiki's error reporting?

Normally it is not necessary to run the incremental upgrades. I've upgraded many sites from 6LTS -> 12LTS with no issues. Be sure to review the Release notes to see everything that has changed.

HTH,

- Rick | My Tiki Blog | My Tiki UserPage

Why be a dummy? Get smarty! TikiForSmarties.com
Tiki for Smarties, your source for the best (and only) Tiki books, guides, and tutorials.
posts: 9 USA

The host can support 12.0. I have an independent install of 12.0 running on the same system using the same mysql instance.

The reason I was upgrading to 11.1 instead of 12 in the first place is that the 12.0 DB upgrade script gives the erroneous error:

MySQL INFORMATION_SCHEMA not available. Your MySQL version is too old to perform this operation. (upgrade_20120429_fix_collation_tiki)

See forum: https://tiki.org/forumthread50478
Bug report: http://dev.tiki.org/item5103?itemId=5103

The system is using mysql 5.1.73 which is the version current distributed with RHEL 6.5.

We are actually running a DB that was directly converted from 6.2 to 10.5. That was built after doing the incremental updates to see where the process failed at.