PHP v 7

Hi Greg,

What version of CMSB are you attempting to install? PHP 7 and mysqli support was added in v3.09.

Thanks,

Hi Daniel,

Ah, that explains it. I am trying to install v3.06.

I will upgrade...

Thank you,

Greg

Hi Interactive Tools

I am getting the same error in upgrading from PHP 5.6 to PHP v7.0.

This program requires the PHP 'mysql' extension.
Please ask your hosting provider (or server administrator) to install missing PHP extension(s).

I am trying to upgrade to PHP 7 as that's the highest the host has, and have uploaded cmsbuilder_3_50_build2215_release (I've installed it's twice in case there was an upload error).  The host has indicated that "PHP-7.0 support MYSQLi extension only and that I need to do coding changes from MYSQL to MYSQLi."  

Can you please provide any guidance.

Thanks

Carole

Hi Carole,

That's a curious issue, as that error was removed from CMSB version after v3.07. This makes me think that there's possibly an issue when upgrading to the latest version. I would first double check that the directory you're uploading the new version is correct and that it is overwriting the existing cmsb directory (you should be able to check the "latest modified" date/time on "/cmsb/lib/init.php" to verify that it is being overwritten).

Let me know if you're able to make any progress, or if you have any further questions!

Thanks!

Hi Daniel

The CMS is showing that the version has been upgraded to CMS Builder v3.50 (Build 2215) and I can access the backend.  However, the front end is requesting the MySQL when I swap it to PHP 7.0 at the host.  Here's the message from the itin.php file and the latest version has definitely been fully uploaded (twice now) but still the same message.  Exactly what should I be looking for/how to change it?

<?php

  ### CMS Constants Reference:
  // CMS_ASSETS_DIR         - filepath url of cms assets folder, also available as $GLOBALS['CMS_ASSETS_DIR'], eg: /usr/local/apache2/htdocs/cmsb
  // CMS_ASSETS_URL         - url of cms assets folder, also available as $GLOBALS['CMS_ASSETS_URL'] and javascript as phpConstant('CMS_ASSETS_URL'), eg: http://www.example.com/cmsb
  // DATA_DIR               - The filepath of the cms data folder, eg: /usr/local/apache2/htdocs/cmsb/data
  // IS_CMS_ADMIN           - if inside of cms admin, set in admin.php
  // MAX_DEMO_TIME          - Demo mode: When creating new demos, demos older than this are removed
  // PREFIX_URL             - development prefix added to urls, from $SETTINGS['webPrefixUrl'], eg: /~username or /development/client-name
  // REQUIRED_MYSQL_VERSION - Version of MySQL required by software (program dies if version isn't supported), set in init.php
  // REQUIRED_PHP_VERSION   - Version of PHP required by software (program dies if version isn't supported), set in init.php
  // SCRIPT_DIR             - The filepath of the cms script folder, eg: /usr/local/apache2/htdocs/cmsb
  // SESSION_STARTED        - whether a session has started, set in startSessionIfRequired()
  // SETTINGS_DEV_FILENAME  - dev server settings file (auto-defined and used if it exists), eg: settings.example.com.php
  // SETTINGS_DEV_FILEPATH  - dev server settings path (auto-defined and used if it exists), eg: /usr/local/apache2/htdocs/cmsb/data/settings.example.com.php
  // SETTINGS_FILENAME      - actual settings file (either settings.dat.php or dev filename), eg: settings.dat.php
  // SETTINGS_FILEPATH      - actual settings file (either settings.dat.php or dev filepath), eg: /usr/local/apache2/htdocs/cmsb/data/settings.dat.php
  // START_SESSION          - whether to start a session, set in admin.php and plugins that require session access

Hi Carole,

Sorry I didn't make the connection before.

I don't know if this is a similar to the issue that I had when upgrading.

Might be worth a look.

https://www.interactivetools.com/forum/forum-posts.php?postNum=2242946

Good luck,

Jerry Kornbluth

Hi Jerry

Thanks for your interest.  I reviewed your thread and triple checked that everything was uploaded (ie, nothing missed), yet it remains an issue.  I have sent a request to Level 2 support and look forward to the response as have quite a few other clients to swap over as well.

Thanks again

Carole

Hi all,

For anyone who may be experiencing a similar issue, the cause for this was found to be some incorrect paths in the front-end files when trying to load the CMSB viewer library. There was an old version of CMSB separate from the version being upgraded, so while the back-end was properly functional, the front-end was still running outdated code.

Cheers,