Forum Replies Created

Viewing 15 replies - 1 through 15 (of 32 total)
  • Thread Starter prof611

    (@prof611)

    Thank you, Steven. I can’t believe that the solution is so simple, or that I didn’t notice it!

    I use CuteFTP, and the whole time I was investigating this issue I had both /include/ files sitting next to each other – and I never noticed it was missing on the server side!!!

    It takes an outsider sometimes to notice something so obvious! Thanks again!

    Professor

    Thread Starter prof611

    (@prof611)

    Thank you, t-p, for your quick and lucid reply. The procedure is perfectly logical, and it works. Don’t know why it’s not somewhere on WordPress. I’m sure other people must need to do this also.

    Thread Starter prof611

    (@prof611)

    Sorry I took so long to get back to you. There were no entries in the error log at all.

    I found out what was going on: When I uploaded the WordPress files to the server, my CuteFTP failed to load some of the files at the end of two of the folders. I went back and uploaded the three folders again – this time making sure they all got transferred. Then when I tried Step 5 again, it worked fine.

    Sorry to bother you, James – it was just a stupid mistake – not a bug at all!

    Thread Starter prof611

    (@prof611)

    Yes it does. It’s called Quick Installer. I didn’t want to use it, since it requires registering. I don’t want to have to become a member of a new organization in order to do something I should be able to do by hand. And I have installed WordPress many times before for my other blogs. I want to get to the bottom of this problem, not hack my way around it!

    Thread Starter prof611

    (@prof611)

    Thanks for your help. However, I DID do it manually. I filled in wp-config.php by hand, and then put simpleislandweddings.org into the address bar –> WSOD!

    Thread Starter prof611

    (@prof611)

    HostGator; PHP 5.4

    Thread Starter prof611

    (@prof611)

    I did some more research, and found that this and other jquery scripits are added to the <head> section by WordPress. Also found a plugin that will move them all to the footer: Scripts to Footer. A simple solution for us php-illiterates!

    Thread Starter prof611

    (@prof611)

    I now find that – even with the Yoast XML Sitemap being disabled – the webpage is being redirected to itself in an endless loop. This occurs whenever the permalink is anything other than the default, “/?p=xxx”.

    This is causing all external links to webpages on my blog to be redirected to the home page. It must be disconcerting for my visitors to click this link in Google search: tanning17.tropicalhouseplants.net/how-to-tan-armpits/ , and end up on the tanning17 homepage, with the offending link still visible in the Address Bar. What do they do now? Most will probably give up!

    Thread Starter prof611

    (@prof611)

    New information about this bug. I went to Google Webmaster Tools, and fetched a page on the blog, http://tanning17.tropicalhouseplants.net/tanning-news-snippets/ . Here is the error:

    Downloaded HTTP response:
    1 HTTP/1.1 301 Moved Permanently
    2 Server: nginx/1.6.1
    3 Date: Wed, 03 Sep 2014 04:14:42 GMT
    4 Content-Type: text/html
    5 Content-Length: 0
    6 Connection: keep-alive
    7 Location: http://tanning17.tropicalhouseplants.net/tanning-news-snippets/

    Somehow, the page has been redirected to itself, obviously causing an endless loop.

    This clearly shows what is happening. But the question remains: WHY is this happening?

    Thread Starter prof611

    (@prof611)

    I discovered the source of the bug described above. It came to me in a dream! It’s not a bug that anyone else will ever have, but it’s solution demonstrates a debugging principle that I was ignoring. So it may be applicable to others in a general sense.

    The debugging principle: if a script works on page 1, but not on page 2, then there must be something on page 2 that’s interfering with the script.

    In my case, the interfering script was the submitForm script. It was being used only on the Home page. So I deleted it, and the posts using the question & answer format worked properly. ( Now I have to rewrite the deleted script, so it doesn’t cause any interference – but that’s another problem altogether. )

    Thread Starter prof611

    (@prof611)

    I discovered where the plugin was getting the defunct URL used in the error message. It was in the database, so I corrected all four instances. Now I still get the same error message, but with the correct URL.

    I opened the XSL file mentioned in the error: http://www.your-homeremedies.professorsopportunities.com/herbalremedies/main-sitemap.xsl, but I can’t figure out what the error is.

    Can somebody who knows about XSL files please go to the above URL, and tell me what’s causing the error?


    Professor

    Thread Starter prof611

    (@prof611)

    I just searched one-by-one all of he files in the wordpress-seo plugin folder, and NONE of them contained my defunct blog URL, your-homeremedies.com.

    So where is the plugin getting this URL to use in its error message???


    Professor

    Thread Starter prof611

    (@prof611)

    Since nobody seemed to have any more suggestions, I took time off from this problem for a few days. As sometimes happens, when I decided to try again, I happened by chance to hit on a solution. It’s not an elegant solution, because I still have NO IDEA what went wrong or how. But I can now login to the blog again.

    All I did was to completely change out my wp-admin and wp-includes folders with brand new ones from the latest WordPress ver 3.9.1 !!!

    Thread Starter prof611

    (@prof611)

    Thank you all for the suggestions.

    MaxManX: Tried your suggestion using IE. Same error.

    perrij3: I was able to access all tables in the database.

    esmi: I looked at your link, but couldn’t make head nor tail of it – I’m not a guru. I don’t have Varnish (?). The only thing I could see to try was to remove <input type=”hidden” name=”testcookie” value=”1″ />, which didn’t change anything. The only other idea that came to me was to try reverting to an earlier version of WordPress. However, I didn’t do it because I have many other blogs that use the latest version, and they’re all working fine.

    I think the key to what caused this whole thing is that I bypassed the popup that requested me to login again. That’s the only thing that I did that I didn’t do with my other blogs. Does anybody have any ideas on what this mistake on my part might cause?

    Thread Starter prof611

    (@prof611)

    OK. I tried to do what you just suggested, but it had already been done.

Viewing 15 replies - 1 through 15 (of 32 total)