Troubleshooting

If chirrup doesn't seem to be working, the best way to debug it is to either use Firebug to look at the data being sent from Chirrup to your page, or to simply visit http://url.for.your/chirrup/installation/?ui&url=http://any.url/ in a browser and look at the text output.

Q: I get a 404 error when trying to load the Chirrup javascript.

You most likely have the URL wrong - check where you installed Chirrup. Make sure the place you installed it is accessible from the web and that you have the correct URL for it.

Q: I get a 50* forbidden error.

You most likely need to check the permissions on the Chirrup installation folder. Make sure that the user account under which your web server runs has read, write and execute access to the folder and contents.

Q: Chirrup says something about curl not existing

Curl is most likely not installed, not enabled or not correctly configured on your server.

Q: Chirrup says it can't write to reply_cache.xml

Make sure that the permissions on your xml folder and all files within it allow the web server to write to it. If you changed the location of the file in chirrup_config.php, make sure that you specified the correct location.

Q: When I post a comment, Chirrup is posting normally and not with AJAX.

Chirrup recognises that the page you're for which you're showing the comments exists on a different domain to your Chirrup installation. Since many browsers forbid AJAX requests between domains, Chirrup will fall back on a traditional form post. If you have Chirrup installed on the same domain as the page on which you're using Chirrup, and Chirrup is still using traditional POSTs, please file a bug (see the "Filing a Bug" heading in readme.markdown.). Bonus points for including the URL of your page, the URL of your Chirrup installation, a way of contacting you, and the source of your page.