rcwatson

Never mind. I found another post that said I needed to add my currency (“USD” in my case) to the price suffix.

Thanks for the tip. I allowed the other IPs as you noted and it seems to have solved the issue. It also occurs to me that just waiting for a timeout after some previously blocked action may have done the trick as well. We’ll see.

Hi Said,

I turned off all experiments and cleared browser and server caches, but the error I reported in my earlier reply is still present above the main menu of the site after the 3.1.0 update.

Is there another plugin, perhaps, from the list I gave in my earlier reply, that could be in conflict with Elementor and causing this issue?

This site also uses Elementor Pro Version 3.0.8, but that presently cannot be updated due to its separate license having expired.

I am also experiencing this issue on a staging version of a WordPress 5.6 site after upgrading Elementor. I had version 3.0.16 of Elementor installed and updated to 3.1.0. I cannot deploy the plugin update to the live site until this is resolved.

Here is the full error message appearing at the top of the site:

Warning: Declaration of Theplus_Column_Responsive::register_controls($element, $section_id) should be compatible with Elementor\Controls_Stack::register_controls() in /code/wp-content/plugins/theplus_elementor_addon/modules/controls/group/plus-column-width.php on line 0

The other plugins also updated at the same time are:

* Google Analytics for WordPress by MonsterInsights – Version 7.15.0 installed. Updated to 7.15.1.
* Ninja Forms – Version 3.4.33 installed. Updated to 3.4.34.
* PixelYourSite – Version 7.2.1.1 installed. Updated to 8.0.1.
* Premium Addons for Elementor – Version 4.1.8 installed. Updated to 4.2.0.
* Redirection – Version 5.0 installed. Updated to 5.0.1.
* Variation Swatches for WooCommerce – Version 1.1.5 installed. Updated to 1.1.6.
* WooCommerce – Version 4.9.1 installed. Updated to 4.9.2.
* WooCommerce Shipping & Tax – Version 1.25.5 installed. Updated to 1.25.6.
* Yoast SEO – Version 15.6.2 installed. Updated to 15.7.

And a theme:

* Astra – Version 3.0.1 installed. Updated to 3.0.2.

Thanks for the response. I should have added that I did check the setting you linked to in #1, but it was already set to only use the plugin for standard wordpress forms. So, that was why we decided to abandon SS for now. I wish it wasn’t the case as it’s been my favorite out of all of them for effectiveness. Hopefully the way you will devise (per #2) will take care of the problem.

This one got me as well. Still seems to be an issue as of this reply. The fix was to remove the .git folder and .gitignore from /vendor/techcrunch/wp-async-task/.

As it turned out, I missed the “OR” part of the OAuth, Secret and API Key entry interface of the plugin. I was trying to enter all three when all I needed was OAuth and Secret, not the API Key. It works now.

While I’ve got you, one feature that would be helpful is some way to determine the order of events imported. For example, I imported two events but in the post list they’re showing with the exact same date import. On the website, the way posts are ordered by ID, this makes one event look like it’s going to happen before another, when the opposite is true. I changed the publish date and time by one minute between them to force the earlier event to show up first, followed by the later event. But I’ll have to do that manually each time I import and it keeps me from buying the Pro version because I’ll have a false sense that it is working when it might actually be confusing people about when the latest event will occur.

Just a feature request for a future version.

Here’s a post I wrote describing the issue and possible solutions to resolve it. https://webidextrous.com/how-to-solve-421-misdirected-request-errors/

I did all that. I even turned off all other plugins and reverted to Twenty Nineteen. Yoast and Facebook continued to not get along. Rank Math works, but Yoast does not. Some article I looked up on Facebook (can’t find it now) said that you can’t have both and that’s what the meaning of the error was that I was getting. I have no idea why. Been wanting to try out Rank Math for a while though, so I guess it’s for the best.

Sorry. I don’t have the data anymore. It got so bad at blocking legitimate users that I had to completely delete the plugin. I replaced it with Sucuri.

The parent DOM container is 1152px, which is definitely wider than the widget’s default width, so I expect that setting it to 100% will result in a wider widget.

However, when I entered “100%” in the widget’s “Width” field, it didn’t respond the same way as the CSS, which is why I was confused.

When I do this via adding “width:100%” to the element in CSS it works fine.

div#fbrev_widget-3.et_pb_widget.fb-reviews-widget {
width: 100%;
}

Update: I achieved this via stylesheet overrides, but it’d still be great to have the ability to specify 100% as the width in the plugin or widget settings.

Thanks. It happens on Chrome on Windows as well.

Thanks, Bruno. I just got info from the client that he tried loading his site as a regular anonymous visitor from an Apple store in another city on multiple devices. He says it’s happening for him there as well. He’s had these sites since around 2009, and the fact that the issue began happening shortly after we installed SSL. There isn’t a Google authentication service involved.

One of the readers wrote and said they were using the Vienna RSS reader app and were able to read the posts fine in that app, but the second they opened the posts in Safari tabs, they got the 421 Misdirected Request error.

Thanks. I should have mentioned that we did clear browser caches like crazy. Also, the issue doesn’t occur in the Private mode of Safari (and not at all in regular or incognito mode of other browsers). It just happens in regular mode in Safari.