PhPCentre

Then use the add_menu_page() instead.
http://codex.wordpress.org/Function_Reference/add_menu_page

Try this:
'post__not_in' => array( get_the_ID() ),

@somedude77 I think the typo error @ronangelo pointed out might be the issue with your code. I did put up a sample plugin to try and replicate your issue with the codes above , but I did not find any. Also in my sample plugin, the result for the query is displayed via a shortcode, and I did insert the shortcode directly inside the index.php file.

However, inserting the shortcode before the loop in the index.php file, the global $index_of_ids is not available as the loop has not been executed yet, but using the shortcode after the loop in the index.php file, the global is available, I do not know whether this is the issue. Just double check and report your results.

You can exclude the featured post from the archive page using the meta value saved by the custom check-box field like this.
This approach is better as it will remove only the intended post instead of all post belonging to a particular category..

Considering your support threads here , here and here, This Amazon s3 and cloudfront plugin have got you covered,it will solve your issue.

Once installed, go to the plugin settings page, switch on the path option and you would notice an input field will immediately appear underneath, by default , the value would be something like this “wp-content/uploads” , now edit that input field and append your desired folder name like this ” bar/wp-content/uploads” and save your options.Then your url should come something like this.

http://s3‑us‑west‑1.amazonaws.com/bucket-name/bar/wp-content/uploads/photo.jpg

However you can further extend your folder structure by enabling the year/month option. So your url could appear something like this

http://s3‑us‑west‑1.amazonaws.com/bucket-name/bar/wp-content/uploads/2015/03/photo.jpg

@brayll the suggestion by @danielagw is by far the best solution I have found for users trying to achieve this hack, the only problem with his solution is that the filter profile_update will update the display name in the db once for each new user the first time the profile page is updated, so the next time the user updates the first or last name, the profile page, the changes will not reflect on the display name. So here is a hack that should solve your problem.

add_action( 'profile_update', 'my_profile_update', 10, 2 );

function my_profile_update( $user_id, $old_user_data ) {
        // Do something
	$user = get_user_by( 'id', $user_id );
	$firstname = $user->first_name;
	$lastname = $user->last_name;
	$nickname = $user->nickname;
	if (  $firstname !== '' && $lastname !== '' && $nickname !=='' ) {
	    remove_action( 'profile_update', 'my_profile_update', 10, 2 );
	    wp_update_user( array( 'ID' => $user_id, 'display_name' => $firstname.' "'.$nickname.'" '.$lastname ) );
	}
}

So anytime a user updates the profile page,the changes are made immediately to the user display name. And Ofcourse you can customize the if statement however you want.

Yes the error has something to do with the location of your bucket. You will get that error while trying to authenticate request to buckets located in Frankfurt region with AWS signature v2. The region will only accept signature v4.

I would like to know what version of the plugin are you using ?, cause this issue has already been fixed in newer versions of the plugin,please upgrade.

@ckunderd

Please can you give me the github link where the issue has been reported to confirm my doubts.