WPReady
Forum Replies Created
-
Current version 1.7.67 adrressed the problem you mentioned. Give it a try.
Well, that is discarding the theme as suspect.
I’ll be digging around and I’ll let you know if I get anything.I finally got something but this would be different from your scenario.
On one particular site, the Maxmind file downloaded, but finally ended up with 0KB each time.Straight to the solution, the theme had a small code rejecting any requests to the api core to improve speed. I took this example from Konstantin Kovshenin a WP guru:
add_filter( ‘pre_http_request’, ‘__return_true’, 100 );
The code is intended to use on local environments to avoid external calls to Internet and to improve development speed (it works quite alright) but accidentally went through production. This code disabled any attempt to update anything, like some sort of protection, included plugins updates like Statcomm.
This caused the same effect you are describing. Even this wouldn’t be your case, did you try to change your theme (to default theme for example) and see if Maxmind file downloads?
Forum: Plugins
In reply to: [StatComm (StatPress Community) Multisite Edition] A couple of possible bugsWhoops..!
I will release a fix shortly, and I will correct your alias there. My apologies.I confirm that serialization/deserialization has a problem that should be fixed before proceed.
If I fix this problem would you volunteer to test it? I would appreciate very much but you should consider the risk involved.
Thank you for your feedback.
According to the changes I made I narrowed the problem to 4 suspects ‘suppossedly’ to be minor:
1-A fix consisting a variable serialization/deserialization to avoid some problems with different PHP installations.
2-A fix to make the plugin relocatable.
3-A fix to call deactivate_plugins on older versions. this code is activated ONLY if we try to install the plugin in a WP version <3.3. I guess we can discard this case.
4-An important side effect affecting multisite plugins. The fix is very simple and I still believe this is not causing the problem, but I can’t discard anything.
So my guesses are options 1 and ‘maybe’ (?) 2 and maybe 4 (?).
While I’m going to make a few round of tests, I have a risky proposition for you, so I understand if you decide to decline it.
What I suggest to solve this riddle is to enable debug and see the error produced when you activate the plugin.
To do that you should insert this line on wp-config.php:
define(‘WP_DEBUG’, true);
and after that try to activate the plugin. That will bring down your site and will display the error. Write it down asap and rename the statcomm plugin folder to reactivate the site (You need FTP access to recover from the problem). That would deactivate the plugin at once and you’ll recover from the error in no time.
It is a wacky proposition , I know.
I really appreciate all the details you’re providing to pinpoint the problem. You stated clear from the beginning. This information is very useful to lead me to the issue.
I’m in the process of comparing what would be the cause and I’ll let you know asap. My sincere apologies for the problem.
The only improvement made to multisite was an important fix discovered last week. This problem affected kept other multisite plugins from running properly.
Before launching the plugin to the public, it is tested on multisite and single site environments. I’m confirming that multisite should worked smoothly. Otherwise it can’t be released.
So my guesses are the problem would be related with the fix mentioned above or there is some issue when the plugin was reinstalled.
I have confirmation from ten sites that single installation solved most of the problems from previous one.
I’ll be in contact if I found anything.
Hi mdunham,
thanks for your comments.
I’m checking what is happening.Forum: Plugins
In reply to: [StatComm (StatPress Community) Multisite Edition] A couple of possible bugsHi GermanKiwi,
Point 1 is a fix included on the next version (this week).
Second point it seems I got a mistake uploading the plugin, although I’m looking what caused.
Thanks for your feedback.Forum: Plugins
In reply to: [StatComm (StatPress Community) Multisite Edition] StatComm crashed my siteHello AmbroseMugwump,
Statcomm would need WP 3.3 and above to be installed. When the plugin detected this version was old enough, he tried to uninstall himself, which
caused the error. My apologies for that.I corrected this problem for the next version to be released this week.
On to the other problem (mdunham’s issue), there is an object it needs to be serialized prior assignation. This has been corrected for the version will be released this week.
Thanks for your feedback!
Forum: Plugins
In reply to: [StatComm (StatPress Community) Multisite Edition] mutisite erroreHi fisherofer,
thanks for your suggestions, I will work on those requests.Forum: Plugins
In reply to: [StatComm (StatPress Community) Multisite Edition] mutisite erroreHi fisherofer,
Thanks for letting me know.
Current Statcomm version has a limitation. It only installs on existent network sites. But if you create a new network site, the plugin won’t detect it, and it won’t work in the new site.If this is your case, I would recommend to reinstall the plugin to fix the problem. Please let me know if we are dealing with a different situation.
Forum: Plugins
In reply to: [StatComm (StatPress Community) Multisite Edition] A couple of possible bugsHi GermanKiwi,
thanks for your comments and suggestions.
1) certainly I will take a look
2) I’m currently checking what happened.I will release a fix for these and other issues this week.
Forum: Plugins
In reply to: [StatComm (StatPress Community) Multisite Edition] StatComm crashed my siteI’m very sorry to hear that. In the meantime I’m digging into the plugin to find a way to avoid this problem, if possible.