Recent activity
Subscribe to this feed
Jure K replied on July 15, 2009 16:02 to the question "Why won't this work?" in Zemanta:
Jure K replied on June 17, 2009 22:45 to the question "uploading pictures to amazon s3" in Zemanta:
Jure K marked one of Gasper Koren's replies in Zemanta as useful. Gasper Koren replied to the problem "I can't get it to work in wordpress 2.8!".
Jure K marked one of Gasper Koren's replies in Zemanta as useful. Gasper Koren replied to the question "Flickr and Wordpress 2.8 issues.".
Jure K replied on June 11, 2009 07:07 to the question "Flickr and Wordpress 2.8 issues." in Zemanta:
Jure K replied on June 11, 2009 07:05 to the problem "I can't get it to work in wordpress 2.8!" in Zemanta:
Jure K replied on December 06, 2008 21:34 to the problem "Zemanta 0.5.0 not working in Wordpress 2.6.2" in Zemanta:
Jure K replied on December 06, 2008 15:05 to the problem "Zemanta 0.5.0 not working in Wordpress 2.6.2" in Zemanta:
Your web server is serving you the php file as is instead of executing it.
Without reading your web server's configuration, I can only guess as to what is actually amiss here. First off, I'd recommend checking your json-proxy.php has execute and read permissions for the user that runs the web server (there's no harm in making it executable to everyone, i.e. all three execute bits on unices and adding execute permission to Everyone in windows, since the whole web should be able to do it anyway).
To further narrow it down, you could create a test.php file beside your json-proxy.php file in the zemanta plugin directory and put <? echo "test"; ?> in it. If you then open [blog url]/wp-content/plugins/zemanta/test.php it must return only the string "test" - or your php scripts don't get executed, which definitely is a web server configuration issue.
Jure K replied on December 01, 2008 10:15 to the problem "WordPress 2.6.3 balks" in Zemanta:
It's most likely your wordpress misreports your root URL, which makes our testing code request an URL that gets redirected to the "real" URL.
If you have access to your web server's log files, can you paste the log entry of the POST request that gets a 301 status response, so we can see which URL we're requesting, instead of /wp-content/plugins/zemanta/json-proxy.php, which apparently is where your 301 redirect points to?
Loading Profile...
