I have been making some updates and checking configurations. When I go to Newsmag/System Status it tells you or is supposed to tell you the php.ini configuration. As far as I can tell it does not read the configuration correctly.
NewsMag States:
php.ini configuration
Server software i Apache
PHP Version i 5.6.31
post_max_size i 128M – You cannot upload images, themes and plugins that have a size bigger than this value. To see how you can change this please check our guide here.
max_execution_time 600
max_input_vars 1000 – the max_input_vars should be bigger than 2000, otherwise it can cause incomplete saves in the menu panel in WordPress. To see how you can change this please check our guide here.
SUHOSIN installed false
mbstring available
After downloading and checking my php.ini file here are the actual settings:
;;;;;;;;;;;;;;;;;;;
; Resource Limits ;
;;;;;;;;;;;;;;;;;;;
max_execution_time = 300 ; Maximum execution time of each script, in seconds
max_input_time = 1000 ; Maximum amount of time each script may spend parsing request data
memory_limit = 256M ; Maximum amount of memory a script may consume (32MB)
max_input_vars = 4000
upload_max_size = 64M
post_max_size = 64M
upload_max_filesize = 64M
Shouldnt they be exactly the same? This same thing is true when Newsmag attempts to read the settings for WordPress. I think this is very important and should be consistent
Local PHP settings on your hosting may not match server over-rides, or hosting panel settings. Normally with any *good* hosting service you should have a hosting panel where you can see/set your PHP settings, version, etc. This is normally where you’d see your *actual* live php settings.
The theme is picking up that info from querying the current php settings as ‘reported’ by the server for your local install.
You can do the same by putting a simple php query file in your public root and then reading that in your web browser.
To read your actual php settings
create an empty text file, name it
phpinfo.php
put this at top of text file, and nothing else
<?php
phpinfo();
?>
Put the file in your root directory via FTP (same place your WP install is, or whatever).
Load that via web browser
mysite.efg/phpinfo.php
this will load the actual php settings as reporting by your system, for your specific site as well as overall server settings used by your site.
This should probably be in the them docs someplace, but there you go.
Theme is querying and posting the same data you see running that php ‘query.’ So, theme is not ‘making it up’ from some random info source. 🙂
Hope that helped. I don’t work here.
Hmm,
Well I have a vps so I have set and assume I can control all my defaults now Im lost LOL.
Shouldnt what is set on the server go to the php.ini file?
This is what is in my WHM Teak Settings PHP
cPanel PHP max execution time (Minimum: 90)
90 s default
180
s
cPanel PHP max POST size (Minimum: 55; Maximum: 2,047)
55 MB default
2000
MB
cPanel PHP max upload size (Minimum: 50; Maximum: 2,047)
50 MB default
1000
MB
cPanel PHP loader
ioncube
sourceguardian
zend
This is what is in the cPanel for the site
max_execution_time This sets the maximum time in seconds a script is allowed to run before it is terminated by the parser. This helps prevent poorly written scripts from tying up the server. The default setting is 90.
300 ; Maximum execution time of each script, in seconds
PHP Default: 90
max_input_time This sets the maximum time in seconds a script is allowed to parse input data, like POST, GET and file uploads.
1000 ; Maximum amount of time each script may spend parsing request data
PHP Default: -1
max_input_vars This sets the maximum number of input variables allowed per request and can be used to deter denial of service attacks involving hash collisions on the input variable names.
4000
PHP Default: 1000
memory_limit This sets the maximum amount of memory in bytes that a script is allowed to allocate. This helps prevent poorly written scripts for eating up all available memory on a server. Note that to have no memory limit, set this directive to -1.
256M ; Maximum amount of memory a script may consume (32MB)
PHP Default: 128M
session.gc_maxlifetime This specifies the number of seconds after which data will be seen as “garbage” and potentially cleaned up.
1440
PHP Default: 1440
session.save_path session.save_path defines the argument which is passed to the save handler. If you choose the default files handler, this is the path where the files are created.
/tmp
PHP Default: /var/cpanel/php/sessions/ea-php56
upload_max_filesize The maximum size of an uploaded file.
128M
PHP Default: 2M
So,
you’re saying the info reported in the theme panel is different than what you see in the phpinfo.php print out on screen ?
Yes that is correct. In the Theme Panel in the Admin area one of the System Status says input variables are 1000, that is not correct and does not match the phpinfo.php file which says 4000
http://thevoiceoflakecounty.com/phpinfo.php
I havent gone through all of them, but typically where there is one error there could easily be another
SO, it definitely is not reading the input variables correctly. I adjusted other items that display in the System Status area and they updated and showed correctly. That vaiable never changes no matter what it is changed to.
Also in System Status it says it has deactivated the TAG DIV Booster, it never deactivates. It says it has a confict with the WP Orion Worker Plugin (Unfortunate)
Well, it may not match the php.ini file, but should match the example file I provided.
However, if you *know* the system settings are correct on server, then it’s really immaterial to anything as the theme is reading that from your system, so the system is reporting the wrong info — but if it’s correct on the backend, that is all that matters if the resources are “actually” available.
Also, per the theme docs, if you know the WP Orion plugin doesn’t conflict, you can simply add it t o the TD Booster plugin whitelist.
I don’t work here, just some feedback as I’ve been managing my own Linux servers since Jan. 1996.
The phpinfo.php file when you run it will show the ‘actual’ PHP settings for your single domain/site. If not, then your system is mis-configured.
Understand but if they are going to have a Theme Status panel it should read things correctly. It is my opinion as well as two others that have gone in and checked this that it does not read ALL the information correctly and accurately.
Like it says it has deactivated the TAG DIV Speed Booster because its not compatible with WP Worker. Then you go look at your plugins and it is Active. Sorry but that makes no sense to me.
Where do you whitelist a plugin?
Um; it means that the TagDiv Booster function capability has been disabled, if you look at your page source you’ll see that — it doesn’t mean your plugin was ‘disabled.’ Two different things.
Again, the theme pulls the data from a query to your php settings via the php query command, it’s not inventing that data.
Anyway — not my problem. Good luck!
