• Resolved muthmedia

    (@muthmedia)


    Hello, happy holidays to everyone.

    I don’t know if my problem is at all related to this person’s: http://wordpress.org/support/topic/344000?replies=16 but I’ve followed along with that thread and done the same steps that have been suggested; I’ve also gotten rid of my plug-ins; and even went into the MySQL database, and looked up the show_on_front, page_on_front and page_for_posts tables; which all looked correct to me.

    The website I’m working on is: http://findmillion.net and the page that’s supposed to be the home page is http://findmillions,net/about-us/ I’ve tried changing the front page setting to other pages; created a page actually called “home”, but nothing takes. If I change the “Posts Page” setting, that will change.

    Any ideas? Something that I’m missing?

    Thanks.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter muthmedia

    (@muthmedia)

    I’ve reinstalled WP 2.8 and still no luck…

    Any ideas?

    and here is another one but skip my last comment/lastline since you have the about-us page.

    http://wordpress.org/support/topic/343965?replies=9

    Did you create a totally empty page called blog or anything and select that one in your settings/reading?
    And how were you going to navigate to your blog?

    Thread Starter muthmedia

    (@muthmedia)

    henkholland, thanks for the reply, and that other topic is exactly what’s happening with my site. There is a blog page – it was linked from like the Contact us Page or something (the owner of the site wanted the blog there, but isn’t really using it, so he didn’t feel the need to highlight it in the main navigation.)

    The thing is, the site was working fine and then the other day he wrote and said it was messed up. When I looked at the files, there was some weird jumbly code, in the WP Admin section, where you edit the theme files. I took that all out; then I reuploaded everything. I have even gone into the database and manually changed the page_on_front/page_for_posts tables to be the correct number.

    The only thing I haven’t done was delete all the tables and just have a clean install. (I kind of thought that reinstalling WP would do that, but maybe not.)

    I also got the gzuncompress error a couple times, so I’m going to implement that fix here pretty quickly; but like the other guy this is a website for a client, and he kind of needs it corrected.

    Thanks. 🙂

    In your code I see:
    <meta name=”generator” content=”WordPress 2.8.6-beta1″ />

    I would change that for a stable 2.8.6 from here: http://wordpress.org/download/release-archive/
    I would suggest unpacking locally and ftp-ing at least wp-admin and wp-includes and the root files EXCEPT wp-config.php

    If Blog is an existing (empty) page it would normally turn up in the page menu and (even before) it is assigned to be the posts page under Settings/Reading. I just tested that in the default theme where every new page gets its navlink.

    Furthermore post 790 is containing stuff pasted directly from Word. (This is probably destroying the right-sidebar for me in IE7).
    Copy and re-paste the text in that post in Visual Editor using the Plain Text insert button (getrs you a popup window).

    Finally, for now: check here http://www.xhtml-css.com/check the coding. The first and only (x)html error is unknown to me but not nice.

    Thread Starter muthmedia

    (@muthmedia)

    What I did that seems to have worked was I exported the database, cleared the tables. Reuploaded WordPress (2.9) and then imported the database. So, I’m guessing there was something in the update from the v2.8 to v2.9 when my client-or whoever- updated it, that caused a conflict. And I’m assuming that it was the clearing out of the database that fixed whatever the error was; as I mentioned, I had already tried reuploading different versions of WP a couple times.

    Thanks for your help, Henkholland.

    Hope this might help, anyone else that has this issue. 🙂

    Hi muthmedia, good for you. Please mark this topic as resolved in the right hand column

    hi there,
    i had the same problem, didn’t find an answer that has solved the static frontpage problem for me….
    i then started looking at the plugins and themes that i’m using, and got to the bottom of the problem for me.
    the cause in my case was a variable called $debug in one of my plugins.
    i renamed it and the static frontpage worked!
    just in case anyone has the same…

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Reading Setting not accepting the change for new Front Page’ is closed to new replies.