wpweaver

A note from the author of the Weaver Xtreme theme:

Your plugin assumes that all themes use box-sizing:border-box; by default. This is not true for many themes, including ours.

You need to wrap all of your generated content with a plugin specific class that set box-sizing:border-box;

The original poster assumed it was a theme issue, which it is not. You need to fix your CSS.

It really is okay to post here. If someone else sees it, they too might see the need to keep up with the latest Captcha plugin.

So, now the forum uses Google reCaptcha V3. Can’t even tell it is there!

The only plugin I could find that supports V3 is

Google Captcha (reCAPTCHA) by BestWebSoft

It has over 200,000 users, and that seems to be the most popular of any “real” Captcha plugin. There is another one with more users, but it seems to be dedicated to Contact Form 7.

The thing that this solution doesn’t solve is the two factor verification required for registration – you still must open your e-mail to get set your password, and then finally be allowed to login.

Again, I really appreciate your input on this.

Thank you for your input on this issue. I am acutally a bit embarrassed by this as I am generally quite aware of all these issues.

One of my goals for the Weaver Theme is to get it certified for accessibility. It has the basics, but could use some of the more subtle changes that allow full accessibility.

That said, the accessibility of the Captcha just never made it to my awareness level.

It should be a matter of switching to a new Captcha plugin.

There are several modes of reCaptcha operation. One uses the “I am not a robot” checkbox, the other is supposed to be invisible but may not work as well.

I would be happy to add either version, but as the forum draws quite a few spam robots, I would like to use the most secure version – as long as that would work.

So, have you encountered the “I am not a robot” version which requires the user to check a checkbox, and does that work for you?

Thanks for your input, and now your help.

I just looked at your page, and if you are using Weaver Xtreme, you’d be much better off using the Page with Posts template rather than the show posts plugin.

Please ask this question on our support forum:

https://forum.weavertheme.com/

We do not do support here, but user our own active forum for support for our themes and plugins.

But you can easily hide the icon with a bit of custom CSS.

• This reply was modified 6 years ago by wpweaver.

You seem to have several good plugins that you don’t update to indicate compatibility with current WP versions.

Even if you don’t need to fix anything, you owe your users the courtesy to at least update the WP version compatibility tag on the 1/10 version updates.

Not sure a switch to JS would work as <script> is not allowed, either.

It may not really be fixable, but at least you could emit a warning when used on Multisite. Mostly, it was just mysterious what happened on my Multisite until I noticed the superadmin account worked just fine, and then remembered the unfiltered_html capability.

sorry – mistaken followup

• This reply was modified 6 years, 1 month ago by wpweaver.

Follow up: I’ve figured out the issue:

Note: In WordPress Multisite, only Super Admins have the unfiltered_html capability.

You should issue warnings to non-super-admins on Multisite installations for your blocks that require unfiltered_html, which included embedded javascript. There’s not much to be done about this necessary restriction, but having a warning instead of broken blocks would be much better.

Fabulous!

How about adding alignment and perhaps a max-width?

But my compliments to the seamless integration. I have been highly recommending Widget Shortcode to all my theme useers, and this addition is great.

Be sure you notify the WP Plugin directory admins that your plugin is Gutenberg / Block Editor compatible.

I just learned that Gutenberg/Block Editor now includes an option to display Custom Fields (off the three vertical dots option menu), so the need for your plugin is a bit redundant now. It was really a lifesaver during the Gutenberg development period, but it probably isn’t worth any more efforts on your part.

Did this just start in 4.0.0?

My plugin has a similar issue – can create it, but not re-edit. This has worked fine since March or so, but broke with 4.0.0. I think they did something related to the save procedure.

I have found the same with some other GB plugins, but some still work.

I think this must be a really major issue.

Sorry, Michael, I have not prompted or asked any of these other folks to reply to your messages. No shills here, just happy Weaver Xtreme users as far as I can tell.

Not every theme is for everyone, but Weaver Xtreme remains the most flexible theme available with more options than any other theme. You can build virtually any design without the need to resort to child themes. No other theme can say that.

The Weaver Xtreme’s own support site is one of the best available for any WordPress theme or plugin. Usually questions are answered within a few hours, a day or two at the worst.

The HTTP/HTTPS issue you mentioned is 100% not theme related. Seriously. Handling HTTPS is entirely within the realm of WordPress core, as well as your original content. If you hardwire a URL with https://, then you will have to manually fix them. While switching from http to https can be non-trivial, that has nothing to do with the theme.

As for the JetPack mobile theme warning, that is essential because that JetPack option totally breaks Weaver Xtreme. MANY users of JetPack had checked that option because of very confusing wording from JetPack about that option. Then we got a bunch of support questions because people’s sites were then broken. That warning is simply good policy.

I’m sorry you’ve had issues. But our support forum is second to none, and the over flexibility and reliability of Weaver Xtreme is also second to none.

It was done as a popup because that seems to be about the only way to get the message for both the Customizer and the Legacy option interface. Because that warning is outside the design of the Customizer, it is really hard to deliver such messages there.

But we will look into an alternative to a popup.