203X

Yep… FTP’d all 7 sites I maintain (burst broke my woocommerce shop too) and replaced class-endpoint.php – now it’s all good again. Thanks.

With that update you broke 6 websites I maintain as a volunteer… can’t login and the websites only showing the critical error page. Not funny. Even when updating the plugin while being logged in, it kills the page.

• This reply was modified 2 years, 4 months ago by 203X.

Thanks for the reply. It was and is PHP 7.4 all the time.

The plugin is faulty in various ways. I don’t know why it displays the content faulty by now. All those years it worked. I edited all content in the sliders that was misformated by a club member, but still the plugin displays stuff wrong at the page of the dogs who got adopted. The placing of the arrows sucks too IMO and we got 105 sliders now for that shortcode, and in the WP backend it seems like those 105 sliders are too much to handle for the backend… it get’s slow and glitchy and stutters. Seems like the script is not made for so many sliders. My high end PC starts heavy working on the page with those 105 sliders in the backend of WP.

https://www.hundefreunde-ev.de/vermittelte-hunde/

• This reply was modified 2 years, 4 months ago by 203X.

I installed the latest plugin update that came in today and now it works again. Images are shown now. Thanks.

• This reply was modified 2 years, 4 months ago by 203X.

Thanks for your reply and the provided information, Sir. It is appreciated.

And you did it again. The plugin was updated and because of the hotlink protection the content on my other domains using the same webspace is now unavailable. So tomorrow I’ll have to edit my htaccess again. I’ll look for other security plugins now. Lately your product causes more and more problems. I always have to fix stuff after you update AIO WPS.

See, I need it like this:

#AIOWPS_PREVENT_IMAGE_HOTLINKS_START
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{REQUEST_FILENAME} -f
RewriteCond %{REQUEST_FILENAME} \.(gif|jpe?g?|png|svg|css)$ [NC]
RewriteCond %{HTTP_REFERER} !^http(s)?://(.*)?\.t-ryder\.de [NC]
RewriteCond %{HTTP_REFERER} !^http(s)?://(.*)?\.menetekel\.net [NC]
RewriteCond %{HTTP_REFERER} !^http(s)?://(.*)?\.iheartshit\.de [NC]
RewriteCond %{HTTP_REFERER} !t-ryder\.de [NC]
RewriteCond %{HTTP_REFERER} !iheartshit\.de [NC]
RewriteCond %{HTTP_REFERER} !menetekel\.net [NC]
RewriteRule \.(gif|jpe?g?|png|svg|css)$ - [F,NC,L]
</IfModule>
#AIOWPS_PREVENT_IMAGE_HOTLINKS_END

But it was reset to:

#AIOWPS_PREVENT_IMAGE_HOTLINKS_START
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{REQUEST_FILENAME} -f
RewriteCond %{REQUEST_FILENAME} \.(gif|jpe?g?|png|svg|css)$ [NC]
RewriteCond %{HTTP_REFERER} !^http(s)?://(.*)?\.t-ryder\.de [NC]
RewriteCond %{HTTP_REFERER} !t-ryder\.de [NC]
RewriteRule \.(gif|jpe?g?|png|svg|css)$ - [F,NC,L]
</IfModule>
#AIOWPS_PREVENT_IMAGE_HOTLINKS_END

And as this happened I was coding on the other domains content and did not realize what’s going on and thought I messed up my CSS/HTML and almost gone nuts!

OK, I just translated the missing stuff. Hope it’ll be updated soon.

I solved all now using FTP, deleting the plugin, reinstalling it.
Permalinks are https://www.tld.com/sample-post/ but I found out now that I had saved
bookmarks to the custom login URL like https://tld.com/custom-loginxyz and suddenly for some sites it was changed by the plugin to the actual folder structure on the server like tld.com gives the page, but the wordpress location is e.g. tld.com/cms/ so the login page URL had changed to https://tld.com/cms/custom-loginxyz which I did not know. Until the plugin updates all worked with my existing bookmarks. My bookmarks were https://tld.com/custom-loginxyz which worked without the folder in the URL. Welp… what do I know.

I did for none of the sites use the cookie-based brute force protection and I got no secret word. I only used login page rename and other sec. features

• This reply was modified 2 years, 6 months ago by 203X.

I uninstalled the plugin via Plesk, installed latest version again, did config all settings again. Set up custom login page URL again. But for the other website for which I don’t have FTP I gotta wait and ask the admin. And I’m scared now to update my other 3-4 pages for which I also use All In One WP Security & Firewall. My site did not work even after the Plesk plugin updates to 5.0.4 and I don’t want to mess up the other sites. The other sites are projects for which I have a volunteer honorary admin promise and it will be no fun to fix all by uninstalling via FTP, reinstall and set all configs again.

For one site I was able to update the plugin to 5.0.4 via Plesk WP module, deleted cache via FTP but still I can not use my custom login URL. Locked out.

Thanks for the explanation, Sir. A hint regarding that at the big Burst cookieless setting DIV would be nice. As it is now it can be confusing for admins and visitors (especially if admins create their own cookie hint texts regarding tracking).

I mean, if I open a new clean session in chrome without being logged into my WP backend, I can accept cookies, then the burst UID cookie is set – but why? Is the cookieless tracking option in burst misleading? At the cookie policy one can read it’s a tracking cookie. If I deny at the cookie hint, the cookie is not set – which is OK, but if accepted it should not be there at all, since I chose cookieless tracking.