/volume1/web/phpvms70/install/install.php(57): Installer::AddTables() #3 {main} thrown in /volume1/web/phpvms70/core/classes/ezdb/ezdb_mysqli.class.php on line 97
Just quickly want to ask, in addition to above, I’ve got the 5.5.2 version running at the moment. Has anyone actually managed a database migration with these changes or have those of you, that have played with this, just done a clean install?
Seeing as V3 seems to have come to a stall, I wanted to know what kind of results people have had with this for migrations.
when I install phpvms 7.0 on my NAS it shows the error below
Fatal error: Uncaught Error: Class ‘mysqli’ not found in
…
So how to fix it. I know little about php
This looks like some files are missing? I’m not sure… what OS is your NAS?
13 hours ago, Brendan03 said:
Just quickly want to ask, in addition to above, I’ve got the 5.5.2 version running at the moment. Has anyone actually managed a database migration with these changes or have those of you, that have played with this, just done a clean install?
Seeing as V3 seems to have come to a stall, I wanted to know what kind of results people have had with this for migrations.
Thanks.
The only testing I’ve done is clean installs. This thread was more for help with that testing and stuff. Trying to make it backwards compatible with PHP 5.3 as well
The only testing I’ve done is clean installs. This thread was more for help with that testing and stuff. Trying to make it backwards compatible with PHP 5.3 as well
Forgive a potentially stupid question, but how does this affect my current site. I am running phpVMS 5.5.x from SimPilot which is a .php version whereas this version that you have here is .tpl. Since I notice that my host still offers down to php 5.3 is this an immediate concern or do I have a while? Also, is phpVMS 4 going to be able to successfully migrate my current database, as well as work with all addon modules?
Forgive a potentially stupid question, but how does this affect my current site. I am running phpVMS 5.5.x from SimPilot which is a .php version whereas this version that you have here is .tpl. Since I notice that my host still offers down to php 5.3 is this an immediate concern or do I have a while? Also, is phpVMS 4 going to be able to successfully migrate my current database, as well as work with all addon modules?
No, keep what you’ve got at the moment as it is a more stable version than the .tpl version for PHP 7.0 at this time. For the foreseeable future, phpVMS is being introduced and yes, it should be able to migrate your current database. In regards to the modules, you’d have to ask Nabeel, but I’m pretty sure they won’t work (at least straight out of the box anyway) due to the nature of the new framework (designed differently), and will require at the very least minimal tweaking or a complete recode. v4 will be the most up-to-date version (including PHP 7.0) at the time of its release, so it’s probably wise to stay where you are currently and wait for further progress.
Thanks Web, that was what I was thinking too. Just concerned about the error logs, as I now have an error due to the deprecated nature of php5.6. Everything seems to be running fine though.
Hello, I am getting the following error. this is a install on php7
Fatal error : Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /var/www/html/phpvms/core/classes/ezdb/ezdb_mysqli.class.php on line 277
Forgive a potentially stupid question, but how does this affect my current site. I am running phpVMS 5.5.x from SimPilot which is a .php version whereas this version that you have here is .tpl. Since I notice that my host still offers down to php 5.3 is this an immediate concern or do I have a while? Also, is phpVMS 4 going to be able to successfully migrate my current database, as well as work with all addon modules?
The goal is to have a migration, but modules/addons won’t work, since it’s a new system. Should be much more robust, though.
On 9/20/2017 at 6:41 AM, Capri said:
Hello, I am getting the following error. this is a install on php7
Fatal error : Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /var/www/html/phpvms/core/classes/ezdb/ezdb_mysqli.class.php on line 277
You/your host needs to increase the memory allotted to PHP
No, keep what you’ve got at the moment as it is a more stable version than the .tpl version for PHP 7.0 at this time. For the foreseeable future, phpVMS is being introduced and yes, it should be able to migrate your current database. In regards to the modules, you’d have to ask Nabeel, but I’m pretty sure they won’t work (at least straight out of the box anyway) due to the nature of the new framework (designed differently), and will require at the very least minimal tweaking or a complete recode. v4 will be the most up-to-date version (including PHP 7.0) at the time of its release, so it’s probably wise to stay where you are currently and wait for further progress.
Yep, the .tpl version update is mainly for the people who are running that copy.
Fatal error: 'break' not in the 'loop' or 'switch' context in /core/modules/ACARS/ACARS.php on line 176
I changed the php version to php 7.0 am using phpvms version 5.5.x by simpilot. I have checked that file and the line and there is a break there, but it is an if statement not a switch statement. I have been having trouble as I have had to move hosts and the new server is not letting me file pireps, using either acars program or manual.
Fatal error: ‘break’ not in the ‘loop’ or ‘switch’ context in /core/modules/ACARS/ACARS.php on line 176
I changed the php version to php 7.0 am using phpvms version 5.5.x by simpilot. I have checked that file and the line and there is a break there, but it is an if statement not a switch statement. I have been having trouble as I have had to move hosts and the new server is not letting me file pireps, using either acars program or manual.
I’m running 5.5.2 currently as well, and will need to migrate to PHP 7.1 on my VPS in the near future. Did you resolve your problems and have your site working as expected? Can you share any insight and code changes you had to do to make the transition?