Doug Vanderweide

Regarding the “Featured Image”, if you mean you can’t see the box to add a featured image to your post, in the Dashboard, when editing a post, click “Screen Options” in the upper-right-hand corner and make sure “Featured Images” is checked.

I believe the problem is related to WordPress attempting to make its thumbnail, medium and large version copies of your images. In short, the photo is uploaded just fine, but when WordPress attempts to resize it, it’s either trying to get the image from the wrong place, or it’s not able to save the resized images to the right place.

In theory this shouldn’t be an issue because the image directory is actually in a subdirectory of your website’s home directory, but it may be that your host’s settings effectively treat that directory as not being part of your main web site’s physical file paths because you applied a subdomain to it.

In other words, it looks to you like it’s a subdirectory, but certain settings in the hosting environment tell PHP / WordPress that the directory does not exist as a subdirectory of your main site.

Unfortunately there is no easy way to resolve this. I would say to contact your hosting company but my guess is that this is not something the average front-line tech can even understand, nonetheless address. You’d need some fairly advanced tech support to get this sorted out.

Meanwhile, your best fix is to go back to not having a subdirectory. I know that’s not cool, but clearly you have a configuration issue.

This is something of a stab, but the error you are getting is generated when WordPress is trying to set the cookie that identifies you as a user and saves certain settings on your computer.

First, try clearing your web browser’s cookies and cache. It may be that an old setting from a disabled plugin is causing this problem.

If that does not work, try creating a new admin user in WordPress, then log in as that user. If you stop getting the error, then the issue is with the user account you were using, and you might consider deleting it and merging all its posts to your new user account.

Otherwise, the problem is with some user metadata in WordPress that has gone bad or is corrupted. There’s no easy way to fix that, unfortunately. There is the function delete_user_meta but invoking it in special cases like yours is hard to do.

Assuming you have access to your website server (i.e., FTP) and you have a Google account, log on to Webmaster Tools, verify that you own the site, and ask Google to re-index the site. That should fix your problem if you have deleted everything there.

As referenced here, you can use the child-of argument for get_pages; if it returns any number of pages, then you know the page has at least one child page.

$pages = get_pages( 'child_of=' . $post->ID );
if( false !== $pages && 0 === count($pages) ) get_template_part( 'my-template-here' );

This is something of a stab in the dark, but I think it may be a problem with proper casting of the user ID, or perhaps $query can’t be properly set from this function.

Try this:

function exclude_this_page( &$query ) {
    if( !is_admin() ) return $query;

    global $pagenow;

    if( 'edit.php' == $pagenow && ( get_query_var( 'post_type' ) && 'page' == get_query_var( 'post_type' ) ) ) {
        get_currentuserinfo();
        if( '4' == $user_ID ) $query->set( 'post__in', array( 59, 67, 115 ) );
        return $query;
    }
}

I think you mean, you want to store some user variable and persist it across URLs so it can be retrieved in JavaScript.

The easiest way to do that is via cookies. See this W3 tutorial for more information.

tl:dr: Your code isn’t running inside WordPress and therefore, $wpdb is not defined. You can fix it by requiring wp-load.php prior to calling your function.

You’re getting this error because you are calling this function from outside of WordPress.

“Call to a member function insert() on a non-object” means that PHP is looking to see if $wpdb is defined as a WordPress Database Access Abstraction Object, but it is not. In fact, the way you have called it, it is basically null.

Therefore, when you set $table_name, it is actually just ‘nd_tempemails’ and when you call $wpdb->insert, PHP can’t do as you request because it has no idea what $wpdb is, other than null.

You can get access to $wpdb from outside WordPress by requiring wp-load.php. See this thread on how you can go about that, and note that how you find the path to wp-load.php depends largely on how your server is set up. That said, generally speaking this will work:

$parse_uri = explode( 'wp-content', $_SERVER['SCRIPT_FILENAME'] );
require_once( $parse_uri[0] . 'wp-load.php' );