Tag Info

New answers tagged

0

You can customize the form response from the plugin itself. Look at the bottom of the edit contact form pages and you'll see a list of error messages / success messages that can be modified without adding code.


1

Your child theme's functions.php file should be an empty file to which you can add code specific to your child theme. It appears you have copied the functions.php file from the parent theme instead. See this note about functions.php in Child Themes: Unlike style.css, the functions.php of a child theme does not override its counterpart from the parent. ...


1

Update for everyone visiting this thread (2015) jwplayer_tag_callback() does not work anymore, you'll get a fatal error telling you the function is not defined. Instead insert a player programmatically like this: echo JWP6_Shortcode::the_content_filter( '[jwplayer file="'. $videoUrl .'"]' ); (Found here.)


0

Yes, there are two places to check for this error -- one is when adding a menu / page as in 'add_options_page', and the other is when explicitly checking the capability with current_user_can and its like. Also, a plugin should not use roles -- it should use capabilities. So for the function I just mentioned 'add_options_page', the capability is probably ...


0

I think I found the solution myself. When I adjusted the declaration of the registration form: <form name="registerform" id="registerform" action="<?php echo esc_url( site_url('wp-login.php?action=register', 'login_post') ); ?>" method="post" novalidate="novalidate"> To the following: <form name="registerform" id="registerform" ...


0

If you look at the source of add_settings_error(), you will see that the errors are stored in the $wp_settings_errors global. So in your tearDown() function, you can do this: $GLOBALS['wp_settings_errors'] = array(); Also, don't forget to call parent::tearDown(). I sometimes forget, and it can lead to strange behavior. ;-)


0

Most important thing here would be to figure out what's causing the errors as opposed to just hiding them. 70 GB file might be tough to open, so you can use tail to open up the last several lines of it tail -f error.log and see what's going on. Maybe it's a quick fix. If it's filling up with notices and things you're okay with you might have debugging ...



Top 50 recent answers are included