Re: 1.38 installation trouble

We're still working out the nuances of github, and the link to the source files do not point at the corrected tag for this release. I have updated the release page and attached a proper zip file for this release.

You can download this for a full install https://github.com/ImpressCMS/impresscms/releases/download/v1.3.8/impresscms-1.3.8.zip

Topic


Re: 1.38 installation trouble

Hi larrykh465,

I'll need some more info:
are you updating or installing from scratch
what file did you download?
what is your environment (PHP version, mysql version)?

Topic


Re: 1.38 installation trouble

  • 2015/8/27 3:59:44

Totally new newbee here but I am getting the same error,
Fatal error: Interface 'icms_db_IUtility' not found in /home/public/libraries/icms/db/legacy/mysql/Utility.php on line 52
from 1.3.8 that I got from this site on the 27th 1.3.6 popped right in.



Re: ImpressCMS Upgrade 1.3.7 to 1.3.8

  • 2015/8/26 9:59:49

Thanks for the link and the informative notes.



Re: ImpressCMS Upgrade 1.3.7 to 1.3.8

My fault, I'm still following what was on the wiki for the release procedure - here : http://wiki.impresscms.org/modules/wiki/index.php?page=Release_Procedure - that documentation needs some serious updates it seems



Re: 1.38 installation trouble

Hi, I pushed the newest bugfix by Skenow as the new 1.3.8final release.

It's not a good idea to go back and forth in the installer, it's not robust enough to support that without errors Your second error is no surprise in that case.

I tried an install starting from the 1.3.8final release (as available now on github and the site) on XAMPP with PHP 5.5.11 and I was able to finish the site installation without a problem.

There were 3 changes done in the bugfixes, so make sure you use that version.



1.38 installation trouble

Hi

I just tried to upgrade my local dev environment (PHP 5.5.25) with a clean 1.38 install. I get the following error on this page with both DB options:

http://192.168.1.99/dev/install/page_tablescreate.php

Notice: Use of undefined constant XOOPS_DB_TYPE - assumed 'XOOPS_DB_TYPE' in /share/MD0_DATA/Qweb/dev/libraries/icms/db/Factory.php on line 141 Notice: Use of undefined constant XOOPS_DB_TYPE - assumed 'XOOPS_DB_TYPE' in /share/MD0_DATA/Qweb/dev/libraries/icms/db/Factory.php on line 148 Fatal error: Class 'icms_db_legacy_XOOPS_DB_TYPE_Safe' not found in /share/MD0_DATA/Qweb/dev/libraries/icms/db/Factory.php on line 151


If I back up a few steps in the installer and try again I get a different error on the same page:

Fatal error: Interface 'icms_db_IUtility' not found in /share/MD0_DATA/Qweb/dev/libraries/icms/db/legacy/mysql/Utility.php on line 52


Any ideas?

I really should know better than to mess with my dev environment during a project, but you know, curiosity and cats...



Re: ImpressCMS Upgrade 1.3.7 to 1.3.8

  • 2015/8/23 17:18:44

Please excuse me. Then I got it wrong with the upgrade and had razed it right :) Yes, the Version Checker in the backend I see now that I have the latest version of ImpressCMS.

Then everything went well, thank you. Oh, then the upgrade for older versions is intended. I know that now.


Attach file:



png  impresscms138-versions-checker.png (12.09 KB)
3974__531655da62e4f3a9d.png 768X246 px


Re: ImpressCMS Upgrade 1.3.7 to 1.3.8

It looks like we have packaged the upgrade files incorrectly, Alex. The 1.3.7 - 1.3.8 should not have an upgrade folder in it. You can use that package, just delete the upgrade folder.

Login as an administrator to your site, upload and overwrite the existing files and then go to the Admin Control Panel to update the system module.

The upgrade folder is only necessary if you are upgrading from a very old version (1.0, or even older - XOOPS). I think going forward, we will only offer that on request.



Re: ImpressCMS Upgrade 1.3.7 to 1.3.8

  • 2015/8/23 16:24:07

Hi Fiammybe,

thanks for the hints. I have now uploaded the remarks of the ZIP package to the server and wanted to call this: /upgrade/

Then I saw these errors.

Fatal error: Class 'IcmsDatabasetable' not found in /www/htdocs/xxxxxx/cms/impress/upgrade/upd-icms-1.0-to-1.1/index.php on line 71

I use MySQL.



Re: ImpressCMS Upgrade 1.3.7 to 1.3.8

Hi AlexL,
you should have no problems when you use the upgrade file, which I posted in the meantime on the github page : https://github.com/ImpressCMS/impresscms/releases/tag/1.3.8

Using the impresscms_1.3.x-to-impresscms_1.3.8.zip file, I have tested the upgrade from 1.3.7, and everything seems to be working as it should.

Let me know if you still have an issue with this file. Does your original site use PDO or mysql directly?



ImpressCMS Upgrade 1.3.7 to 1.3.8

  • 2015/8/20 18:10:41

Hello Webdevelopers,

I have learned that there is a new version of ImpressCMS and was about to upgrade from 1.3.7 to 1.3.8.

Do I have to upgrade right with /upgrade/index.php or is it already when I uploaded the new files to the server?

If I call in the browser /upgrade/index.php, I get this error appears:


Fatal error: Class 'IcmsDatabasetable' not found in /www/htdocs/xxxxxx/cms/impress/upgrade/upd-icms-1.0-to-1.1/index.php on line 71


What can it mean? Happy about your assistance. Thanks!



Re: errors on upgrade from 1.3.3 to 1.3.7

And don't forget to test that the backup actually works :)



Re: errors on upgrade from 1.3.3 to 1.3.7

ok great will do, but may wait a bit lol



