Clicking the "Remote Site Content" link on the configuration configuration page of Drupal Admin section returns a blank page.

This originally happened on an existing site using Domain Access. I also tried this on a fresh installation of Drupal and I got the same behaviour.

No help doc was provided with the module, so no abvious way tot try to debug.

Thanks for having a look at this.

Comments

solotandem’s picture

Are there any messages in the drupal watchdog log related to this blank page? Do you have site configured to display all error messages?

RYL’s picture

Hi,

On a fresh Drupal installation, I enabled the Remote content module, got the blank page from the admin...

The only message I saw in the Report section is :
Type page not found
Date Friday, November 22, 2013 - 20:21
User admin
Location http://dev2.ici-medias2.ca/favicon.ico
Referrer
Message favicon.ico
Severity warning
Hostname 70.53.234.56
Operations

Is this related ? Does it make sense ?

Thanks for following up. The Remote Content module seems to be very promising.

solotandem’s picture

Category: Bug report » Support request

Can not reproduce a blank page with fresh installation of latest Drupal 7.24.

Test sites are based on drupal 7.24, views 3.7, ctools 1.3, and remote_content 1.x-dev.
Configuration page at admin/config/content/remote_content displays with nothing to configure as the sites do not have any content types and only one database definition in their settings.php files.

I suspect the issue is the use of syntax that requires PHP 5.3+ on the settings page. Can you install PHP 5.3? Otherwise change line 47 in includes/settings.inc to be:
'#default_value' => isset($connections[$key]['url']) ? $connections[$key]['url'] : '',

The module info file does not list this as a dependency (and should, although we should all be on at least 5.3).

solotandem’s picture

Assigned: Unassigned » solotandem
Status: Active » Fixed

Marking fixed for two reasons:

  • lack of further feedback
  • if the blank page was related to PHP 5.3+ syntax, this was changed in this commit.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.