Pages (the non-Post things) are not fetchable

  • Resolved paul

    (@paul)


    16 years, 9 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 15 replies - 1 through 15 (of 20 total)
1 2
  • Thread Starter paul

    (@paul)

    16 years, 9 months ago

    OK, I created a Post, verified that it worked, then went into the DB and made it a Page. Eventually, the UI sees it (in the Manage Pages area) and it appears on the published site as a Page, but it can’t be viewed/fetched.

    Something skwewy going on awound here . . .

    moshu

    (@moshu)

    16 years, 9 months ago

    went into the DB and made it a Page.
    How did you do that?

    Thread Starter paul

    (@paul)

    16 years, 9 months ago

    used a tool to look at the DB (I use CocoaMySQL): changed post_type to page (from post).

    moshu

    (@moshu)

    16 years, 9 months ago

    Are you sure the post_status hasn’t been changed? It should be “publish” for both posts and Pages.

    Also, the other day there was a post here in the forum about the “safeinclude” plugin… as not being safe at all.

    Thread Starter paul

    (@paul)

    16 years, 9 months ago

    Are you sure the post_status hasn’t been changed? It should be “publish” for both posts and Pages.

    No, it’s set as published. The use of safeInclude doesn’t seem to have any effect on whether the Page is viewable or not. I can take out the call to the plugin. I still don’t see the page (I get

    Its not here anymore !
    The page or post that you are looking for is not found.
    Please try searching through our Archives, or contact the administrators to report the problem.
    )

    Also, the other day there was a post here in the forum about the “safeinclude” plugin… as not being safe at all.

    Well, that’s as may be. I’m more concerned with why and how I can make Pages work in 2.2 as they did in 2.0 and 2.1.

    Has anyone addressed the security issues with the developer?

    ccoupe

    (@ccoupe)

    16 years, 9 months ago

    Try calling up the page with it’s ugly URL. Then check your error log or modify the 404 error template to report more info about the query string/

    Thread Starter paul

    (@paul)

    16 years, 9 months ago

    the ugly URL? you mean by ID number? nothing doing there. Pages can’t be called that way, apparently.

    Thread Starter paul

    (@paul)

    16 years, 9 months ago

    I just dumped my database with create statements and grepped out the insert: I suspect something may have gotten out of whack when I moved it between hosts, moving from 4.something to 5.1.

    [long code moderated – use http://wordpress.pastebin.ca ]

    ccoupe

    (@ccoupe)

    16 years, 9 months ago

    if your.site.com/?p=nnn doesn’t work where nnn== “the post_id” you changed to “page” status then you’ve fixed your .htaccess in some strange way.

    moshu

    (@moshu)

    16 years, 9 months ago

    For Pages it shold be example.com/?page_id=XX
    /?p=YY – works only for posts!

    Thread Starter paul

    (@paul)

    16 years, 9 months ago

    excellent, moshu, now we’re getting somewhere. That works. I do get the page returned when I use that syntax. Now why doesn’t the fancy link work, I wonder?

    I just redid the permalink structure/updated .htaccess. seems to work OK for everything except now NO pages work: I have insert index.php/ before the pagename to get it to load.

    And that one stubborn Page still won’t load unless I request it by number. 

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

# END WordPress
    moshu

    (@moshu)

    16 years, 9 months ago

    No, nothing works when it comes about the permalinks:
    http://paulbeard.org/wordpress/2007/07/09/quote-of-the-day-48/
    You may want to set them to default and verify it they work.

    Further, make sure to ask your host that mode_rewrite and AllowOverride is enabled on your server.

    Thread Starter paul

    (@paul)

    16 years, 9 months ago

    OK, I think I have un-broken that. I am my own host, so it was easy to get an answer 😉

    I know mod_rewrite is on and am pretty sure AllowOverride is good: this all worked, except for one Page, just yesterday, after all. That page still doesn’t work unless called by number and now all Pages need to have “index.php” typed in from front of their names before they work.

    moshu

    (@moshu)

    16 years, 9 months ago

    I am my own host,

    Unfortunatley, that tends to be the worst case scenario – where we cannot really help. We don’t deal with server setup issues. Don’t even ask 🙂

    But your permalinks now don’t work. Click on any post title and you get a 404.

    Thread Starter paul

    (@paul)

    16 years, 9 months ago

    Well, by saying that, you’re making it sound like WordPress is hard to integrate and we both know that ain’t so.

    I guess I’ll have to go to the codex and see if I can find the setup requirements.

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