[email protected]
Forum Replies Created
-
sysinfo also reported PHP 5.2.17 (although cPanel still reported 5.3.2)
Contacted host – they ‘fixed’ it and current version of your plugin is now working just fine.
Thanks!
Simple Calendar could not be activated.
Required PHP version: 5.3.2 – Version found: 5.2.17
Please update to meet Simple Calendar requirements.As of Simple Calendar 3.03 I’m still unable to activate the plugin
HELP!!
Yes. 100% certain server is running PHP Version 5.3.29
I can’t post System Report because “plugin could not be activated”.
That worked, Gilligan. Thanks.
Same sort of problem – options set in plugin dashboard are ignored on output – sites checked for exclusion in dashboard are shown on report – how can I suppress listing of excluded sites in shortcode?
Please repair plugin so that sites marked excluded are actually excluded (and repair plugin to pay attention to options set from dashboard).
Thanks!
Daniel – I applied your fix from github at https://github.com/convissor/login-security-solution – that seems to have done the trick. Thanks so much for your prompt attention!
Mike
Forum: Plugins
In reply to: [Plugin Name: Traffic Stats Widget Plugin] Unexpected textLines 297 and 329 had the trailing space in my file…
Good catch – thanks so much, jens.bjork and realtech !!
Forum: Fixing WordPress
In reply to: can't save settingsmy host reports that they could see that one of the server mod_security settings was causing the issue – they ‘white listed the rule’ and all is now working normally.
Thanks all of you for your concern and assistance – problem is resolved.
Forum: Fixing WordPress
In reply to: can't save settingsNope, I have nothing like
define( ‘WP_SITEURL’, ‘https://’ . $_SERVER[‘SERVER_NAME’] . ‘/path/to/wordpress’ );
in config.phpForum: Fixing WordPress
In reply to: can't save settings[Thu Mar 27 17:05:45 2014] [error] [client 108.212.220.217] File does not exist: /home/cecily/public_html/403.shtml, referer: https://cecilypalamara.com/wp-admin/options-general.php
[Thu Mar 27 17:03:39 2014] [error] [client 108.212.220.217] File does not exist: /home/cecily/public_html/403.shtml, referer: https://cecilypalamara.com/wp-admin/options-general.php
[Thu Mar 27 16:48:24 2014] [error] [client 108.212.220.217] File does not exist: /home/cecily/public_html/404.shtmlThese are the only errors – this is a second brand new fresh out of the box site on the same server with same symptom…
Forum: Fixing WordPress
In reply to: can't save settingsPrior to .htaccess, I was getting this error when I tried to save Settings/General:
Maybe that will help?
Forbidden
You don’t have permission to access /wp-admin/options.php on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Forum: Fixing WordPress
In reply to: can't save settingsThis is a new install – no changes to theme or plugins – it’s exactly the way wordpress woke up.
sigh
I can, of course, manually upload the site, but… As I mentioned, I suspect that this is either a .htaccess problem or server or PHP setting or the like. What could cause this behavior?
Forum: Fixing WordPress
In reply to: can't save settingsExactly same behavior in Chrome, IE, FireFox, Safari
??Forum: Fixing WordPress
In reply to: the text 'exit' in body of page crashes with 404 during 'save page'Thanks, esmi! You were right on the button. Here’s an explanation from my host:
When we checked the apache error log we could see that there were some mod security rule conflicts on the server. Then we have whitelisted the rule id on the server. Please see the below log snippet for more details:
=====
[Thu Oct 10 10:07:11 2013] [error] [client nnn.nnn.nnn.nnn] ModSecurity: Access denied with code 403 (phase 2). Pattern match “(passthru|^cmd|fopen|exit|fwrite)” at ARGS:content. [file “/usr/local/apache/conf/modsec2.user.conf”] [line “89”] [id “600067”] [hostname “bachariasoloists.com”] [uri “/wp-admin/post.php”] [unique_id “UlbCnkPebqsAAEfYHlAAAABJ”]
=====The rule with the id id “600067” has been whitelisted for the domain. This fixed the issue.