My PHP version is : 7.3 My MySQL version is : 5.6.41-84.1
Upgrading/installing via: Web Cpanel
These errors are showing in the installer :
An error occurred while attempting to add default data: An exception occurred while executing ‘CREATE INDEX instagram_search ON leads (instagram)’: SQLSTATE: Syntax error or access violation: 1118 Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs
These errors are showing in the Mautic log :
[16-Jun-2020 07:37:42 UTC] PHP Warning: Class ‘Tightenco\Collect\Support\LazyCollection’ not found in [MAUTIC PATH]/vendor/tightenco/collect/src/Collect/Support/alias.php on line 19
[16-Jun-2020 07:37:42 UTC] PHP Parse error: syntax error, unexpected ‘=’ in [MAUTIC PATH]/vendor/tightenco/collect/src/Collect/Support/LazyCollection.php on line 611
Your problem My problem is : Not able to install Mautic on my subdomain
MariaDB 10.2, MariaDB 10.3, and MariaDB 10.4 function as limited drop-in replacements for MySQL 5.7, as far as InnoDB is concerned. However, the implementation differences continue to grow in each new MariaDB version.
MariaDB 10.0 and MariaDB 10.1 function as limited drop-in replacements for MySQL 5.6, as far as InnoDB is concerned. However, there are some implementation differences in some features.
Hmmmm - this is concerning. I thought that MaridaDB was a 100% drop-in replacement from MySQL.
Does this mean that we should ONLY be using MySQL for Mautic installations?
We have installed with MariaDB v10.3.22 and it “seems” ok… But we have not yet started to acutally use the software yet Also as there is no corresponding mathcing numbers between the two RDBMS - how is one to compare?
This is a discussion we are having in the Mautic 3 channel on Slack - as per the info above it seems they are becoming less a ‘drop in replacement’ as time goes on.
We are proposing:
Update the stats app in such way that we can see the amount of MariaDB installations
If a large number of users are using MariaDB, we could consider adding MariaDB to the Travis config (we currently only test against MySQL) so that we are notified automatically if a migration or feature is created that’s incompatible with MariaDB. Travis supports it: https://docs.travis-ci.com/user/database-setup/#mariadb
So we are actively looking into it as a result of this issue.
very interesting - I had no idea! It did not even dawn on me to even THINK about the differences between MySQL and MariaDB…Oh no…!!
I would be curious to see those stats too - as I guess most will just go with MariaDB as it is supposed tobe the “right one” and free of the big O’s nasty grip…
Ok - but on another tak - software like Nextcloud are “db agnostic” (sort-off) - I am surprised that given the big effort of the V3 re-write - and the proposed move to microservices - that this is hitched to MySQL - epsecially as it’s not exactly the most popular DB these days
Personally i like Pg (PosgreSQL) - a quality database, FOSS, and solid.
We had this issue too but moving to php 7.2 fixed it. Which version of php 7.2.x are you on that you still get the error?
You might want to confirm your PHP version a phpinfo() file in the root if you can’t access the server details in the settings area of Mautic. (Also you may need to disable htaccess to load the phpinfo php file in the root as the htaccess routes all requests to index)
Also if it is the right version make don’t assume its the same error causing the 500 error…make sure the error did not change to a memory error.
Actually @rcheesley I know why this might happen. Your install script replaces the .htaccess file with a newer version. Some hosts have a multi php feature that allows changing the php version in the htaccess file and in those cases as soon as the upgrade is done bam you get the 500 error because the code (something like this):
# php -- BEGIN cPanel-generated handler, do not edit
# Set the “ea-php72” package as the default “PHP” programming language.
AddType application/x-httpd-ea-php72 .php .php7 .phtml
# php -- END cPanel-generated handler, do not edit
Is deleted. Now I don’t know if this is something you need to handle or not but maybe it should be mentioned in the install docs or the install script compatibility check?