Steve

Yeah, I saw that from the other thread. My mistake, sorry.

It might be helpful to add some kind of visual confirmation that the slide order has changed when the button is pushed. A ‘working’ icon or something — I know that kind of thing is overused, but I think that’s why I didn’t notice that the order had actually changed.

Well, I’ll be a monkey’s uncle — so there are.

I remember clicking the buttons at one point but didn’t see the slide change, or maybe a javascript error was preventing it. Or maybe I just wasn’t paying attention. Who knows.

Because the powers-that-be forced their Gutenberg brain-child on the public before it was ready, with no ‘how to’ instructions whatsoever.

Whoever pushed this created a big, steaming pile of horse&*it in the world of WordPress, as you can see by the 1M+ installations of this plugin.

This is a late reply, but it was not a “false positive”.

Your file name, “SRCB Swap ‘Til You Drop exp.pdf”, contained an illegal character (the ‘ mark).

WordPress strips invalid characters from filenames during the uploading and storing process, but your server beat WP to the punch.

Don’t use punctuation characters in file names, it’s bad practice and can definitely cause issues.

This WP vulnerability issue you mention – “We were surprised to see that they did not patch that issue.” Did you submit a patch for it?

WP is, after all, a community effort.

I came here because I am experiencing exactly the same issue on a couple of sites – the client is all up in arms about ‘security warnings’.

‘Flaming you’ helps if it awakens you to the fact that people don’t want to be bombarded with Chicken Little warnings all the time and give them an option to turn them off.

Doing so appears to run afoul of WordPress’s plugin Guidelines:

7. The plugin may not “phone home” or track users without their informed, explicit, opt-in consent.

In the interest of protecting user privacy, plugins may not contact external servers without the explicit consent of the user via requiring registration with a service or a checkbox within the settings. This method is called ‘opt in.’ Documentation on how any user data is collected, and used, should be included in the plugin’s readme, preferably with a clearly stated privacy policy.

This restriction includes the following:

No unauthorized collection of user data. Users may be asked to submit information but it cannot be automatically recorded without explicit confirmation from the user.
Intentionally misleading users into submitting information as a requirement for use of the plugin itself is prohibited.
Images and scripts should be loaded locally as part of the plugin whenever possible. If external data (such as blocklists) is required, their inclusion must be made clear to the user.
Any third party advertisement mechanisms used within the plugin must have all tracking features disabled by default. Advertisement mechanisms which do not have the capability of disabling user tracking features are prohibited.

I will be reporting the plugin to WP. They can sort it out.

The backslashes are namespace identifiers – which I should have known, which makes me a bit of a dork.

The problem in my case was client’s hosting still running PHP V5.2, which doesn’t deal with namespaces.

My bad, wish I could delete the thread.

No need to delete the other theme just yet. Let’s see what happens after you change the error display.

Hi Mandy,

Please remove the @ini_set line, and change WP_DEBUG_DISPLAY to true.

The settings you have now will write errors to a log file on the server. If you do as I advise, you may (doesn’t always work this way) be able to see the actual error on the screen.

You haven’t killed all of your plugins. At least two – jetpack and photo gallery – are still active.

Super – it’s great when plugin authors listen to feedback! ??

@mickeyroush, ‘extortion’ is a little strong, admittedly. But a plugin this complex WILL have issues, it’s a given. People should know that if they do have problems not to expect much in the way of support unless they pay.

@johnwbyrd – I’m mildly amused that you were incensed enough to create an account just so you could post your own little rant (which is totally off base, btw).

@andrew, I don’t need support, thanks. One of my clients did, and wanted to try to fix his problem on his own. He described the responses he’d gotten, which is what brought me here.

Feel free to delete this whole thread if you wish. My starting it was ill-advised in the first place.

I don’t think I can justify my rant, really, other than to let people know that if they install this plugin and they have problems not to expect much in the way of help.

I don’t need support, but plenty of other people do, and they’re not getting answers. Not because the developer doesn’t have time, but because they’re holding out for money.

I understand completely a dev not having time to support a free plugin that is necessarily complex and prone to any number of problems.

iThemes has chosen to withhold support unless you pay for it. That’s their decision, of course, but in my opinion it is unbelievably tacky and causes harm to the people who actually DO depend on the plugin. Extortion is basically what it is.

All that said, this isn’t really a support post or thread so it should probably be deleted if possible.

Need confirmation of the above? Just look above the green Support Forum button:

27 of 246 support threads in the last two months have been resolved.

That pretty much says it all.

+1

Have had this problem also, though not to the degree as the OP.

This used to be a great plugin until iThemes bought it. Any idea how to get the old 3.x version?