Breaks backend CSS

Hi @catmaniax,

Sorry about this issue. I’ll check on this issue.

And I’d appreciate if you provide a screen shot. Please find my email address here if you need.

Also could you try to specify wp-slimstat as exceptions at “Plugins area” in “Back-end target settings” section if you select “Prevent Zero-day Exploit“.

Thank you for your reporting!

I will try that and let you know.

Thanks ??

Hey, I can send you the screenshots but I cannot seem to find your email in the github link you posted before.

It’s a weird issue though… The CSS just now appeared broken again but after refreshing (hitting F5) it came back to normal…

Hi, email address disappeared on github ??

tokkonopapa at yahoo dot com

And also please copy and paste the result of “Show information” button at the bottom of “Plugin settings” section and send it to me.

Thanks for your cooperation!

Hey, just sent you the e-mail ??

Hello @catmaniax,

Thank you for your email.

I had tried to reproduce your issue, but found no direct cause. So I emulate the case that “/wp-content/plugins/wp-slimstat/admin/js/slimstat.css” was not loaded.

Success to load slimstat.css:

Fail to load slimstat.css:

I think the later screenshot is quite similar to your situation. And the point is sometimes this issue happens to you. So my assumption is that sometimes you fails to load slimstat.css.

And my solution is that please change the “UA string and qualification” in “Front-end target settings” section as follows:

Before change:

Google:HOST,bot:HOST,slurp:HOST
spider:HOST,archive:HOST,*:FEED
*:HOST=embed.ly,Twitterbot:US,Facebot:US

After change:

Google:*,bot:*,slurp:*
spider:*,archive:*,*:FEED
embed.ly:*,Twitterbot:US,Facebot:US

When “UA string and qualification” includes HOST or HOST=..., this plugin will fetch DNS reverse lookup which costs some server resources. This possibly makes your server busy and slimstat.css fails to be loaded.

This is the reason why I got 1 ★ review (thanks to @cinderellamancom, he changed it to 4 ★ review!).

I’d appreciate you to try the above.

Thanks for your sharing this issue.

Dear @catmaniax and all,

Thanks to @catmaniax, I found how to make this plugin compatible with Slimstat Analytics. Please refer to this topic.

Thanks.

Hi,

Jason from the Slimstat Support team here. @tokkonopapa, thank you so much for looking into this. @catmaniax had contacted us as well, to see if we could find a solution, so I installed your plugin in our sandbox, but I was not able to reproduce the issue (with the default settings in place). Probably because the sandbox we use has a local IP address and thus it doesn’t trigger the functionality your plugin provides. Great that you find a solution, I will make sure to add it to our knowledge base at https://docs.wp-slimstat.com so that other people will be able to find it there as well.

Cheers,
Jason

Hi @coolmann,

I’m sorry to get you involved in this plugin’s issue. And thank you for the information about your knowledge base!

And @catmaniax, I’d appreciate you to let me know if your issue would be solved or not.

Thanks!

Hello again and thank you for looking into this in detail!

This is your solution that seems to be working for me, as soon as I applied it:

Before change:

Google:HOST,bot:HOST,slurp:HOST
spider:HOST,archive:HOST,*:FEED
*:HOST=embed.ly,Twitterbot:US,Facebot:US

After change:

Google:*,bot:*,slurp:*
spider:*,archive:*,*:FEED
embed.ly:*,Twitterbot:US,Facebot:US

I tried this at first: ( https://www.ads-software.com/support/topic/slimstat-analytics-and-prevent-zero-day-exploit/ ), but didn’t make any difference and the issue still persisted.

Anyway, It will be great if you can implement in a future update the compatibility with IP Geo Block+Slimstat to work properly out of the box without any customization as the above, but I’m surely glad and grateful for your help!

Problem solved ??
If I see any weird behavior I will let you know.

Unfortunately, I’m back with this issue as it appeared again.
I then went to IP Geo Block’s settings and just pressed the Save Changes button without changing anything and the CSS worked instantly, weird huh?

I forgot to tell you from the beginning, that the broken CSS of Slimstat appears only in the basic wp-admin dashboard. If I visit the same widgets in Slimstat it works fine.
(……/wp-admin/admin.php?page=slimview1&ip-geo-block-auth-nonce=1e2b6daf54)

Anyway, I also wanted to ask you something else.
I saw in the statistics of IP Geo Block that today it blocked 11 visits coming from US and Germany (they were trying to visit POST[443]:/wp-admin/admin-ajax.php), even though I have not set the plugin to block those countries.
Any idea why?

Thank you.

• This reply was modified 7 years, 10 months ago by catmaniax.

I just found another irritating bug.
I’m using “Imagify” to automatically compress images on upload, and if IP Geo Block is enabled then it does not automatically compress the images, I have to do it manually through the Gallery.

I would be grateful if you could look into this so I can resolve it.
Thanks again.

Hi,

I then went to IP Geo Block’s settings and just pressed the Save Changes button without changing anything and the CSS worked instantly, weird huh?

I found either no issue and no relation between Slimstat CSS and IGB. So please back to the basic: Deactivate all the plugins and activate only Slimstat and IGB. Too many plugins (you send me a list of 87 plugins) also may cause this issue. The same as I described here could be happened.

And also please try some kind of developer tool in your browser. For example, Chrome has Network Panel. You can find the css is successfully loaded or not like this:

—

Regarding the blocking from US and Germany, which target do you find the blocking? If you find them in XML-RPC, please select “Disable” as “XML-RPC” at “Back-end target settings” section. Or you can find the list of reason of blocking: Record settings and logs.

Thanks.

Hi again,

Thank you for reporting the issue about “Imagify”. Unfortunately, I have no time now, but I’ll check it at night. For the time being, please select “Imagify” as “Exceptions” at “Plugins area“.

I think this is not a bug but a specification and a limitation of this plugin.

And also please check the list of reason of blocking: Record settings and logs. This may help us to find the best configurations for your site.

I’m sorry about many issues on your site. I’ll try to solve them one by one.

Thanks for your cooperation.

I’m following this thread, please mention my handle if you guys find a solution.

Best,
Jason