static pages

Is your .htaccess writable?

I had the very same problem. The reason was, that I first edited my .htaccess manually and later let WordPress edit it. That resulted in double mod_rewrite rules, as WordPress adds begin and end comments to it’s automatically written edits, but not to the generated code for manual copy&paste edits.
Just remove any double rewrite-rules and keep those with the WordPress comments around.

I suggest WordPress should also generate the comments for the copy&paste code to avoid such problems.

Also check your server’s configuration allows you to override settings using .htaccess. Chances are it’s already set up like that though, unless you’ve installed Apache yourself.

Thank you! I knew it just had to be something simple :p

.htaccess writable?

Are you suggesting to chmod the .htaccess file? At the moment, It is in 644 mode (Owner: read/write; Group: read; Public: read).

I have the same problem: I created a new page (About), put some dummy text to test it, and I always end up on my 404 file.

See for yourself: https://baudesign.ca/wp/

When I write a page. I don’t get /pagename . . for a page link.,

I get /?page_id=xxx

I thought for a moment that the problem could have come from the Kubrick theme, but no. I have the same problem event with the default (and ugly) green theme.

Is there anybody experiencing the same problem: no page, or no “static” page?

baudesign, WordPress needs to write to .htaccess everytim you create/delete a Page. Try chmod 666 to see if that works.

normgregory, Do you have permalinks working for porsts/categories/etc.? Try updating your permalink structure from Options->Permalinks (as in, click the button – you shouldn’t have to actually change your structure).

mdawaffe, thanks for the idea. But no, it does not work or change anything. I have created another “page”, called Test, after I chmod to 666, and the problem is still present: page 404.

Now, this has to be a bug of some kind. Look at what I can read from the Admin panel:

Post Preview (updated when post is saved)
Test
Filed under: Tips & Tricks a€?? @ 17:09

Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. […]

“Tips & Tricks”! This is one of my “categories”. Not a page. Now, what is wrong with this page feature?

Pages get “filed under” the default category. It’s a bit of a kludge – the database requires they be in some category, so the default it is, even though they really aren’t associated with any category. Is Tips & Tricks the default category? Or is it Category #1? (I forget just how it works).

If you edit .htaccess, do you see lines for /test ?

mdawaffe,

You asked: If you edit .htaccess, do you see lines for /test ?.

The answer is no. This is what I see:


RewriteEngine On
RewriteBase /wp/
RewriteRule ^archives/category/(.*)/(feed|rdf|rss|rss2|atom)/?$ /wp/wp-feed.php?category_name=$1&feed=$2 [QSA]
RewriteRule ^archives/category/?(.*) /wp/index.php?category_name=$1 [QSA]
RewriteRule ^archives/author/(.*)/(feed|rdf|rss|rss2|atom)/?$ /wp/wp-feed.php?author_name=$1&feed=$2 [QSA]
RewriteRule ^archives/author/?(.*) /wp/index.php?author_name=$1 [QSA]
RewriteRule ^archives/([0-9]{4})?/?([0-9]{1,2})?/?([0-9]{1,2})?/?([_0-9a-z-]+)?/?([0-9]+)?/?$ /wp/index.php?year=$1&monthnum=$2&day=$3&name=$4&page=$5 [QSA]
RewriteRule ^archives/([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([_0-9a-z-]+)/(feed|rdf|rss|rss2|atom)/?$ /wp/wp-feed.php?year=$1&monthnum=$2&day=$3&name=$4&feed=$5 [QSA]
RewriteRule ^archives/([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([_0-9a-z-]+)/trackback/?$ /wp/wp-trackback.php?year=$1&monthnum=$2&day=$3&name=$4 [QSA]
RewriteRule ^feed/?([_0-9a-z-]+)?/?$ /wp/wp-feed.php?feed=$1 [QSA]
RewriteRule ^comments/feed/?([_0-9a-z-]+)?/?$ /wp/wp-feed.php?feed=$1&withcomments=1 [QSA]

??

I wonder what’s wrong here.

For me, this problem seems to be related to the value of the $home_path variable that WordPress uses to determine if .htaccess is indeed writeable. My site is hosted at Dreamhost, and I am running php as a cgi, not as an Apache module. I added some debug code to ‘wp-admin/options-permalink.php’ in order to see what value was stored in the $home_path variable. The value was ‘/dh/cgi-system/php.cgi/.htaccess’ which is absolutely not where my .htaccess file resides. Dreamhost offers the option to run php as either cgi or Apache module. I am going to switch to the Apache module option and see if this doesn’t solve the problem.

Edit: Hacking in the correct path to my .htaccess file seemed to solve the problem. I’d rather run php as cgi on a shared host for security reasons.

The fact that WordPress apparently can’t/doesn’t determine the correct path to .htaccess in all situations leads me to believe this is a bug (I don’t recall seeing a requirement that php cannot be run as a cgi).

Creating, chmoding and updating .htaccess did it.

Via Permalinks I used the /%year%/%monthnum%/%day%/%postname%/ structure.

Thanks mdawaffe . … I never would of thought of it.

Ok, I am just about to quit and forget about this “page” option.

When I try to edit the Test “page” that I created (which points nowhere) by changing the “Page Template” (a drop down box option), my options are:

Default Templates
Archives
Links

Now, what are “Archives” and “Links” doing there? I should have had “Default” and “Classic”.

Should me problem be redirected to the bug bin?