josephparsley
Forum Replies Created
-
This continues to be an issue in the latest version — the
tribe_catch_and_throw()function is catching non-TEC-related errors and throwing a fatal error, regardless of the error’s initial severity.This escalates notices and warnings into fatal errors, which is pretty unacceptable. Obviously you don’t want these things in your code if they can be avoided but an edge case that wouldn’t normally cause a visible issue causes the site to fail.
This remains an issue in 4.9.0.2. I’m still not sure if this was an intentional change but if it was it’d be helpful to at least have that acknowledged.
This remains an issue in 4.9.0.2.
Also noticing this issue. Seems like the
restore_error_handler()on line 1214 of\common\src\Tribe\Date_Utils.phpis not restoring the original error handler properly after switching it two lines above.@jyhsiao I suspect what you need to do is to check the box on your GTM Trigger for YouTube videos that says “Add JavaScript API support to all YouTube videos”.
I’m fairly certain the iframed versions don’t have this natively, so what’s probably happening is that the plugin’s code does this for you somehow when you turn it on, but since you don’t want two different tracking items, you can turn it on through the trigger.
Hello Georgian,
Thanks for the reply. It turns out there was another plugin that was hooking into ‘wp_login_failed’ and redirecting to wp-login.php. I’ve found the source of the problem, but now I need to resolve it.
This plugin is something I need to keep using, but it already has a mechanism for working around it built in. Is it possible to add additional fields to the login form? I’d like to add a hidden field that contains the data that I need, if I can. But I don’t know if it’s possible to modify the login form without actually modifying plugin code.
Thanks for your help again!
I don’t know if this helps (either the plugin author or the user who experienced this problem), but this is actually a core WordPress issue: https://core.trac.wordpress.org/ticket/36196
Users with no role don’t display in the users table, as they’re essentially not really users at all according to WordPress’s capability management. Whether that’s a user issue (because you intentionally or accidentally didn’t add a role) or a plugin issue (users being created without roles) I can’t and won’t say, but it’s worth being aware of.