Mattias

You can’t change the RSS icons url. Atm the RSS automatically use the get_bloginfo( “rss2_url” ) WordPress function to get the RSS url.

I could look into the possibility to make the URL changeable, but no promises it will be added.

No, the plugin use wp_embed_register_handler() method to register the embed. So the conversion of the link to embed is done before the post/page content is give to the view/html.

Hi @userahn

The plugin does not do any modification to any files, and it is therefore impossible for it to permanently change something.

The issue, as you also updated the post with, is related to cache. Refreshing the cache is always recommended when you have installed/uninstalled a plugin.

Sry for late reply. I have noted the issue and added it to my todo list https://github.com/darkwhispering/Advanced-Browser-Check/issues

I’ll let you know when updated.

Might be possible with some custom CSS. but there is no option in the plugin for it.

What exactly the CSS would need to be I do not know at this time.

Can you please turn on debug for said browsers and post the result here please.

Also, what Windows OS version are you using?

Unfortunately the links you shared are not related to how to have a website detect what extensions are installed in a users browser.

There is no way for a website to do this kind of detection mainly due to privacy concerns as you would be able to get a list of every users extensions and by so also potentially track and collect data about specific user behavior and more.

An extension however can alter HTML on a webpage, making it look like the website detected the extension, when it was actually the opposite happening.

Seems like I missed adding this change to the changelog. It was included in version 4.4.0

Please don’t create new support thread for an issue that you already know exists and posted in!

See my answer in the other thread: https://www.ads-software.com/support/topic/wont-active-error/

@limcoh If you have the exact same error as described in the original post you aren’t running the latest version of the plugin. The latest version, 4.4.1 should resolve the issue for you.

If you can’t access your admin dashboard and you are sure it is due to the Advanced Browser Check plugin, just access your site over FTP/SFTP and delete the plugin manually. You should then be able to access admin and then download the latest version of the plugin.

Hmm, if that is the case I don’t know what is going on and to be able to try and figure out I would need to debug your site specifically.

What you can try, if possible:
– Remove my plugin and install it again.
– Disable all other plugins and see if it works.
– Try with another theme.

The best would be if it is possible for you to do a duplicate of your site and do the testing there.

Ah, yeah, your .htaccess protection will prevent the ajax call to success and unfortunatly render my plugin useless for you. ??

The “display:none;” is hardcoded in the plugin html code. If it is not present in your sites source code is has been removed by Javascript.

I can see 2 possible scenarios

1. The plugin settings are set to detect the browser you visited the page with, but for unknown reasons the plugin ajax call the did not return any html code, and therefor no popup.
2. Another plugin/theme removes the display:none; from the Advanced Browser Check div.

If you can, it would help a lot if you can check if the plugin is doing the AJAX call or not. You can do so in Chrome by right click on your site and select “Inspect”. Then select the “Network” tab and “XHR” filter (it’s in the list of with All, XHR, JS, CSS and so on.
Refresh the site and see if there is a call to “admin-ajax.php”. If there is, click on it and see what the response looks like.

Regarding the debug, you are correct, it is by design. Debug merely just add the debug above the regular popup content.

I’m glad you like the plugin and find it useful. The download link for IE has been updated in the last version.

Hi again @armando_e @davidoshiro

I have just updated the plugin to v4.4.1 fixing the issues reported.

I’m again very sry for the issues caused by my plugin. The change of PHP version requirements was unintentional (force of habit using [] in newer PHP versions and not having PHP 5.3 installed locally to test on). If you still get errors, please let me know and I will fix them asap.

Minimum PHP version supported for the plugin is PHP 5.3 though, just FYI.

Note: I really do encourage you to update to a newer version of PHP if your hosting provider allows. PHP 5.3 is no longer supported and therefore don’t get any security updates.