jamesstcrice

Thanks for looking into it, and that is a totally fair point, I wouldn’t be disabling those.

As someone else here mentioned, it would be great if this could do category management. I know there might be some technical limitations around that, but would be great to be able to group blocks in a more client-helpful way than like their source (in the the case of things like generateblocks or stackable).

Hi Corey,

Sorry, didn’t mean to give you radio silence.

There is no one specific way I’d want it to work, but added flexibility for forms in general would be great. I bought FormSync, which does a similar json based form migration, and I confirmed it worked but haven’t used it heavily enough to have confident opinion.

I confess I haven’t given your plugin a good try yet either because I often pulled in a bunch of directions at once. However, I just activated it on a collection of about 20 sites that share a common codebase, so happy to circle back with any helpful feedback.

Ps- Saw your google sheet plugin and that is a frequent request I get, and Zapier tends to fail… so you might get a customer there.

• This reply was modified 2 years, 7 months ago by jamesstcrice.

Hi Jeff,

Have you had a chance to look into this?

Thanks

I was able to replicate the issue on a staging site with only these two plugins installed (the latest versions).

Hi Maya,

I’m definitely using the latest versions.

When you do the above, can you then access Posts > Taxonomy order?

I further discovered that it’s only an issue for the post content type but works normal for other content types.

I submitted your contact form yesterday as well.

Did a bit more testing and this is what I narrowed down:

With “Disable Gutenberg everywhere” checked, I don’t get the error.

If I uncheck “Disable Gutenberg everywhere” and check all the roles and all the post types, I still do not get the error.

If I just uncheck “Disable for Administrator” (my role), then I get the error.

So based on the testing I did, this is what happens.
With “Disable Gutenberg everywhere” checked, I don’t get the problem.

If I uncheck “Disable Gutenberg everywhere” and check all the roles and all the post types, I still do not get the problem.

If I just uncheck “Disable for Administrator” (my role), then I get the error.

Going to add this info to my other thread as well.

Does that provide any clues as to what might be happening?

Thanks for the quick reply, Jeff.
I am doing some more testing and it doesn’t happen when you leave “disable everywhere” checked. However, it seems to happen if you start adjusting per role. Still working to narrow down.
I own the paid version of the other plugins, so I submitted a ticket there as well.

I saw that but it seemed to use custom rules rather than the built in meter?

I’m using a gravity forms based registration form that enforced “Strong” using the core meter.

Can you clarify how the extension does it? I want the registration and reset to use consistent logic.

This is perfect, thank you very much

Thanks for pointing me in the right direction, that works.

I would prefer to use TML if possible. Do you know of any TML compatible ways to require a “strong” password when doing a reset?

This is basically what I want to do as well.

I am working on a client portal for a client. Users confirm their email upon registration, so we already know the address is valid. I would like to have 2FA by Email automatically active for all users without any extra steps, and this is not a crowd that would be likely to use Google Authenticator. It’s because the system contains sensitive data, so in this case I want it to be mandatory.

Is that possible?

Update: It appears having 2FA enabled prevents user login notifications from working. I have not yet figured out why the Available Updates notification is not working as intended.

Did some additional poking around and found the code that adds the generator tag in site kit. Since it uses an anonymous function, it can’t be removed using remove_action which is unfortunate.

It would be great if this tag was either removed entirely, or the code altered to use a named function/action that can be manipulated as needed.

• This reply was modified 4 years, 10 months ago by jamesstcrice.

Thanks @reneesoffice. The setup loop is definitely the higher priority of the two. Appreciate the prompt responses.