(Solved)Hyacynthe upgrade 1.10.3 - Stuck at step 6

[micahgodbolt]

I am upgrading a site from 1.9.4.1 to 1.10.3 - I uploaded all of the 1.10.3 files, ran the install/upgrade.php, did a full check-sum (passed). Everything else passed normally, but when I get to step 6, I get nothing except the step bar at the top.

I have restored to the original site and did the entire process again with the exact same result.

What happens at step 6 that might be causing this hangup?

[scelle]

Outdated (incompatible with the 1.10.x series) modules! Read the Recommended Upgrading Procedure.

[micahgodbolt]

Nice! Thanks. I'll give that a try.

[micahgodbolt]

Yup, that did the trick. Now to track down the offending module! Any easy way to figure that out? Is there a list of discontinued modules? Or will there be some note on their forge page?

[Rolf]

Probably not fully up to date, but it will help http://forum.cmsmadesimple.org/viewtopi ... 35#p265635

Grtz. Rolf

[micahgodbolt]

Well shoot...I looked over the modules on this site (which isn't a huge list) and checked them against that list and against other installs that I have done. I don't see anything that would cause problems.

Do you see any suspects?

Code: Select all

CMSMailer
2.0.1
FileManager
1.1.0
MenuManager
1.7.6
ModuleManager
1.4.2
News
2.11.4
nuSOAP
1.0.2
Printing
1.1.2
Search
1.6.10
ThemeManager
1.1.4
TinyMCE
2.9.1
CGExtensions
1.27.2
FrontEndUsers
1.16.2
SelfRegistration
1.6.14
Captcha
0.4.5
CGEcommerceBase
1.3.9
CGSimpleSmarty
1.4.8
Products
2.15.1
Cart
1.8.1
CGPaymentGatewayBase
1.0.11
AuthNetAimSubscribe
1.2.5
PaypalGateway
2.3.5
Orders
1.13
AuthNetAim
1.4
CustomContent
1.7.3
CGSmartImage
1.6.1
Glossary
0.6.8
TemplateExternalizer
1.3.1
Gallery
1.4.4

[scelle]

Well, I can tell you that nuSOAP and Printing (replaced with CMSPrinting) are deprecated in 1.10.x series. So, you can delete them completely.

As for the rest of the listed modules, I sincerely doubt that anybody will do your job for you. Go to The Forge and check one 3rd party modules by one - look at the release date, Release Notes and Changelog. If the module is released in October (or after), there is a good chance that it is compatible with 1.10.x series. Check the Release Notes and Changelog, it should say something like "Fixed for CMSMS 1.10". If all of your (necessary) modules are not compatible, then stick with the 1.9 series and try contacting module authors, asking them to upgrade the problematic modules.

[micahgodbolt]

I certainly don't expect anyone to do my job I did my best to compare what was there with what I have installed in other 1.10 installs, or checked the forge for recent 1.10 updates.

I'll try nusoap and print, and cross my fingers. Otherwise, I guess staying at 1.9 isn't the end of the world.

[uniqu3]

Well you can allways rename all third party modules in modules folder like SomeModule~ and it will be sort of disabled and not recognized as installed, then you will be able to pass that step and figure out whats wrong afterwards.
A cause to your problem can aswell be some UDT or plugin that you are using.

[DIGI3]

Glossary caused this issue for me, it's now been updated a new version in the forge.

[micahgodbolt]

Thanks Uniqu3 - the changing name trick worked well. I was able to go back through 1 by 1 to see which module was causing the issue. Appears that it was my orders module! Didn't see that coming. Now to track down why. ---- or maybe it is. Shessh...problem city.

[micahgodbolt]

Hah! Seems it took a few refreshes for the problem to kick in/out. So it wasn't orders that was the issue....it was the module i had turned off a few minutes prior.....Glossary!

[M@rtijn]

So this one is solved?

Would you be so kind to add [solved] in front of the title of the first post, as per http://forum.cmsmadesimple.org/viewtopic.php?f=3&t=8692