Solution:
We usually write about major plugin versions and when we have something important to share with our community. For Maps there has been no major changes in recent time. Usually we do not provide any ETA but do you have any reported bugs or feature request in the past that you would like to know about?
If yes, please share with me the link to tickets where those bugs or features were reported by you and I will try my best to look into our system and forward your concerns ahead accordingly.
Other plugins like CRED, Layouts are also getting updates from time to time as you can see in the changelog for each plugin. So yeah other plugins will be updated as necessary.
Problem:
Setup links to parent post, the link text is a custom field value of parent post.
I wrote a shortcode [next-post-id] to get the id of the next post.
function shortcode_next_post_id ($atts)
{
global $post;
$next_post = get_next_post();
if (empty ($next_post))
return 0;
return $next_post->ID;
}
add_shortcode('next-post-id', 'shortcode_next_post_id');
Solution:
Since you have already got the post ID of next post with custom shortcode [next-post-id], so you can setup the link manually with HTML code, for example:
Please make sure you have already registered the custom shortcode name in the Toolset setting page:
Dashboard->Toolset-> Front-end content
option "Third-party shortcode arguments", fill the custom shortcode name: next-post-id
Problem:
How to style (using bootstrap) this Login form created using CRED form:
[wpv-login-form]
Solution:
Use Custom HTML and CSS to style the Login form differently from the WordPress native Login form.
As an example a display: flex applied on the container div will put your input fields inline.
But wpv_filter_override_auth_errors is not working as expected on [wpv-login-form].
Solution:
There was a mistake in the given example code but it's fixed now. Please add this updated code in your theme’s or child theme’s functions.php file and it will resolve the issue:
add_filter( 'wpv_filter_override_auth_errors', 'custom_wpv_override_auth_errors', 30, 3 );
function custom_wpv_override_auth_errors( $message, $class = '', $code = '' ) {
if ( $code != '') {
$message = __( '<strong>ERROR</strong>: ', 'wpv-views' );
switch( $code ) {
case 'invalid_username':
$message .= __( 'Invalid username.', 'wpv-views' );
break;
case 'incorrect_password':
$message .= __( 'The password you entered is incorrect.', 'wpv-views' );
break;
case 'empty_password':
$message .= __( 'The password field is empty.', 'wpv-views' );
break;
case 'empty_username':
$message .= __( 'The username field is empty.', 'wpv-views' );
break;
default:
$message .= __( 'Unknown error.', 'wpv-views' );
break;
}
if( !empty( $class ) ) {
$message = '<div class="' . $class . '">' . $message . '</div>';
}
return $message;
}
}
Wir dokumentieren bekannte Probleme und ihre Lösungen in Toolset-Fehlerverzeichnissen. Sparen Sie Zeit, indem Sie zuerst dort nachsehen, ob der bei Ihnen auftretende Fehler bereits bekannt ist. Die Liste wird kurz gehalten. Wir tun unser Bestes, um bei jeder Veröffentlichung von Toolset-Plugins alle bekannten Probleme zu lösen.
Support-Richtlinie
Das Toolset-Team hilft Ihnen, die Toolset-Plugins richtig zu benutzen, liefert Ihnen alle nötigen Informationen, unterstützt Sie bei der Lösung von Problemen und gibt Ihnen Tipps zu Best Practices.
Bitte stellen Sie sicher, dass Sie nur ein Thema pro Support-Ticket eröffnen.
