Loading...
 

Architecture / Installation


Not exactly what I expected when upgrading from 18.2 to 18.3

posts: 98 Greece

I have tried a few times to do the upgrade mentioned on title, but the only thing I get is a new home page with no wiki pages (thankfully, my database and previous installation, the 18.2, is intact and waiting for me to change folder name and get my site back).

As I have upgraded my tiki countless times for 6+ years now, I can't really understand what is my error. During installation I choose "upgrade existing..." and can't get to the page where I connect db to my new install / folder. Instead it is "connected automatically..." and nothing happens.

Any hint?

posts: 658
That's a new one, all I can say at this point nikosal, since my 18.3 upgrade, frustrating and weird issues keep popping up, I'll check around and see if I can have any valuable input on your issue.

posts: 98 Greece
I sincerely thank you - I will try to come back with a step to step description of what I do.

posts: 29
I had to update my wiki installation from 18.0 to 18.3 by command line, otherwise I got strange errors. Maybe that fixes it for you too?

posts: 98 Greece

I could -finally- do the upgrade to 19.1 the usual way.

For a reason still unknown (but not longer bothering me!) while trying to upgrade to 18.3 I was not asked to connect with db using my credentials and so I was ending up with a blank db.

posts: 22
Can I ask, did you just end up upgrading from 18.2 to 19.1? I'm having all kinds of trouble going from 18.1 to 18.3, so I thought I would try just upgrading to 19.1 next. I thought a minor upgrade would be easier and it would make more sense to stay with the LTS version, but seems like I'm not the only one having problems.
posts: 98 Greece
yes, I did exactly that (18.2->19.1)

posts: 7877 Israel

Sad to read you got troubles upgrading.

It is important for the project to understand clearly what happened to you but for this we need detailed report.

Things like did you use an official released package, an svn version what kind of MySQL db you use (mariaDB or myisam), the db encoding, etc...

Also the developers will need the precise error thrown back.

Another important things to consider is that with PHP7 (and the new ZendFramework) there are more controls and check about expected values and you may see "warnings" (warniong and not errors) due to a misusage of some elements;

Just 2 examples to give you an idea:

  • I debugged on one customers many errors due to the fact that he was duplicating pages and pages with empty footnote area plugin in case he’ll need it. That’s not the way it is supposed to work. :-)
  • On another customer I found out that he was using an email address for his articles author fields, again that’s not what is expected.


Those 2 things weren’t checked or signalled when using previous versions (and previous PHP version) now they lead (thanks) to a warning. There are more but it was just to give you an idea. So when you have warning read the warning content, it may give a lead on what is going on.

Please for whatever issue you have (after trying to solve it) you are welcomed to post a ticket at https://dev.tiki.org/Development (after checking it is not already reported).

Join our Tiki Open Online Hours session every first, second and fourth Thursday of the month and receive support from a Tiki consultant online for free.


Why Register?

Register at tiki.org and you'll be able to use the account at any *.tiki.org site, thanks to the InterTiki feature. A valid email address is required to receive site notifications and occasional newsletters. You can opt out of these items at any time.

Newest Forum Posts