Jump to content

Featured Replies

Posted

Hey Guys. Who of you can tell me the easiest way to upgrade from 4.7.18 in a short step-by-step list? 
I have tried to upgrade every time from beta 1 to beta 4 (v5). 

I go and copy all the new files into my old 4.7.18 environment. Then I start domain.tld/admin/upgrade and let the upgrader update everything once. After that, my start page is never accessible. I always get errors. 

For example this one

Quote

Fatal error: Declaration of IPS\Node\_Model::constructLoadQuery($id, $idField, $extraWhereClause) must be compatible with IPS\Patterns\ActiveRecord::constructLoadQuery(string|int $id, string $idField, mixed $extraWhereClause): IPS\Db\Select in /var/www/vhosts/domain.tld/system/Node/Model.php on line 1784

A clean installation is not the problem, but currently the Converter isn't ready 

Is it necessary to uninstall all modules and applications before? 

You will want to ensure that you are replacing every file with the version 5 equivalent. 1784 of that file for me is a comment so shouldn't be rendering an error.

  • Author

I'll try it again... 🙂 

Besides Beta 3 I tested the upgrade on a copy of my main site and I always had a white page so far after upgrading when I opened my site.

This is what I experienced and how I get it up and running.

  • I didn't overwrite the files on the server. I deleted all the files and uploaded the new ones.
    Be careful: Don't delete your uploads/downloads folder etc.. On my dev site I don't care!
  • I made sure the background task which is shown in the ACP was executed. I have a very small site and and I just clicked run it now. No, problems there.
  • I cleared all the caches in the support section of the ACP.
  • My main app is pages. After the upgrade I had to open every page and remove the used templates. Although, before the upgrade I switched to default templates this didn't help.
  • I had to go in the the database settings and remove the templates as well.

After these changes my dev site worked.

Of course, none of the custom blocks in pages worked. But this I expected.

Edited by Hatsu

  • Author

After a second try i got the following message 

 

Quote

Fatal error: Declaration of IPS\forums\widgets\_hotTopics::isExecutableByApp($app) must be compatible with IPS\Widget::isExecutableByApp(array|string $app): bool in /var/www/vhosts/domain.tld/applications/forums/widgets/hotTopics.php on line 62

 

and this one on my start page

Quote

TypeError: array_key_exists(): Argument #2 ($array) must be of type array, null given (0)
#0 /var/www/vhosts/domain.tld/system/Output/Plugin/Theme.php(95): array_key_exists()
#1 /var/www/vhosts/domain.tld/system/Theme/Theme.php(4009): IPS\Output\Plugin\Theme::runPlugin()
#2 [internal function]: IPS\Theme::IPS\{closure}()
#3 /var/www/vhosts/domain.tld/system/Theme/Theme.php(3964): preg_replace_callback()
#4 /var/www/vhosts/domain.tld/system/Theme/Theme.php(3885): IPS\Theme::_compileTemplate()
#5 /var/www/vhosts/domain.tld/applications/cms/sources/Blocks/Block.php(242): IPS\Theme::compileTemplate()
#6 /var/www/vhosts/domain.tld/applications/cms/widgets/Blocks.php(149): IPS\cms\Blocks\Block::display()
#7 /var/www/vhosts/domain.tld/system/Widget/Widget.php(1291): IPS\cms\widgets\Blocks->render()
#8 /var/www/vhosts/domain.tld/system/Widget/Widget.php(1323): IPS\Widget->_render()
#9 /var/www/vhosts/domain.tld/system/Widget/Area.php(914): IPS\Widget->__toString()
#10 /var/www/vhosts/domain.tld/system/Widget/Area.php(883): IPS\Widget\Area->getWidgetContent()
#11 /var/www/vhosts/domain.tld/static/templates/core_front_global.php(23202): IPS\Widget\Area->totalVisibleWidgets()
#12 /var/www/vhosts/domain.tld/system/Theme/SandboxedTemplate.php(68): IPS\Theme\class_core_front_global->widgetArea()
#13 /var/www/vhosts/domain.tld/system/Widget/Area.php(273): IPS\Theme\SandboxedTemplate->__call()
#14 /var/www/vhosts/domain.tld/applications/cms/sources/Pages/Page.php(2177): IPS\Widget\Area->__toString()
#15 /var/www/vhosts/domain.tld/applications/cms/sources/Pages/Page.php(2123): IPS\cms\Pages\Page->getPageContent()
#16 /var/www/vhosts/domain.tld/applications/cms/modules/front/pages/page.php(122): IPS\cms\Pages\Page->output()
#17 /var/www/vhosts/domain.tld/applications/cms/modules/front/pages/page.php(49): IPS\cms\modules\front\pages\page->view()
#18 /var/www/vhosts/domain.tld/system/Dispatcher/Controller.php(139): IPS\cms\modules\front\pages\page->manage()
#19 /var/www/vhosts/domain.tld/system/Dispatcher/Dispatcher.php(169): IPS\Dispatcher\Controller->execute()
#20 /var/www/vhosts/domain.tld/index.php(16): IPS\Dispatcher->run()
#21 {main}

 

I would try and disable all third party apps and plugins from your old site first. Then try and upgrade.

As mentioned, please ensure all files are version 5 equivalents. Seems like those are out of date

  • Author

I have checked twice. 
All files were transferred according to Filezilla. Without any problems. 

However, the hottopics.php file is also not included in the v5 upgrade

 

  • Author

ok i'll give up... will try the last chance. Install a fresh 4.7.19 instance. Convert the productive site to the demo site, without any apps and so on, migrate the User, Forums... and so on, and try to upgrade again.

Please make sure you are taking backups throughout this process.

@MythonPonty Why are you using 4.7.19 that is in beta maybe you should use 4.7.18 the stable version then upgrade.

^ this is a very good point. While it "should" be fine,  there is no guarentee. 

  • Author

I had already tested it before with 4.7.18. I had the same result here.

Perhaps an application is interfering in the background, even if it has been “deactivated”. 
Therefore, my plan would be to install a fresh installation with 4.7.19 after the release, migrate the data from the database once, and then perform another upgrade based on the fresh installation (without applications and plug-ins). 

If the files are still present and its installed, then yes thats possible. You would need to check with the author

  • Author

Soooooo guys... I'm happy now. 

Short step list of what I did to finally use a working installation of 5.0.0 Beta 4. 

1. fresh installation of 4.7.19 (without existing data)
2. conversion of data from the production environment to the new fresh installation environment. 
3. standard procedure to upgrade from 4.7.19 to 5.0.0 Beta4. Exchange all files as supplied and then start domain.tld/admin/upgrade. 

Lo and behold, everything works perfectly and without any error messages. Now it's time to get down to business. 

43 minutes ago, MythonPonty said:

Soooooo guys... I'm happy now. 

Short step list of what I did to finally use a working installation of 5.0.0 Beta 4. 

1. fresh installation of 4.7.19 (without existing data)
2. conversion of data from the production environment to the new fresh installation environment. 
3. standard procedure to upgrade from 4.7.19 to 5.0.0 Beta4. Exchange all files as supplied and then start domain.tld/admin/upgrade. 

Lo and behold, everything works perfectly and without any error messages. Now it's time to get down to business. 

Have fun 🙂 

Recently Browsing 0

  • No registered users viewing this page.