wp-includes/general-template.php:2102 is the function wp_admin_css(). On the login page this function is called in login_header(). Your theme or some plugin trys to send an HTTP header after that, probably during the actions login_enqueue_scripts or login_head. wp-includes/option.php on:569 is in function wp_user_settings(); a cookie is set here. Cookies are HTTP headers, so that cannot work when … Read more
They recommend putting it into the wp-config.php file. You can read more about it from the codex Editing wp-config It is quite a long document but the error info is found at 2.15 Configure Error Logging
@pzstar it is a good approach to check if your variables are assigned a value or not. If a variable or an index in an array is not declared/assigned then you’d probably get such error. I would suggest you to use isset(). <input id=”welcome_post_char” type=”text” name=”abc_options[welcome_post_char]” value=”<?php echo (isset($settings[‘welcome_post_char’]))? esc_attr($settings[‘welcome_post_char’],’abc’): ”}; ?>”>
First, you need to to find out what your current version of MYSQL… WordPress requires MySQL 5.0 or greater Since its a VPS, I’m assuming its a linux installation. Just type mysql -V on the command line and it will return your MYSQL version. If the version is compatible with wordpress, this message may be … Read more
One of the parameter that you can pass to the supports argument is post_formats, removing this argument will fix the problem with the preview redirecting to a wrong or non-existing url. Code sample: if ( ! function_exists(‘custom_post_type’) ) { // Register Custom Post Type function custom_post_type() { // some code $args = array( // ‘supports’ … Read more
So, yes, WP can be quite a mess, more so in complicated themes. Some of it is just experience and chewing through sources. There are, however, several things that can help to determine what is happening via code: Dumping get_included_files() will get you all PHP files loaded up to that point. It’s messy, but sometimes … Read more
Any messages you are seeing with the debug output should be resolved. These often point to holes in the current logic within your theme. If your goal is to submit the theme to the WordPress Theme Directory you have to resolve any PHP errors, warnings, or notices for the theme to be approved. Themes must … Read more
This could be output a ton of different places and ways, but judging on what you re saying, and that you can’t see anything in your header.php, check your theme functions.php. Look for something along the lines of this: dirname(__FILE__); pathinfo(__FILE__, PATHINFO_FILENAME); SCRIPT_FILENAME If no luck still, check index.php and then check mu-plugins folder for … Read more
Assuming that the hook you have used is correct; below is the updated code which you can use: function custom_listify_single_job_listing_actions_after() { global $post; if( $post->ID == 1464 ) { $url = get_post_meta( $post->ID, ‘your_custom_meta_key’, true ); echo ‘<a href=”‘ . esc_url( $url ) . ‘” class=”button”>My Button</a>’; } } add_filter( ‘listify_single_job_listing_actions_after’, ‘custom_listify_single_job_listing_actions_after’ ); Let me … Read more
You can you wp_parse_args to merge $instance with a default array. So, you would start you form function not with extract($instance) but with $defaults = array( ‘title’ => ‘Your title’, ‘text’ => ‘…’, ‘image_url’ => ‘…’ ‘textarea’ => ‘…’ ); $instance = wp_parse_args((array) $instance, $defaults);