WordPress.org

Ready to get started?Download WordPress

Forums

Preview Post - Returns 404 (5 posts)

  1. RomanT
    Member
    Posted 7 years ago #

    Just updated to 2.2.1.

    I went to add a post, and wanted to see what it rendered like, prior to posting it.

    Unfortunately it is shown in the preview pane as 'not found' - a normal 404 error.

    Apart from upgrading to 2.2.1 - as far as I know, nothing has been changed.

    Any ideas?

    Thank you.

  2. wingnut2600
    Member
    Posted 6 years ago #

    I am having the same issue and would like some guidance into possible reasons for this error.

    When I attempt to preview a page from a saved draft, I go to the proper-looking link (e.g. http://www.pressuretobear.com/?p=45&preview=true), but I receive the 404 text in lieu of the previewed information.

    I am currently using WP 2.3, and this is somewhat irritating as I have to post something, then look at the published post, then edit it, see how it is working, then continue the chain until this works.

    This is a pain in the ass if anyone were to be an ATOM subscriber.

  3. letsknit2gether
    Member
    Posted 6 years ago #

    I am also experiencing this. I have set up my blog in htt://letsknit2gether.com/blog1 but access it via http://letsknit2gether.com. In my test environment http://creativeartstechnologies.com I have not set up this redirect and the draft preview seems to work fine.
    I am running 2.3.1

  4. swag
    Member
    Posted 6 years ago #

    Just started experiencing this with the first time since my upgrade to 2.5.1 this week.

  5. swag
    Member
    Posted 6 years ago #

    OK, I think I found the root of the problem. It has to do with how the WordPress codebase handles installs on one subdomain when the posts show up on another subdomain.

    This used to be a maddening problem with the basic post management screen. The main post management screen would hit "www.domain.com/mysubdomain/wp-admin/edit.php" just fine. But click on the pagination for it, and the WordPress PHP file would flip to "mysubdomain.domain.com/wp-admin/edit.php?paged=2" and result in a 404.

    Now I see that the preview PHP is introducing the same mistakes that the edit.php files finally fixed in WordPress: previewing to the URL "www.domain.com/mysubdomain/?p=45&preview=true" works like a charm and comes up fine. But now the preview function is forcing "mysubdomain.domain.com/?p=45&preview=true" which returns a 404.

    Maybe there's an .htaccess URL remapping hack I can use here. But really -- there's no reason why WordPress should fix this problem in edit.php and at the same time introduce it in the preview URL generator.

Topic Closed

This topic has been closed to new replies.

About this Topic