Pages (the non-Post things) are not fetchable

  • Resolved paul

    (@paul)


    17 years, 8 months ago

    So the terminology of this could use some decrypting. Here’s the story. I have moved my database/webserver to a new host sometime back. [edit: I have seen some issues with table creation stuff not being done properly, namely autoincrement on IDs having to be fixed on some tables. So I suspect there may be more wrongness in there somewhere.]

    Recently, I wanted to create a new static Page, using the safeInclude plugin. Works fine for me on previous instances. But now for some reason, I can create a Page in the admin UI, edit it, but it can never be displayed. No post with that numeric ID can be fetched. What’s the deal here?

    I just changed it from a Post to a Page: still no luck. It’s in the database and it looks like any other item (as I look at the other fields in that entry). Is there some meta data that needs to be fiddled with?

Viewing 5 replies - 16 through 20 (of 20 total)
  • Thread Starter paul

    (@paul)

    Hmm, it looks like no matter what I change in the UI, .htaccess never changes. My guess is that’s not the correct behavior.

    Yes, I just made a lot of changes via the UI and the .htaccess file never changes (though mod times is updated). I can move it aside and have WP create a new one, same as the old.

    is that a feature?

    My guess is that’s not the correct behavior.
    Your guess is wrong ??
    The htaccess is always the same – since 2.x – and the rewrite rules are handled internally. However, for some mysterious reason (don’t ask, I am not a coder) htaccess has to remain writable when creating a new Page. This is based purely on empirical experience…

    Thread Starter paul

    (@paul)

    Well, then why does this page exist if .htaccess is static and all the magic happens internally?

    I’m not saying it doesn’t happen that way: my old .htaccess contained nothing more that the mod_rewrite invocation. But it does seem confusing to have a lot of stuff on manually maintaining a file that never needs to be changed.

    Thread Starter paul

    (@paul)

    If I am reading this right, I never did have “pretty printed” permalinks, but PATHINFO. I always had index.php in there.

    So how do I get back to that?

    mod_rewrite works. there is a valid .htaccess file. 

    # BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /wordpress/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /wordpress/index.php [L]
</IfModule>

    What needs to happen to make these permalinks work again?

    wordpress/index.php/archives/%year%/%month%/%day%/%postname%

    If this isn’t handled in the .htaccess file it must live in the database. Else how would these setting survive a restart?

    Thread Starter paul

    (@paul)

    Just to resolve this, the answer is here.

    The synopsis: the rules are stored in the database, as the field “rewrite_rules” in the table wp_options. Simply cleaning out that field and forcing a rebuild through the usual steps was all it took.

    That sounds like a misfeature to me: not everyone is going to be thrilled at the prospect of monkeying with their database directly.

Viewing 5 replies - 16 through 20 (of 20 total)
  • The topic ‘Pages (the non-Post things) are not fetchable’ is closed to new replies.