WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] Preview of Scheduled Posts Sends User to Static Home Page (4 posts)

  1. hehafner
    Member
    Posted 10 months ago #

    I have WP set up as a blog on a static site. When my client creates a post on her blog and sets that post to publish in the future, she is no longer able to preview that post in a preview window. It takes her to the static home page. That static page is also broken in the preview.

    If the post is in draft, you can click on preview and can then preview the post, but I cannot do this in a "scheduled" post.

    -- I have checked the link in general settings to make sure it was correct.
    -- I reinstalled WP thinking that there was a corrupt file. Still have the problem.
    -- I uninstalled all plugins and still have the problem.
    -- I have tested this in another WP on another domain... I can't cause this to occur on another server.

    Can someone help me out?

    Thank you,

    Heidi Hafner

  2. esmi
    Forum Moderator
    Posted 10 months ago #

    Have you tried:

    - deactivating all plugins to see if this resolves the problem. If this works, re-activate the plugins one by one until you find the problematic plugin(s).

    - switching to the default theme to rule out any theme-specific problems.

    - resetting the plugins folder by FTP or PhpMyAdmin. Sometimes, an apparently inactive plugin can still cause problems.

    - re-uploading all files & folders - except the wp-content folder - from a fresh download of WordPress. Make sure that you delete the old copies of files & folder before uploading the new ones.

  3. hehafner
    Member
    Posted 10 months ago #

    I solved this problem. Apparently, the permalinks got changed on me. I have .htacess locked, so WP could not access the file to change the permalinks.

    All is working at this time!

  4. DaveKinskey
    Member
    Posted 10 months ago #

    hehafner...How exactly did you resolve the problem with the .htaccess? Is there a way to unlock it only for WordPress? Or does it just need to be completely unlocked? I'm having the same problem. My website uses Cpanel for administration. The problem is occurring in a beta WordPress version of my website, currently in a sub-directory for testing and design, in case that makes any difference. Is there something necessary to prevent security problems after unlocking the .htaccess?

Reply

You must log in to post.

About this Topic