HSteeb

Dear Henry,

the “cURL error 7” mentioned in the log means “Failed to connect to host.”, which indicates for some reason the plugin in your WordPress installation does not reach out to “https://bible2.net/service/TheWord/twd11?format=atom” to fetch the required information.

I see this is the same effect reported in your related support query about Font Awesome few days ago (https://ww.wp.xz.cn/support/topic/activation-failed-17/).

The author of that plugin made a good explanation, trying curl directly on your server to access the other host. Unfortunately, I have nothing to add to these points. Accessing information from an outside host is crucial for these plugins. The Word Widget uses multiple PHP methods listed in the log – all of them fail, so obviously the reason is more fundamental. Hope you get a clue on this with your provider.

Very sorry for that!

Unfortuately, 2017-03-16 the Sociedade Bíblica do Brasil terminated the permission to publish The Word using the Portuguese Almeida Revista E Atualizada. We thank the Sociedade Bíblica do Brasil for kindly granting permission to use the text so far! I asked to extend the license, but they refused to grant it.

Any help to handle this would be welcome. Maybe someone to contact them, or another Bible edition where we can get the license.

I’ll update the widget info page to reflect this change.

Original announcement:

http://bible2.net/2017/03/portuguese-almeida-revista-e-atualizada-permission-terminated/

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.

Do you still have the same effect? It works for me.
What’s the WordPress version?

Hi Dawson,

(sorry for late reply – I didn’t get a notice about your question, or maybe overlooked it)

This looks like your PHP environment does not allow access to the remote URL of bible2.net. I do not yet have a solution for this, but maybe you can help find one! Would you try to create a file called php.ini with the line

allow_url_fopen=on

in the folder of the widget (typically wordpress/wp-content/plugins/the-word-widget/) and in the sub-folder includes there?

If this does not help, to find an alternative way that works, you might fetch the zip file

http://bible2.net/download/dev/2014-10-06_test_simplexml_load_file.zip

and put the 4 contained .php files in some folder on your server, then open them in order in your browser (the php.ini in the zip file is just the same as described above).

1. loadtheword0.php just reports the setting of allow_url_fopen.
2. loadtheword1.php uses the same mechanism as the plugin (simplexml_load_file).
3. loadtheword2.php uses slightly modified code (setting user agent, memory limit…).
4. loadtheword3.php uses a rather different mechanism curl.