VR Media

UPDATE/RESOLVED: In case this helps anyone else, we found the issue. The reCAPTCHA v3 site keys needed to be updated as they did not match the reCAPTCHA keys in the Google Account. This likely also explains why the reCAPTCHA challenge pop-up was appearing randomly on other pages. Hope that helps someone else!

We are also getting the same reCAPTCHA v3 error in Flamingo as of today when testing the Contact Form 7 form after making a bunch of WordPress, plugin, and theme updates to the site:

{ “success”: false, “error-codes”: [ “invalid-input-response” ] }

What’s strange, though, is that the same form on a site that’s essentially the same (but using a different URL) worked just fine last week. The issue only appeared today. We also noticed the reCAPTCHA pop-up appeared several times on random pages on the site that do NOT have a CF7 form on them (which it’s not supposed to do) *before* we encountered the issues when testing the CF7 form.

Any suggestions on how to resolve would be greatly appreciated. Wondering if deleting and recreating the reCAPTCHA v3 keys might help. Thanks!

• This reply was modified 2 months ago by VR Media. Reason: clarification

Huzzah. Nevermind. Fixed it.

For others having the same issue – it was permalink-related. Seems like adding the IssueM plugin may have caused a permalinks issue (or it could be because we have the “Current Issue” and “Past Issues” pages set up as child pages of another page). Here’s the simple fix:

1. Navigate to Settings > Permalinks
2. Select a different Permalink structure and save
3. Reset the Permalink structure back to what was originally set and save again

Seems this fixes the permalink issue.

P.S. When on the WP Customizer page (with WPtouch default settings so the WPtouch Customizer settings appear in WP Customizer), Chrome’s Developer Tools console shows this error. Maybe that will help figuring out what’s happening?

Uncaught ReferenceError: WPtouchCustomizer is not defined
at doBauhausCustomizerReady (bauhaus-customizer.js?ver=2.2.4:69)
at bauhaus-customizer.js?ver=2.2.4:79
at dispatch (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,underscore,wp-a11y,wp-util,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable,jquery-&load[]=ui-draggable,jquery-ui-droppable,backbone,wp-backbone,shortcode,utils,media-models,moxiejs,plupload,wp-plupload&ver=4.9.8:3)
at r.handle (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,underscore,wp-a11y,wp-util,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable,jquery-&load[]=ui-draggable,jquery-ui-droppable,backbone,wp-backbone,shortcode,utils,media-models,moxiejs,plupload,wp-plupload&ver=4.9.8:3)

Thank you!

Thanks for the quick reply.

Switched to the Twenty-Nineteen default theme and deactivated all plugins except the wptouch plugin and the issue still persists. Next added the — define(‘WPTOUCH_USE_CUSTOMIZER’, false); — line you suggested to wp-config.php. (FYI, had to change the curly opening and closing single quote after pasting in the line).

Adding the line to wp-config.php did remove WPtouch’s customizer from the main WordPress Customizer BUT unfortunately it also removed the final two Setup options on WPtouch’s settings page. Specifically, the “Customize Theme” and “Subscribe to Newsletter” options are now gone, so we have no way to customize wptouch.

Is there a way to force the “Customize Theme” option to appear again in WPtouch’s settings page? This seems like the easiest solution, if we can get it working properly.

Thank you!

@markzahra you’re most welcome. If it’s helpful, we only installed the plugin a few days before my initial post, so the issue was present for us from the get go. No further response needed, just FYI.

Thanks, Miguel. That seems to have done the trick.

It’s odd though because all the other plugins were properly using the site-specific temp directory without having to add the code. And given cliffrhode appears to be having the same issue – wondering if there could still be something specific to the latest version of the plugin.

Regardless, issue seems to be resolved for us by your suggested fix – setting the temp directory in the site’s wp-config.php file. Thank you!

Forgot to include: the files are being written about once an hour. The plugin is set to refresh feeds once very 2 hours.

Thanks. We had the same issue and this post helped track it down. Glad to hear it will be resolved in next plugin update!

We figured out what’s happening, and it has nothing to do with the Open graph plugin so marking this issue as resolved.

For anyone experience a similar issue – here’s what we found. The plugin is working correctly but is unable to resolve the “featured thumbnail” image for posts because the underlying database records are incomplete. This is a development site, and there are numerous post featured image records in the WP database that don’t have matching media file entries (we haven’t yet XML imported the media library files). When the plugin can’t find the matching media file image record, it simply omits the og:image tag rather than moving to the next option (selecting the first image in the body content).

• This reply was modified 6 years, 2 months ago by VR Media.

Thanks for your help. We weren’t able to get those working, so we have decided to use Theme My Login’s default login & logout pages.

Fwiw, we ended up using the below Paid Memberships Pro code (we’re using Paid Memberships Pro (PMPro, https://www.paidmembershipspro.com) for Membership in conjunction with the Theme My Login plugin) to customize the login process. If a PMPro member logs in, they’re redirected to PMPro’s Membership Account page (/membership-account/) because it has more detailed information, but if they aren’t a Member, then they’re taken to the WooCommerce My Account (/my-account/) page instead:

/*
	Login redirect example using PMPro to check membership levels.
*/
function my_login_redirect($redirect_to, $request, $user)
{
	//check level
	if(pmpro_hasMembershipLevel())
		return home_url("/membership-account/");
	else
		return home_url("/my-account/");
}
add_filter("login_redirect", "my_login_redirect", 10, 3);

Full details (for PMPro support members) at:
https://www.paidmembershipspro.com/forums/topic/different-woocommerce-login-redirect-if-a-pmpro-member/#post-32427

Thanks for the fast response. We’ve tried using those action terms and they are still taking us to the default /login/ and /logout/ TML pages.

Here’s the code we have added to the /plugins/theme-my-login-custom.php file:

<?php function tml_action_url_filter( $url, $action, $instance ) {
	$home_url = get_option('home');

	if ( 'logout' == $action ) {
		$url = $home_url.'/my-account/customer-logout/';
	} elseif ( 'login' == $action ) {
		$url = $home_url.'/my-account/';
	}
	return $url;
}
add_filter( 'tml_action_url', 'tml_action_url_filter', 10, 3 );
?>

Is there something else we could be doing wrong? Thank you.

[RESOLVED] Following up. Stupid oversight on our part. The issue was the thumbnail settings size within the widget itself. We hadn’t realized that option existed & that it’s set to 15×15 by default. Once we updated the thumbnail dimensions in the specific widget, everything worked great.

Posting here in case anyone else makes the same dumb mistake.

Happy WP-ing all,
Daniel

Chris & Michael – you guys rock! Disabling animation did the trick. Sorry for the hassle. Thank you for the superb level of support and a great, highly-customizable plugin.

Hello,

Thanks very much for the super quick response. I tried the steps you suggested but that hasn’t fixed it. We’re not so concerned about the maroon footer moving up and down because the testimonials are different heights.

The only thing we’re trying to fix is that when a testimonial first fades in, the main text & grey open quote image initially appear just a few pixels lower on the page, but then in a second or two, the text/image jump up the correct spot. The Widget Title/H3 above remains static so it seems the issue is somewhere with the blockquote or related divs below the <h3>. Am thinking maybe javascript or CSS is conflicting with the code/CSS that the theme (Vulcan from ThemeForest) has by default for its built-in testimonials functionality. If the theme is changed to Twenty-Thirteen, the issue disappears – so it seems very specific to the theme.

If you have any other suggestions about where we might look to resolve the issue, they would be greatly appreciated.

Thank you again,
D