grl570810

Hi nextgen,
I’m reopening this topic as I can confirm that it’s a nextgen bug happening on my site. When a new image is created with either of a ‘ (apostrophe) or ” (quote) character then instead of the character being written directly into the database it is entered escaped i.e. \’ or \”, and is then displayed in that manner when the image is viewed. As an example, here’s the nextgen gallery editor view of an entry:

and this is what is stored:

NGG version 3.59.5 running on WordPress 6.6.2. This has been confirmed with all plugins other than NGG disabled and the vanilla 2024 theme. It is something that has recently changed as images stored a few months back have no issue it’s only more recent ones that show this issue. Unfortunately I don’t have an exact date of when it happened. Please address this urgently as the workaround of entering as ' or " is not suitable for the end user of this site.

To update on this: the issue turned out to be that the account owner (not me!) had accidentally activated the single site PRO licence on a second site. Whoops. Thanks to Ole from @supsysticcom for his support.

Bump. Any chance of a response please @supsystic?

I can see that the icon / link is there now. But I’m 100% sure it wasn’t there when I was initially setting up the menu item; there’s no way I would miss anything that obvious. It’s a long while ago now so no big deal but I wonder if maybe the removal link doesn’t appear in a session immediately following the addition, perhaps logout and back in is required?

Hi @takanakui . Yes, it would still be useful to know how to do this as I did not find a method to do so. So I had to revert the site to a recent backup but that wasn’t an ideal result as I had to also re-apply other changes I’d made.
TIA, Graham

Hi @shra
https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/inactive-user-deleter/inactive-user-deleter-158-cross-site-request-forgery-via-multiple-functions
If you need more details I suggest you reach out to the Wordfence support team.
Regards,
Graham

Hi Wordfence Support,
Bump. Any chance of some feedback regarding my issue?
Regards,
Graham

Hi @wfjanet
Thanks for replying but I am afraid you have completely missed the point of my issue. I have no problem with the performance of the Wordfence plugin on any individual website. My (new) hosting server is blindingly fast in normal usage and initiating a scan on any one website has no performance impact whatsoever.
My issue is with the Wordfence Central Console (https://www.wordfence.com/central). As I reported, when I login to this at my start of day to check on the status of the sites I host the back-end immediately triggers a scan on every site I have connected to it. It is this approach of running a scan on all my WordPress sites simultaneously that is spiking the hosting server’s CPU usage to 100% and slowing down every site on the server.
What I am requesting is the the Wordfence Central system be adjusted to issue the requests for a scan to the list of sites in an orderly manner, rather than hitting all the sites at the same instant.
Regards,
Graham

+1

Thanks for your assistance with this. I have now tracked the issue down to the theme in use on the site (Antique Mall by netbaseteam) so will be taking it up with them.

Sorry guys, that made no difference. Any other ideas to try?
Please can you advise me where the information about the gallery preview image is stored, i.e. where is the code that displays the album looking to determine which image to show for each of the galleries? If you can advise me of that I can have a look at what is happening as I change the preview image and might be able to diagnose the issue.

• This reply was modified 1 year, 11 months ago by grl570810.

I’ve removed WPO from the site. That made no difference. I’m attaching a site report generated from Wordfence. Please advise further as to why this function is failing on my site.
https://www.abbottsantiques.com.au/wp-content/uploads/2023/04/diagnostics_for_www.abbottsantiques.com_.au_.txt

• This reply was modified 1 year, 11 months ago by grl570810.

WP Optimize is only being used to compress images as they are added to the site (it uses reSmush.it for that). However, to the best of my knowledge it only works on images uploaded via the WordPress Media page, it won’t be touching anything uploaded through NGG. Since this site is now stable other than the NGG changes I will try removing WPO and see if that’s the source of the issue. I’ll let you know the results.

Hi Jaime,
I run the hosting server myself, and there’s definitely no server side caching involved. I’ve already run through disabling plugins with no effect. No Jetpack; the only similar thing is WP-Optimize but it’s not got either caching or minification on as I suspected those as a possible cause. The only thing I can point at as having changed the behavior of the site since it was first implemented is the change in version of WordPress; each time that has undergone a major shift the issue has got worse.

I found this on another thread https://community.gravityforms.com/t/how-to-capture-country-code-with-phone-field-resolved/10541/2 : “…and click on “Enable smart phone field” and “Automatically select countries” 45, then enter your default country…” It seems that you must have the “automatically select countries using IP address” checkbox turned on to allow the country code to capture.

There’s no mention of that in the documentation, and, given the number of folks using VPNs these days which would very likely result in the misidentification of the country in many cases, I don’t see why it should be necessary. Surely you should always collect the country code regardless of whether it’s been “guessed” based on IP address or manually selected by the user? As I said above, collecting international phone numbers without the country code is futile.

Please can you look at your design here to address the issue, whilst it’s not a bug per se it’s at best an obscure approach. At the very least you need to improve the documentation to highlight this somewhat odd behaviour.

Thanks,
Graham