prjg

The slug is viewable on the index page – at least it is on mine – https://petergreenwell.com right down the bottom (search for logout)

Mine does, and has done every time I’ve asked. Every time some idiot runs bots, open procxies or other crap and slams my site, my host has nuked it at the host level.

Reading other webmastering/hosting forums out there, it seems to be a fairly common thing granted if requested.

Doing it any other way, .htaccess or PHP or whatever, still means they get to you regardless, using up server time, log space, warp stats, etc, etc.

Just saying.

There’s no need for attitude here, you say. You’ve been given plenty of advice, most of it decent, and you continue to carp.

If you don’t like what you’re reading, oh well.

I think the PHP deny method is a kludge. They’re all kludges unless access is blocked at the host level.

That way, your site never gets to see any of the stuff you are currently seeing, and you say your host won’t do that.

What does that tell you?

It’d tell me, screw you, let me dump my sql and I’ll go find a host that actually has a clue. There are plenty out there.

You’re just head-butting a brick-wall otherwise.

That’s nuts. Time to find another host. If they don’t care about people slamming their servers, from things like automated open proxies and stuff, then that’s a real worry.

Find a good reputable host.

I’d do what the message says and check your server logs. They’re usually fairly descriptive. It’d be something silly like a misplaced period or whitespace where it shouldn’t be.

Thank you Kafkaesqui, that fixed it.

Any issues with simply FTPing the file into the target directory and adding its info to the DB somehow?

Honest opinion? It looks like 99% of all WP blogs. 50-60% page width, two column layout, square-ish header, eminently readable and somewhere between average and slightly above-average.

I’m seeing where it’s set in the default theme’s single.php

You say it’s in /public_html/ but where is WP looking for it?

WP automatically generates .htaccess.
Just make sure it’s CHMOD 644 (permissions).

WP can’t write to it with those permissions. Needs to be 666, PHP and apache run as “nobody” which requires world-writeable permissions.

Not quite related but,

Most of the robots you are blocking with the env matching rules obey robots.txt.

Realted, that .htaccess looks OK to me.

<?php if (is_home()) { ?>
<?php if (function_exists('wp_theme_switcher')) { ?>
<h2>Styleswitcher</h2>
<?php wp_theme_switcher(); ?>
<?php } ?>

That is what’s before it and this is the line that loads the Pages menu. If I remove this line it get rid of the error, but it also gets rid of my page menu :/

<?php wp_list_pages('sort_column=menu_order&title_li=<h2>' . __('Pages') . '</h2>' ); ?> `

Was going to say, it looks like 95% of all blogs out there at prima facie. Needs to be jazzed up a little like some of the others have said.

No can do. Either you or the other guy, but not both together.

That’s one of the design paradigms behind sessions to begin with.