We are running into problems with import_html. We have tried to use the import_html on my
server but am running into problems with maxing out the execution time and memory limit in php settings.

Even though the server is set to 900 seconds and 32MB, the server is still maxing out. Also when it creates folders to put the files in, the folders are owned by user "apache" and set to 755; we have to manually delete and recreate them each time setting 777.

My developer believes that my control panel software, Plesk, is blocking access to some php modules. Have anyone ever had this experience? Any suggestions?

thanks

Comments

dman’s picture

dman commented
Status: Active » Closed (works as designed)

No clue about Plesk 'blocking' some modules, although if you don't have the full htmltidy extension, the command line version is (attempted to be) used.
this method can be blocked by some security set-ups (for good reason) and if you don't have htmltidy, AND you can'd run system calls, sorry, this module can't do its magic.

As for maxing out, that's altogether possible, but the interface allows you to select a dozen pages at a time to process. Unfortunately that's a lot of checkboxes if your site is big and largely horizontal. The tool is designed for reasonably proportional deep/wide sites. half a hundred pages in one subdirectory will kill it, yeah. The only solution is be selective using the UI.

Permissions is a usual problem when dealing with webserver uploads. It can probably be tweaked to 775 not 755, but that still won't help if your login isn't even in the same group as the web daemon. I don't really want to make it 777 by default. Sorry, that's an admin issue really.
As with the normal drupal /files handling procedure, you can pre-empt this problem by creating the target directory (eg /files/imported) manually before starting. Thus apache doesn't need to make (and own) it, and you can manipulate it yourself later.