Scriptrunner (Doug Sparling)

Are you saying that you are adding an Apache basic authentication on your login page (using htpasswd) so you have to get past that before you can log into WordPress? If so, once you’ve authenticated successfully via basic auth, then it stays active until you close your browser.

Another option would be to use a Limit Login attemps plugin (there are several) or WP Better Security, which also limits the amount of times a user can attempt to login. However, there’s nothing wrong with putting basic authentication in front of your admin page.

What you’ve done is actually one of the suggestions in the Codex page on brute force attacks (but there’s other good info there too):

Codex: Brute Force Attacks

You’re using a frameset for some reason, that seems to be breaking links.

If I navigate to “Links and Resources,” links aren’t working, but if I got straight to the page in the frameset:

http://alaskaseafoodcooperative.org/WP/links-and-resources-2/

Don’t use frames.

If you don’t want your main url:

http://alaskaseafoodcooperative.org/WP

to contain the “WP,” then there are better was to do that.

Codex: Giving WordPress Its Own Directory

Moving WordPress from Subdirectory to Root – FAQ

To find the page that contains the posts (the listing of posts), you use:

get_option('page_for_posts')

as alchymyth said.

$posts_page_id = get_option( 'page_for_posts' );
echo "posts page id: " . $posts_page_id;

The caveat is that this value will only be set if you assign a static page for your front page and assign another page for your posts page (via Settings->Reading). When you run WordPress where the front page displays your blogs posts, that’s a special case and there is no “posts page” id. (actually, I think it comes back as 0).

That’s actually a warning, not an error, so it won’t cause a runtime error.

Error: Fatal run-time errors. These indicate errors that can not be recovered from, such as a memory allocation problem. Execution of the script is halted.

Warning: Run-time warnings (non-fatal errors). Execution of the script is not halted.

This also tells me you’re running your WordPress site with debug mode on, which is not a good practice.

In wp-config.php, change:

define('WP_DEBUG', true);

to:

define('WP_DEBUG', false);

As far as the warning message itself:

Warning: Illegal string offset 'sidebar'

This generally means that your code is trying to access a key in an array that doesn’t exist. The theme author needs to fix that by checking that a key in the array exists (is_set) before trying to access it.

It does indicate a problem with the code, but not a fatal one. I often see piles of Warning messages from various plugins when I turn on DEBUG. (which doesn’t make it right, but sadly it isn’t uncommon) At the very least, set DEBUG to false so the Warnings won’t display on your production site.

chrisntoukas, you’re quite welcome! If you don’t mind, please mark the topic as resolved to help others who may have run across the same incorrect code in the other post.

Add this to your themes functions.php and see if it works for you. It might need a little tweaking, just let me know:

function exclude_category( $query ) {
    // Add your category id(s) here
    $excluded_category_ids = array(1,17);
    if ( $query->is_main_query() ) {
        if ( ( $query->is_home() || $query->is_category() || $query->is_archive() || $query->is_feed() ) || ( !is_admin() && $query->is_search() ) ) {
            $query->set('category__not_in', $excluded_category_ids);
        } elseif ( $query->is_single() ) {
            $post_categories = wp_get_post_categories( $query->query_vars['p'] );
            foreach ($excluded_category_ids as $category_id ) {
                if ( in_array( $category_id, $post_categories ) ) {
                    $query->set( 'p', -$category_id );
                    break;
                }
            }
        }
    }
}
add_action( 'pre_get_posts', 'exclude_category' );

Just change:

$excluded_category_ids = array(1,17);

to include whatever category ids you want to exclude. Must be an array (but it can contain just one element).

So basically you don’t want the post to be visible in any view that would normally show it? (single, category, tag, archive, etc) What do your custom made elements rely on, if anything, to display these particular posts? (category?) I assume it’s different from making the posts private? Is there any particular plugin that comes closest to what you want?