Forum Replies Created

Viewing 15 replies - 16 through 30 (of 45 total)
  • Thread Starter worldblogosphere

    (@worldblogosphere)

    Yes, correct.

    Thread Starter worldblogosphere

    (@worldblogosphere)

    It is in the root directory.

    Thread Starter worldblogosphere

    (@worldblogosphere)

    Ahh, well either way. I just hope they don’t decide to change anything.

    Thread Starter worldblogosphere

    (@worldblogosphere)

    After further review the info they sent explained how to change the file type. I don’t see how that is supposed to help anything. Whatever he checked in his test though changed the error I am getting.

    Now when you go to
    https://extraordinaryintelligence.com/index.php?s=news

    Scroll down and click Next Page you get the following error.

    Fatal error: Call to undefined function get_header() in /home/content/b/l/o/blogamerica/html/page.php on line 1

    The first line of page.php is of course the php code calling the header.

    Any thoughts on what I can do to fix this evolving problem?

    Thread Starter worldblogosphere

    (@worldblogosphere)

    Thanks for responding even though it seems I might not need it anymore. I was prepared to make each folder if I had to switch.

    Hopefully this post will help someone in the same situation.

    Thanks again.

    I just had a very similar issue after moving my 2 year old blog to GoDaddy. I went to the DNS manager and put in a new DNS record for the wildcard domain *.yourdomain.com (The same place you used to set your A record). After a couple hours it seems it propagated and all the subdomnain sites that had been created since I moved to the new server were working. This was just a couple hours after GoDaddy told me I could not add the subdomain into the httpd.conf or VHOST files.

    Not sure if it will work for you, I am still not sre why it is working for me even. lol

    Thread Starter worldblogosphere

    (@worldblogosphere)

    OK, this is odd. Since GoDaddy said I can’t add the line of code (ServerAlias *.example.com) to server file httpd.conf I was on my way to delete the wildcard domain I created in the DNS records. Right before clicking delete on it since it was no useless I decided to check something.

    I went and created a new blog site and it worked! Then I went and checked all the spam blogs that were created last night that weren’t working and they were working too! So apparently WordPress doesn’t need both portions of this instruction…

    1. Apache must be configured to accept wildcards.
    1. Open up the httpd.conf file or the include file containing the VHOST entry for your web account.
    2. Add this line:

    ServerAlias *.example.com

    2. In the DNS records on your server, add a wildcard subdomain that points to the main installation. It should look like:

    A *.example.com

    Am I the only one that this works for? Has anyone else tried it?

    Thread Starter worldblogosphere

    (@worldblogosphere)

    Making that switch won’t have adverse affects on blogs already in place? Will I have to go make a separate folder for each in the subdirectory setup?

    Thread Starter worldblogosphere

    (@worldblogosphere)

    Well GoDaddy ran some tests and they say everything is parsing correctly. They say the issue is with an incomplete header. They have sent me the information to fix it, but I haven’t gotten to that point yet.

    Thanks again for all the help.

    Thread Starter worldblogosphere

    (@worldblogosphere)

    Sorry, I didn’t link back to it.

    The switch I meant was from Host Gator servers to the GoDaddy servers as I explained in my previous post that I didn’t link to.

    Just got off the phone with GoDaddy.

    They said on a shared server account I cannot have a change made to put in the wildcard subdomain. I would have to switch all the way up to their fully dedicated server in order to be able to change the necessary file. Not sure we can afford that at the moment. (Jump from $15 to $70 a month.)

    Is there anyway for me to switch from subdomain to subdirectory? My WordPress site was originally made about two years ago, but the move was just this month with a new install of WordPress followed by replacing the new files and database with the old ones.

    Thanks for any advice. (I also got an answer from them on the pagination issues in the above linked post. Going to update it in a minute.)

    Thread Starter worldblogosphere

    (@worldblogosphere)

    Thanks again ipstenu.

    I came across a new issue thanks to the spam sign ups I have been getting, but I am putting it in a new post since it is completely unrelated.

    Thread Starter worldblogosphere

    (@worldblogosphere)

    Thanks for the quick response ipstenu! All the updated code is in now and seems to be working. Thanks.

    So did anyone have any thoughts on how to fix the pagination problem?

    It seems the only problem I have left is pagination in many places. Here is an example of what I am talking about.
    https://extraordinaryintelligence.com/index.php?s=news

    Scroll to the bottom and click Next Page.

    Thread Starter worldblogosphere

    (@worldblogosphere)

    Thanks Andrea and ipstenu!

    The bottom single WP one I put in there manually in an attempt to fix it. What was actually in there was missing a couple lines. I didn’t realize it was for single version.

    I actually do have a subdomain setup. What is it that needs to be different?

    Thanks again for the help.

    Thread Starter worldblogosphere

    (@worldblogosphere)

    I have no clue how the two bits of WP code got in there, thought it looked very similar. How do I tell which is correct?

    RewriteCond %{REQUEST_FILENAME} -f [OR]
    RewriteCond %{REQUEST_FILENAME} -d
    RewriteRule . - [L]
    RewriteRule  ^([_0-9a-zA-Z-]+/)?(wp-.*) $2 [L]
    RewriteRule  ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
    RewriteRule . index.php [L]

    That one or this one?

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

    As for the Super Cache code, that is the exact code it loaded on its own. Is there not supposed to be that much?

    I can’t seem to find the link back to the Antispam code. Is there any reason it would be causing people to not be able to comment on posts? People were getting page not found erros when clicking submit.

    Thread Starter worldblogosphere

    (@worldblogosphere)

    Hi Andrea,

    Getting this direct from my GD panel…

    OS/Hosting Type: Linux/Shared Hosting

    with PHP 5.X if that matters.

    Main reason I asked about the htaccess file being updated was because I was trying to clean it all out. I had to remove the Antispam code suggested by WordPress (and you I believe) because with it in people couldn’t comment about half the time. That was for known members too, not just new people.

    Does the rest of the htaccess file look normal?

    Thanks for the help.

Viewing 15 replies - 16 through 30 (of 45 total)