Giorgos Sarigiannidis

Actually, you don’t need to update jQuery but to remove the theme’s old version. WordPress will load the proper version anyway, which is considered the best practice.

Depending on the theme, this could be achieved with any of the following:
– via some option that might exist in the Theme’s Options page (it is very likely, though, that the theme might not have such an option)
– using wp_deregister_script() (supposing, of course that your theme used “wp_enqueue_script()” to load its jQuery, which is the proper way to do so in WordPress)
– If the theme includes hardcoded jQuery (which is a bad practice) you can just find it, usually in header.php or footer.php and remove it.

There is a chance that the theme loads old jQuery because some of its functions depends on it and can’t work with newer versions. If such is the case, then, indeed, there is not much you can do about it. Otherwise it would be better to use WordPress’ default jQuery from every aspect (security, performance, stability etc).

For further reading on the subject you can check the following resources:
https://justintadlock.com/archives/2009/08/06/how-to-disable-scripts-and-styles
https://pippinsplugins.com/why-loading-your-own-jquery-is-irresponsible/

Anyway, thank you for your feedback and for testing Slidr!

There might be some conflict with the theme or some other plugin. The one thing that I noticed when I viewed the source code is that your theme loads an older version of jQuery, while WordPress itself loads the proper one too.

If you have a local version of your site where you can perform tests, could you please try the following:

– Try to disable all other plugins and check if the carousel works. If it does, enable them one by one until you find which one conflicts.
– If the above doesn’t work, try switching themes but keep all your plugins active. If it does solve the problem, then there probably is a conflict with your theme.
– Finally, see if you can prevent the theme from loading its own jQuery and let WordPress handle it.

BTW, I don’t know if you are aware but in your footer there are two hidden links leading to porn pages (check screenshot: https://imageshack.com/i/eyXIfUxKp ). I suggest that you should also check your site for suspicious activity and find what injected those links.

Hello,
Which type of content would you like to display? Recent posts of a specific category, for example, or something else?

Also, which shortcode do you use in your post? Just [slidr] or did you include some other parameters?

Hi,

If you’re viewing the DOM using Chrome’s Developer Tools (or any other Browser’s dev tools), you won’t see the encoded text because it’s already converted to readable text.
To test it, you should view the actual source code of the page (to do so, right click anywhere on the page and click “view page source”).

In your case, this is what I see when I view the source of your homepage: https://imageshack.com/i/eyDEpNEWp

By the way, keep in mind that this function encodes only portions of an address, and does so randomly so the letters encoded are different each time the page loads. For more details on how it works, visit https://codex.www.ads-software.com/Protection_From_Harvesters

I’ve added the changes mentioned above to the latest update of the plugin.

Thank you for your feedback!

Is there any chance that you use some Chrome extension that affects the page’s appearance? In my case, Chrome behaves exactly like IE in that matter and the only browser that automatically fixes the issue is Firefox.

For the first part: If you don’t mind doing some beta testing, you can replace the file /js/jquery.remove-uppercase-accents.js in the plugin’s folder with the one I am attaching here: https://dl.dropboxusercontent.com/u/38634/Various/jquery.remove-upcase-accents.js?dl=1

It should do what you want but it’s still untested, so I would appreciate your feedback.

On that note, I suggest that you keep a backup of the original file, in case you want to restore it.

Regarding B) – I am afraid that I can’t do anything about the delay. The plugin “reads” the contents of the page and when it finds text transformed via CSS it fixes it. Therefore, in order to work it needs to wait until the page is fully loaded.

The plugin has been updated and now it includes an additional option to hide Jetpack from non-admins.

Hello and thank you for your feedback.

I just tested it locally and it seems that you can hide the Contact form 7 by simply adding “Contact” at the Custom excludes field (first letter uppercase, no blank spaces).

Unfortunately, Jetpack is a different case and I couldn’t find a quick workaround to hide it directly from the Custom excludes field. Perhaps I could update the plugin and add extra options for some very popular plugins such as Jetpack, but it will take some time for me to release it.

Meanwhile you can try some of the options mentioned here: https://www.ads-software.com/support/topic/security-problem-detected-please-hide-jetpack-admin-menu-for-subscriber-users?replies=14

Hello,

To be honest, I have never used AWS. I installed it in localhost and it seems to work fine for me. Can you send me a link to your website to see if I can figure something via view/source? Also, a list of all your installed plugins might help.

Nice! ??

I will update the plugin in order to include the fix.

Thank you for your feedback!

OK, I ‘ve done a little digging and I suspect that the cause of your problem might be that in your cases the script is loading before the jQuery.

Could you please replace the current remove-uppercase-accents.php file with the one below and and let me know if it fixed the problem?

https://dl.dropboxusercontent.com/u/38634/Transfers/remove-uppercase-accents.php?dl=1

hello,

sorry for the delayed response – I just saw the message.

can you send me a link to your website? I have tested the plugin in 3.6.1 And it was working fine. I don’t know if there is a conflict with some other plugin out some issue with the script enqueuing.

I will give it a try – thanks for the quick response!

I have a similar problem to the one described in the initial post. On my main blog I use this plugin for almost a year now and I have no issues. But when I installed it on a new blog I found that it publishes the new posts on both the fanpage AND my personal profile.

I have the “See all pages” option ticked and I have selected the fanpage to which i want it to post. In fact, I double checked my settings comparing them to those of the other blog and they are the same.

Any ideas why it keeps posting on my personal profile as well? Perhaps I am missing something, but I can’t find out what…

Thanks!