Wordpress/php issue
-
Are you sure that WordPress is calling PHP7 rather than 5.6?
-
@scottalanmiller said in Wordpress/php issue:
Are you sure that WordPress is calling PHP7 rather than 5.6?
It is calling 5.6 because the limit for file uploads is set to 8MB in 5.6 and 20MB in 7 and when I go to media in wordpress it shows that the limit is 8MB
-
@scottalanmiller said in Wordpress/php issue:
Are you sure that WordPress is calling PHP7 rather than 5.6?
@wls-itguy said in Wordpress/php issue:
@scottalanmiller said in Wordpress/php issue:
Are you sure that WordPress is calling PHP7 rather than 5.6?
It is calling 5.6 because the limit for file uploads is set to 8MB in 5.6 and 20MB in 7 and when I go to media in wordpress it shows that the limit is 8MB
The other odd part is I changed the upload limit to 15 in 5.6 and it still shows 8MB
-
@wls-itguy said in Wordpress/php issue:
@scottalanmiller said in Wordpress/php issue:
Are you sure that WordPress is calling PHP7 rather than 5.6?
@wls-itguy said in Wordpress/php issue:
@scottalanmiller said in Wordpress/php issue:
Are you sure that WordPress is calling PHP7 rather than 5.6?
It is calling 5.6 because the limit for file uploads is set to 8MB in 5.6 and 20MB in 7 and when I go to media in wordpress it shows that the limit is 8MB
The other odd part is I changed the upload limit to 15 in 5.6 and it still shows 8MB
systemctl restart apache -
@black3dynamite said in Wordpress/php issue:
@wls-itguy said in Wordpress/php issue:
@scottalanmiller said in Wordpress/php issue:
Are you sure that WordPress is calling PHP7 rather than 5.6?
@wls-itguy said in Wordpress/php issue:
@scottalanmiller said in Wordpress/php issue:
Are you sure that WordPress is calling PHP7 rather than 5.6?
It is calling 5.6 because the limit for file uploads is set to 8MB in 5.6 and 20MB in 7 and when I go to media in wordpress it shows that the limit is 8MB
The other odd part is I changed the upload limit to 15 in 5.6 and it still shows 8MB
systemctl restart apacheDebian moved to systemd?
-
@black3dynamite said in Wordpress/php issue:
@wls-itguy said in Wordpress/php issue:
@scottalanmiller said in Wordpress/php issue:
Are you sure that WordPress is calling PHP7 rather than 5.6?
@wls-itguy said in Wordpress/php issue:
@scottalanmiller said in Wordpress/php issue:
Are you sure that WordPress is calling PHP7 rather than 5.6?
It is calling 5.6 because the limit for file uploads is set to 8MB in 5.6 and 20MB in 7 and when I go to media in wordpress it shows that the limit is 8MB
The other odd part is I changed the upload limit to 15 in 5.6 and it still shows 8MB
systemctl restart apacheThere should a be a 'No $hit' button for replies like that :). I did that also and actually rebooted the server. Still nothing.
-
@jaredbusch said in Wordpress/php issue:
@black3dynamite said in Wordpress/php issue:
@wls-itguy said in Wordpress/php issue:
@scottalanmiller said in Wordpress/php issue:
Are you sure that WordPress is calling PHP7 rather than 5.6?
@wls-itguy said in Wordpress/php issue:
@scottalanmiller said in Wordpress/php issue:
Are you sure that WordPress is calling PHP7 rather than 5.6?
It is calling 5.6 because the limit for file uploads is set to 8MB in 5.6 and 20MB in 7 and when I go to media in wordpress it shows that the limit is 8MB
The other odd part is I changed the upload limit to 15 in 5.6 and it still shows 8MB
systemctl restart apacheDebian moved to systemd?
Yes
since Debian 8 -
I use it for my Ubiquiti stuff only. and that is barely touched.
-
Instead of uninstalling php5, just disable it.
# Disable php5 enable php7 a2dismod php5 a2enmod php7 systemctl restart apache2.service -
Weird but working now. I went back in the ini file for 5.6 and changed it to another #, saved it, restarted service, went into wordpress and it didn't register. Went back to ini in 5.6, changed it again, saved, and restarted services and this time it did register. WHATEVER!
@black3dynamite said in Wordpress/php issue:
Instead of uninstalling php5, just disable it.
# Disable php5 enable php7 a2dismod php5 a2enmod php7 systemctl restart apache2.serviceWell, that sure makes things easier
