brettbum

Don’t entirely know what caused it to stop working. Might have been something of a Google Workspace issue more than anything. (all our users were converted to under 18. first problem)

Then it was as if our cloud.google.com account was completely wiped out.

We had to go in and create an entirely new workspace user/email account, make them an adult, create a new cloud account and then go through the entire setup from scratch.

Google support also reminded us to clear our browser cache otherwise we couldn’t even log into the new console.cloud.google.com account.

Good times, barrel of fun, monkeys might have climbed out of a barrel and eaten my brain. :p

Plugin is working just fine now. phew

Follow up, this might be a header permissions policy issue, thus it might feel like its showing up randomly depending on where you host your site(s) and/or depending on your apache or nginx server settings for this.

Decent description of the possible challenge here on stackoverflow with a response from Vimeo Support Center as well.

https://stackoverflow.com/questions/67720466/embedded-vimeo-iframe-fullscreen-not-working-in-chrome

Seeing this challenge as well… coming at this from a vimeo url link added into an ACF oembed field… I mention that as the oembed function seems to be the part that is blocking this control, sometimes. Been discussed in ACF forums and kicked things back over here to WordPress.

Witnessed this in both Chrome and Safari May 2023 latest browsers of each running on a Mac for whatever the extra detail is worth.

I appreciate the follow up. And we might add this back to our mix on the site in question again soon.

It’s been a couple years since we dug into better managing our thumbnails.

Thank you for the follow up and update, hope it helps other users too.

The Insert Pages Widget does still seem to be working to display pages.

Not sure why I’m seeing the failed to load plugin error on post type pages when editing yet. Still troubleshooting, posted this in case others will benefit from the heads up and or find a solution faster than I will.

(I set this up on a site a few years back, and going through and refreshing my memory from notes and more. Feeling rusty on this plugin from that time… Seems like it is still supported which is good. mmay or may not be some other conflict on my site, we’re running a default WordPress twenty seventeen theme there for what that’s worth, although this seems like a problem inside wp-admin and not on the public facing side)

Similar problem in that when submitting a form with a checkbox option, it triggers an error message that the checkbox item was not completed… Since the form does not submit, nothing saves. It doesn’t give the option to actually try again on its own.

Hitting the back button takes users back to the completed form, where the checkbox is still checked, and trying again, same errror.

Failed on 3.1. Rolled back to 3.09 still failed.

Saw on here someone recommend 3.04, tried that and it worked. (didn’t have time to keep going back one at a time).

WP 6.0 running with PHP 7.4

Not positive but the same site generates a critical error when I upgrade to php 8.0. That might be this plugin too, might be something else.

I normally work exclusively with GF. This plugin was installed by a previous developer. I’m not knocking it, but only maintained it on this site for about 3 years as compared to 14 years of doing lots of things with GF.

Having very good competition between at least a couple plugins, if not more is often good for everyone.

Quick update in case it helps anyone…

We have the Classic Editor plugin running (so as not to use Gutenberg blocks).

When I deactivate the Classic Editor plugin, we no longer see this error.

A couple guesses… Maybe this plugin and the Classic Editor plugin are both trying to load the TinyMCE JS library. This one maybe tries last and fails, because its already loaded, which is maybe why we get an error pop up, but the editor still seems to work?

https://www.ads-software.com/plugins/classic-editor/

For what its worth, after the error showed up in the wp-admin edit post or page area….

I tried installing the plugin Disable Widget Block Editor on the off chance that might be related.

It didn’t solve/fix this specific error. (might not be related)

Yup, we’re seeing it too with wordpress 5.8/plugin 2.7.

I should add the content node is visible via Feed Validator. This was not a scenario where the content was hidden.

Link of bug in action

https://pbs.twimg.com/media/D5bAGRlXoAAgKu_.jpg:large

And if I attempt to then add a 2nd item, it does NOT show up in the shopping cart.

Quick addition, if I click Back, and then go to the Shopping Cart, the item that was clicked to ‘Add to Cart’ is present in the shopping cart.

Obviously, getting a 500 error tends to stop people from checking out. ??

I agree. I read that before and afterwards. Somehow I missed that before.

I think it was the screenshot that showed the Bulk Updater screen that countered what the text read.

https://www.ads-software.com/plugins/auto-image-attributes-from-filename-with-bulk-updater/

The screenshot shows the bulk updater screen having options that it does not have in the version that comes from the repository.

I think if that image had a warning that said “Pro version screenshot” it might have helped.

Better yet if the screenshot had shown the bulk updater from the actual free version. Don’t get me wrong, I’m more than happy to support plugin creators and their pro version plugins when and where I can and when its appropriate. I am not one of those people that thinks its healthy for all plugins to be free.

I want plugin creators to be successful enough so that they can keep their plugins up to date, working and safe.

When I got to the Bulk Updater page, and the screen did not match the screenshot provided, I thought maybe I misunderstood the instructions. That mismatch, made me question everything, and then (my mistake) I tried to experiment. First with the test, then reran the test. Didn’t give me a big enough sample to understand what was and wasn’t happening.

So (with a site backup already done) I ran the bulk updater, and experienced the problem mentioned.

I shared my review and comment to help others avoid this mistake and I hope that it might give you some insights to help others avoid getting confused and doing the same or worse.

Hoping this might give you some ideas on how to better convert people to Premium as well. ?? GOOD LUCK!

Is this the solution?

you can deactivate new version and then download, install and activate old version from https://www.ads-software.com/plugins/simple-social-icons/developers/