Re: errors on upgrade from 1.3.3 to 1.3.7

I was going to point you to the wiki for the change to pdo

but it seems you already found the info you needed.

I would recommend to have a backup of your DB and files before starting the upgrade on the production site, just as a precaution.



Re: errors on upgrade from 1.3.3 to 1.3.7

I just upgraded the way skenow suggested. But I upgraded on the localhost just to be sure not to disable the production site.

The upgrade went perfect, only one issue (see below), I am at 137 now, locally. I am now going to update the news and sprockets modules

But my new question is, what about the DB, an error in admin says:

Quote:

System Warnings Edit
The mysql extension is being deprecated as of PHP 5.5.0 (PHP MySQL Extenstion). Switch to PDO, instead



Didnt I need to upgrade the DB? how to now if already at 1.3.7?

Gerry

update: I saw a post about changing the line in mainfile to:

define( 'XOOPS_DB_TYPE', 'pdo.mysql' );

All ok and working, ALSO updated News to 1.16 and Sprockets to 2.0 versions and all ok, and also updated all other modules, but havent checked for new versions yet.

So if all good so far just might be able to upgrade the production site.....



Re: errors on upgrade from 1.3.3 to 1.3.7

  • 2015/6/11 11:51:24
  • 63RD

I was thinking about protector again and it could be a good practise to disable it while doing the upgrade. It has a file manipulation check feature which gives a blank page as default reaction when an altered file, lets say by ftp, was found.

Have a good day!

The best way to predict the future is to invent it! (Alan Kay)
Good things happen when you go for it! (Alan Webb)
Seek the wisdom of the ages, but look at the world through the eyes of a child.


Re: errors on upgrade from 1.3.3 to 1.3.7

Ok so I have managed to get my site running on PHP 5.5.2.5. The errors mentioned above are still there but they are not fatal, and looking at yours I don't think those are either.



Re: errors on upgrade from 1.3.3 to 1.3.7

I just tried updating to PHP 5.4 on an existing 1.3.7 site, and I get a bunch of similar errors and a white screen:

Strict: Only variables should be assigned by reference in file /home/[account]/[trustpath]/modules/protector/include/postcheck_functions.php line 23 Strict: Accessing static property icms_member_groupperm_Handler::$_cachedRights as non static in file /libraries/icms/member/groupperm/Handler.php line 390 Strict: Declaration of icms_view_block_Object::store() should be compatible with icms_ipf_Object::store($force = false) in file /libraries/icms/view/block/Object.php line 429 Strict: Declaration of icms_view_block_Object::delete() should be compatible with icms_ipf_Object::delete($force = false) in file /libraries/icms/view/block/Object.php line 429 Strict: Only variables should be assigned by reference in file /include/functions.php line 899 Strict: Only variables should be assigned by reference in file /include/functions.php line 899 Strict: Only variables should be assigned by reference in file /libraries/icms/view/block/Object.php line 119 Strict: Only variables should be assigned by reference in file /include/functions.php line 899 Strict: Only variables should be assigned by reference in file /libraries/icms/ipf/permission/Handler.php line 124 Strict: Only variables should be assigned by reference in file /libraries/icms/ipf/permission/Handler.php line 135


I recompiled again with PHP 5.5.25 to see what would happen and there are a few differences:


Strict: Only variables should be assigned by reference in file /home/[account]/[trustpath]/modules/protector/include/postcheck_functions.php line 23 Unknown: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in file /libraries/icms/core/DataFilter.php line 775 Unknown: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in file /plugins/textsanitizer/syntaxhighlightphp/syntaxhighlightphp.php line 23 Unknown: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in file /libraries/icms/core/DataFilter.php line 800 Unknown: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in file /libraries/icms/core/DataFilter.php line 775 Unknown: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in file /plugins/textsanitizer/syntaxhighlightphp/syntaxhighlightphp.php line 23 Unknown: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in file /libraries/icms/core/DataFilter.php line 800 Strict: Accessing static property icms_member_groupperm_Handler::$_cachedRights as non static in file /libraries/icms/member/groupperm/Handler.php line 390 Strict: Declaration of icms_view_block_Object::store() should be compatible with icms_ipf_Object::store($force = false) in file /libraries/icms/view/block/Object.php line 429 Strict: Declaration of icms_view_block_Object::delete() should be compatible with icms_ipf_Object::delete($force = false) in file /libraries/icms/view/block/Object.php line 429 Strict: Only variables should be assigned by reference in file /include/functions.php line 899 Strict: Only variables should be assigned by reference in file /libraries/icms/view/block/Object.php line 119 Strict: Only variables should be assigned by reference in file /include/functions.php line 899 Strict: Only variables should be assigned by reference in file /libraries/icms/ipf/permission/Handler.php line 124 Strict: Only variables should be assigned by reference in file /libraries/icms/ipf/permission/Handler.php line 135


I did find a few call-time pass-by-references left in my modules too, which are fatal. Don't know how I missed them but will fix those as soon as possible.

Edit: Wait a bit I'm just testing this again.



Re: errors on upgrade from 1.3.3 to 1.3.7

It was fully functioning until after the php upgrade, then it gave me that first error. After I tried upgrading, thinking that was the case, as someone mentioned a fix would be 1.3.7 but that didnt work either lol.

Before upgrading I downloaded all files, back up after back up, then zipped it all up, tried uploading 137 and kept getting upload errors, so with the back up files I wrote them over with 137 then zipped and uploaded that unzipped, changed permissions, then upgrade the db, I created a new db with old backed up db, upgraded and didnt get but a blank scree during the tablecreate process.

I can try again, but not sure If I can get that original errors, or even try to duplicate fiammybe, using 133 with php5.5.11




 Top