Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
I have used HTML export quite extensively in the past and it is not really that similar. Yes, HTML export makes .html files out of your site, but it is designed as a one off to get a folder of those .html files.
Save to FTP is designed to allow publishing a node directly to an FTP Server. Potentially, I could have offered to try to to add this functionality to the HTML export module, but that is not really the goal of that module.
Without further information I will mark this as closed.
I've reopened efforts on html export, any possibility it would make sense to merge efforts?
I think being able to export to html the entire site and automatically dump it onto an ftp server would be fantastic. Sounds like if you just doing single nodes this could be accomplished by html export being told to only publish 1 file. Also I was going to use querypath but instead opted for simplehtmldom which is easier to install for end-users via http://drupal.org/project/simplehtmldom.
If you'd like to keep them separate no problem, just figured I'd open up the dialogue if interested as I think the goal of this module could be plugged into html export if html export was given a more pluggable export_path / destination api (which I've at least positioned things for somewhat).
agreed. just wanted to see if you were open to it. If S3 is in your queue it might even make more sense to write a plugin that hooks into backup and migrate as that has FTP, S3 and local file writing as destinations.
Comments
Comment #1
coderintherye commentedI have used HTML export quite extensively in the past and it is not really that similar. Yes, HTML export makes .html files out of your site, but it is designed as a one off to get a folder of those .html files.
Save to FTP is designed to allow publishing a node directly to an FTP Server. Potentially, I could have offered to try to to add this functionality to the HTML export module, but that is not really the goal of that module.
Without further information I will mark this as closed.
Comment #2
coderintherye commentedComment #3
btopro commentedI've reopened efforts on html export, any possibility it would make sense to merge efforts?
I think being able to export to html the entire site and automatically dump it onto an ftp server would be fantastic. Sounds like if you just doing single nodes this could be accomplished by html export being told to only publish 1 file. Also I was going to use querypath but instead opted for simplehtmldom which is easier to install for end-users via http://drupal.org/project/simplehtmldom.
If you'd like to keep them separate no problem, just figured I'd open up the dialogue if interested as I think the goal of this module could be plugged into html export if html export was given a more pluggable export_path / destination api (which I've at least positioned things for somewhat).
Comment #4
coderintherye commentedI'm up for merging efforts, but I think we should get both of our projects cleaned up a bit first, then see where it best makes sense.
Comment #5
btopro commentedagreed. just wanted to see if you were open to it. If S3 is in your queue it might even make more sense to write a plugin that hooks into backup and migrate as that has FTP, S3 and local file writing as destinations.