Anthology of Ideas

I hate to bother you but am having a devil of a time with “more” and “back”. It works beautifully on another site of mine but on this reunion site, when you log on to this site, the “more” button does not work. If you go “back” and click on it again, it does work the second time.

This problem exists on both Firefox and IE.

Any help would be so appreciated.

Thanks

1. Aaron posted the following on June 16, 2007 at 12:37 pm.

   I have looked at your website and there seems to be an error with server permissions. Are the two sites on the same server?

   Reply to Aaron

We are back working on this site once again. “We” includes my friend and programmer (Michael Sky) and me, trying to fix the problem.

When you go to our site (http://www.yale58.org/news.php), on the home page down a bit, there are 2 WP posts: one a letter from Linus Travers and the other a letter from Harry Harlow. In both letters, we have put “more” after the 1st paragraph.

Whichever one you go to, the 1st time you click on more, nothing happens. The second time it and the other “more” on the other post work great. Why? Why don’t they work the first time?

I love the plug in, I love the concept but we have over 800 classmates with access to this site and we are frustrated by this weird problem.

Russell Lee Post

1. Aaron posted the following on June 23, 2007 at 6:50 pm.

   I have looked at your website and there seems to be an error with server permissions. Are the two sites on the same server?

   Reply to Aaron

Hi Aaron, this is Michael Sky, the designer/coder for yale58.org. I’ve been putting off writing until I really had a grasp on what’s happening with this site and INAP.

It’s very weird. We have INAP comments working perfectly on all browsers here:

http://www.yale58.org/global-warming/

This is a wp Page, with standard URL.

But we can’t get more/back working. Typically the first time you click, nothing happens. The second time it works, throughout the site. And if you come back to the page a week later (and haven’t flushed your cache during that time) it still works.

But after cache flush, or on new computer, it always fails the first time.

I thought the problem might be that I am using WP in a non-typical way, with pages at the root level of the site, ie:

http://www.yale58.org/news.php

But when I try this on the basic index page (inside of wp-content) it acts even weirder, sticking the post plug into the url.

I’ve tried all sorts of variations of INAP preferences. I’ve tried the 2.3 version — was even buggier.

If it’s a permissions problem, what files do I need to change permissions on?

We much appreciate all the work you’ve put into this, and any help you can give us. I’ve just donated money to your paypal acct.

thanks,

Michael Sky

1. Aaron posted the following on June 28, 2007 at 12:42 pm.

   Ironically I found out what the problem was because of the donation: I saw the notification email, so I went to the site that the payment came from and found that that site also has the same permission problem. Actually I’m a little embarrassed now because it is a problem I’ve had to deal with before.

   The problem is with the server/Wordpress settings, but is fairly easy to fix. AJAX (the technology INAP runs off of) does not allow you to send data to another website. (I could not use it to get a list of Google search results and display it in this page.) However, because of the way the internet was designed, it also sees http://www.anthologyoi.com as a different website than http://anthologyoi.com.

   If you go to the URL http://yale58.org/news.php and try to click the link INAP tries to get the information from the URL in your WordPress settings; however, you have it set as http://www.yale58.org, so even though everything is working correctly the security in the server itself blocks the request because it thinks you are trying to get information from a different website.

   By blocking the request, it causes an error in the Javascript and INAP stops trying to load the data in-line and just goes to the page automatically. (This is what we want it to do, so it doesn’t block the user from seeing the page if their browser is incompatible.) Once it is on that page the base URL is www.yale58.org, so when you click it again and try to request data from www.yale58.org the server sees that it is the same site and allows it to continue without interruption.

   If you go to the URL http://www.yale58.org/news.php this doesn’t happen and everything works fine.

   Explanation done, now the fix:

   The problem is being caused because users can go to either www.yale58.org or yale58.org, but WordPress only is able to use www.yale58.org because of the way it works. Now changing the default WordPress URL to yale58.org isn’t enough, because then someone could still go to www.yale58.org and you would have the same problem in reverse.

   So what you need to do is tell the server that only one of the URLs should be used, and this can be done by automatically by redirecting all requests from yale58.org to www.yale58.org.

   The easiest way to fix this is to open the .htaccess file that is in the root of your website and add the following lines.

   1. <IfModule mod_rewrite.c>
   2. RewriteEngine On
   3. RewriteCond %{HTTP_HOST} ^yale58\.org
   4. RewriteRule ^(.*)$ http://www.yale58.org/$1 [R=301,L]
   5. </IfModule>
   6. Use the following to copy and paste the code.
      <IfModule mod_rewrite.c> RewriteEngine On RewriteCond %{HTTP_HOST} ^yale58\.org RewriteRule ^(.*)$ http://www.yale58.org/$1 [R=301,L] </IfModule>

   The effects of this change (but redirecting all requests with the www.) can be seen on this site ( http://anthologyoi.com versus http://www.anthologyoi.com ) clicking the latter will still send you to the main site.

   I’ve also sent you an email.

   Reply to Aaron
2. Aaron posted the following on June 28, 2007 at 12:57 pm.

   Also, I would suggest doing the same for your other website running INAP. (For privacy I won’t post it here, but just change the URL in the script I’ve already posted.)

   Not only does it allow AJAX to flow seamlessly, but it also makes your site easier for users and search engines like Google.

   Reply to Aaron