OK, HTTP 403 means “Forbidden”. But I found no indication about this in the bible2.net server log. So sorry, I have no solution so far. Would you consider the following questions?
1. Is your server configured to block outgoing requests?
If you put the following lines into the your server’s root folder as file loadtheword1.php and enter the address for your site YOURSITE.org in your browser as http://YOURSITE.org/loadtheword1.php, does it show “OK”?
<?php
$Xml = simplexml_load_file("http://bible2.net/service/TheWord/twd11?format=atom");
echo "simplexml_load_file "
. ($Xml ? "" : "NOT ")
. "OK.<br />";
or extended with some heuristic settings:
<?php
ini_set("user_agent","Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)");
ini_set("max_execution_time", 0);
ini_set("memory_limit", "10000M");
$Xml = simplexml_load_file("http://bible2.net/service/TheWord/twd11?format=atom");
echo "simplexml_load_file "
. ($Xml ? "" : "NOT ")
. "OK.<br />";
2. Otherwise: does your wp-config.php contain the following line?
define('WP_HTTP_BLOCK_EXTERNAL', true);
In this case, you could allow access to bible2.net by adding
define('WP_ACCESSIBLE_HOSTS', 'bible2.net'); # comma separated
3. Is your site run behind a proxy?
4. Is there any info in your WordPress logfile?
To inspect the WordPress logfile, create a file called debug.log, make it server-writable, place it in the wp-content directory, and add to wp-config.php:
define('WP_DEBUG_LOG', true)
ini_set('error_log', WP_CONTENT_DIR . '/debug.log');
Then configure the widget and inspect the debug.log file for info.
Ensure to undo all changes after the testing.
