kevinff

Hello Jeremy,

Is the background request only used to display the related posts? nothing more? So caching that background request wouldn’t affect the content of the related posts (apart from delaying it) ?

I understand you want to make things quicker, but it’s really a lot more backend load, why not proposing to make a wp-cron every X minutes to load this data? If caching is enough it is fine for me, however i guess 99% of people do not use any frontend cache.

Thanks for your explanations

Yes unfortunately we cannot do that, had to comment the lines in the plugin ??

Tried to disable SFS and re-check login/signup, and it seems to work thx.

Same here.
Didn’t try to disable deny spammers, but i disabled checks at login.
In the admin page i had this written for my IP “cached bad ip”.

Well i reopen, it seems to be some kind of bug anyway and i’d like to know what was wrong.. as in the admin panel it shows sidebar-1 sidebar-2 sidebar-3 fine, it’s just broken in the db.

Ok checked the db, it seems to add it as “sidebar-%d” in it, even though it works in template tags..
Better forget this trick.

Hi!
I saw that the charts don’t appear in IE8, i also saw they fixed something about it in jquery flot, don’t know if it fixes it though..

Also in Multisite it would be great that users are not allowed to modify the path of the .js file (otherwise it’s a security issue).

Just giving you some updates of what i find, i love your plugin ??

Kevin

Hello camu,

Here’s what i get when activating a new blog with the latest slimstat version and multisite wp:

Fatal error: Using $this when not in object context in /*******/wp-content/plugins/wp-slimstat/wp-slimstat.php on line 101

It doesn’t create the slimstat tables, but it might be because of this error..

Your latest version seems to be working!!! ??
Thanks a lot Camu!

Maybe i wasn’t clear: in the main site there are the slimstat tables but not in the new users blogs (stat, visits..)

No improvement, sorry ??
I’ve installed wp 3.2, enabled multisite with subdomains, installed wp-slimstat.
Then created a new user + new blog, activated.. And no, no slimstat tables ??
I’ve also tried with the proper-activation-plugin..
Sorry ??

Well that last update made it worse for WPMU installs ??
Now i don’t even have 1 table created. I read that the new network activation is experimental so i’m not too worried ??

I wish i knew more about this part of wp, i would be glad to fix it..

Nevermind.. I didn’t know this was the expected behaviour and that i had to change the options.. thanks!

If someone has “registered” access in a blog, the slimstat menu appears for him:
https://img862.imageshack.us/img862/7629/captureslimstat.png

Well, in my case, i have a wordpress multisite install, and in the main site, the users are registered as “registered”, and somehow the wp-slimstat entry in the dashboard appears in the admin panel of the main site, so they can view the stats of the main site!
So i think there’s a small problem here..

Just to say that i still had to modify wp-slimstat with version 2.4.2, as the stats table was not being created :s
Also i noticed that you added a check on the referer. It gave me problems with domains mapped with the domain mapping plugin. I changed this in wp-slimstat-js.php:
Search for something like this “if (empty($_SERVER[‘HTTP_REFERER’]) || ((strpos($_SERVER[‘HTTP_REFERER’], $site_url) === false”

And i replaced the full line with:
if (empty($_SERVER[‘HTTP_REFERER’]) || ((strpos($_SERVER[‘HTTP_REFERER’], $site_url) === false ) && strpos($_SERVER[‘HTTP_REFERER’], “https://” . $_SERVER[‘HTTP_HOST’]) === false ) ){

Hope it helps somebody again ??