Hello --
I found this error listed in forum message "http://drupal.org/node/686038" but have not been able to find a satisfactory solution. I'm running an Ubuntu installation with Apache 2.2.16, PHP 5.3.3-1ubuntu9.1, and import_html version 6.x-10. HtmlTidy is present and seems to be working.
The module 'sees' the static site, lists all pages to be imported, allows me to select multiple pages and images, then gives me the following error messages for each page:
* warning: Parameter 2 to menu_import_html() expected to be a reference, value given in /var/www/includes/module.inc on line 483.
* warning: Parameter 2 to node_import_html() expected to be a reference, value given in /var/www/includes/module.inc on line 483.
* warning: Parameter 2 to path_import_html() expected to be a reference, value given in /var/www/includes/module.inc on line 483.
* warning: Parameter 2 to taxonomy_import_html() expected to be a reference, value given in /var/www/includes/module.inc on line 483.
* warning: Parameter 2 to user_import_html() expected to be a reference, value given in /var/www/includes/module.inc on line 483.
* No body content found in this node
Checking the sites/default/files/import... folder reveals that the images have been successfully copied and a matching file for the static page exists with a .tidied.html extension - that file is in fact the exact body content I would like to see imported as a Drupal node. I'm pretty sure that since I see the both the images and the .tidied file that the write permissions on the destination folder are set correctly.
The original posting at node http://drupal.org/node/686038 was marked as "Edited by WorldFallz - moved to appropriate forum.", but without a link to where it was moved.
Thanks in advance for any help in the right direction ...
Comments
Comment #1
dman commentedThanks for a nice report.
The 'moved to appropriate forum' means that that issue was shifted from (wherever) into the place you found it. But because it wasn't reported here (as you have done :-) I never saw it.
It does sound like something that only shows up in php5.3, which I admit to not testing for a while. Now it's the end of 2010, I should take it seriously.
I've been steadily squashing trivial issues as I found them in the dev version although I haven't released a 'stable' update for a long while.
I can't recall hitting this one precisely but it may have gone away sometime in the last half-year, as part of other code clean-ups (it's being thrown because of an undefined object somewhere).
Can I suggest you try the current -dev version, and if it's still a problem I'll try upgrading one of my boxes to 5.3 and see if I can replicate.
Comment #2
teschek commentedThank you for the quick response. I'm currently away from the host computer for a week, but I do recall trying the .dev version of the import_html module. It returned another set of error messages, and no files at all in the sites/default/files/import... destination folder. The 6.x-1.0 version at least got me part way ;). When I return to work I'll install the .dev version again and list the error messages.
I did have this module (6.x-1.0) working under a previous version of Ubuntu (with the LAMP stack and Drupal automatically installed from the repositories). This error cropped up when I did a complete wipe and re-install of the latest Ubuntu, which I believe included the update to php 5.3.
Comment #3
teschek commentedHello --
I am pleased to report that we have a successful import using the new 2011-Jan-09 dev version. I do see the following error message:
warning: Parameter 2 to menu_import_html_after_save() expected to be a reference, value given in /var/www/includes/module.inc on line 483.
but the nodes are correctly created. There is one small problem, in that the node aliases are created without an .htm extension, in spite of the fact that I have "Legacy Aliases" checked in the Replication Options section. So far this hasn't been a problem, as the "Try to Relink Files by discarding suffixes" seems to work fine when modifying the embedded page links.
Again, thank you for all your work - we could not possible begin to convert our library site to Drupal without this automated help ...
Comment #4
dman commentedClearing the old 6.x issues from the issue queue for a cleanup.