efc

Perfect! I found it. That was exactly what I was looking for. Thanks, Darin!

We did try with the V2 Checkbox and this works. The trouble seems to be when we use V2 Invisible. Since this is for a donation page, we’d really like the invisible version to work too.

Thanks, @wpmudev-support7, we found that without any captcha the attempts to use PayPal would always end in “something went wrong.” We are using the V2-invisible captcha (though we have also seem visible captcha that we assume are driven by the PayPal iframe?). We have a JSON export of the form for you, in case that helps.

All in all we have been surprised at just how badly behaved this PayPal integration is. We have used Stripe for years without this sort of trouble, but this site has many international users who need PayPal.

Adam, it _was_ siteurl and homeurl that were different in the database and UI! We’ve never seen this before and did not even know this was possible. We updated the database, but we still have no idea why the WordPress dashboard UI was showing us a setting that was not in the database.

Just in case you are wondering, we had not set these in the WP config file either. This would have made them uneditable in the UI, which we would have noticed.

Thank you, yes. Deactivating and reactivating the plugin seems to have resolved the issue.

It turns out that even removing WC altogether still results in a fatal error from TP. Clearly TP is not checking for the existence of this PageController before it tries to access it. If WC is not present, TP should not cause a fatal error, it should just report that it needs WC. And if WC is updated to 7.3.0 or beyond, it should notice and look for some alternative to the PageController (or maybe this missing PageController is a WC bug?).

I believe that version 2.5.5 has resolved this issue for me. Can anyone else confirm that this issues is now resolved?

Please don’t just mark this “resolved.” This is a real problem with this plugin. There is no reason it should work this way. It would be much more helpful if _every_ post type was made available for substitution.

I, too, have a case where my custom post type does not need any taxonomies, but we _do_ need a special sidebar. It is very unfortunate that this plugin does not allow me to assign one. Please consider actually fixing this problem, not ignoring it.

Thank you!

This is very confusing for newcomers and a terrible experience as an introduction to Meta Box. In fact, there is a page available for Meta Box even in the free version, it is just impossible to navigate to, this is the /wp-admin/plugins.php?page=meta-box page. In the free version it would be a much better experience if MB created an item in the sidebar that took you to this same content, just so new users would not misunderstand. And on this page it should say clearly just what you said above: “In the free version, Meta Box does not have the UI to create custom fields.”

This simples statement is not provided anywhere in the plugin description, or even anywhere in the installation page. In fact, the installation page goes immediately from “install the plugin from www.remarpro.com” to “let’s look at the custom post UI” which is not available at all without further action and even payment.

Please, fix this. Make it easy for new users to get on board and understand what is happening and how to make Meta Box useful!

I do have the code, it is in the repository I linked to in the original message.

I’ve also put the relevant part of that code into a gist…

• This reply was modified 3 years, 9 months ago by efc.

I was having this same problem. I think it is especially a problem when multisite is set up to use multiple different host names for sites (in other words, one site is uses https://example-a.com and another is https://example-b.org). In this case WordPress forces an admin to re-login when switching sites in the Dashboard using the “My Sites” menu, and WPS Hide Login slugs are ignored, leading to 404s.

I have resolved this with my own Modify “My Sites” Menu plugin that simplifies the “My Sites” menu and is sensitive to WPS Hide Login slugs. If the author of WPS Hide Login wants to take a look at this plugin it might offer a way to resolve this problem.

• This reply was modified 3 years, 9 months ago by efc. Reason: mangled quote marks

Yes, I see this problem too. When using domains or subdomains for multisite (instead of the folder method), the “Dashboard” items in the “Sites” menu refer to the subsite/wp-admin. WPS Hide Login will (correctly) redirect this to a 404.

It would be nice if WPS Hide Login could change those “Dashboard” menu items to refer to the correct logins… but this could be pretty tricky since these can be set either at the network level or within the individual site.

It turns out this was an issue only with Safari. I was able to resolve it with the following CSS in the Customizer > Additional CSS…

pre.wp-block-code .token {
  word-wrap: initial;
  word-break: initial;
}

• This reply was modified 4 years, 5 months ago by efc.

Ah! There it is! Thank you @wpmudev-support8.

I would recommend some clearer help text to make this more self-evident. This feature is impossible to find unless you change the default settings. It is important enough that there should be hints elsewhere about it.

In the visibility settings under “Pop-up Visibility Rules” sidebar I would recommend adding a paragraph:

“Use the Behavior settings if you want to hide your pop-up from visitor for a set amount of time.”

In the behavior settings under the “Closing Behavior” sidebar I would recommend adding:

“Set the amount of time before your pop-up will reappear to visitors after they have closed it.”

Something like this would have helped me find these features.

Thanks for pointing them out. Hustle is a wonderful plugin!

Hm, I think you are right, @wpmudev-support8. I just created a new site with Twenty Twenty and I do not see the issue. I _do_ see it in Twenty Twenty on my live site, so I imagine this is some kind of plugin interaction and will have to dig in to debug it. Sorry to bother you with this, it does not appear to be an issue with Hustle.