Posted by seanB on September 21, 2010 at 10:56am
6 followers
| Project: | HTML Export |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs work |
Issue Summary
For a client of ours I added some features to the HTML export module. Here is a list of things I added:
- Views support: All page views are added to the export
- Custom folder name setting (with the option to add a timestamp)
- Domain name setting (some sites have different lay-out based on domain). It's also possible to login as a certain user if used with the securesite module.
- Export extra URL's setting: URL's wich aren't nodes or views can be added here (sitemap for example)
- Find & Replace setting: You can define strings to replace in the HTML of the export files.
- Cron support: You can define an interval to run the export as a cron job.
The features are attached in a patch. Maybe the new features can be added to the next version of the module.
Regards,
Sean
| Attachment | Size |
|---|---|
| html_export_added_features.patch | 21.79 KB |
Comments
#1
I have a problem applying your patch.
Could you attach your html_export.module file?
Thank you
#2
I'm getting failed hunks too:
patching file html_export.module
Hunk #2 FAILED at 63.
Hunk #3 succeeded at 119 (offset -41 lines).
1 out of 3 hunks FAILED -- saving rejects to file html_export.module.rej
+++ html_export.module (working copy)@@ -258,4 +160,253 @@
+ set_time_limit(500000);
If you're having to set the time limit, maybe this would be best running as a batch operation?
Powered by Dreditor.
#3
hi i just tested the above patch and it works ( i mean it creates the views pages etc ) what's seem to be the problem?
p.s : i have included the above version without the corrections -+@ signs in order if someone else who wants can use this ;) .
#4
I'm accepting comaintainers for this project (as always). I will most likely get back to this module at some point in the future but it's pretty low priority for ELMS at the moment.
#5
ok totally accepted . i just posted something that could help the community perhaps :) . . . i would like to help but i dont know the .cvs system and to be honest i find it kind of 'difficult' to follow :)
#6
need to learn cvs in order to contribute unfortunately
#7
yeap. i know that. i'll be back when i'm ready ;)
#8
http://drupal.org/handbook/cvs/quickstart <-- this is a really good page which covers everything you need. Look at the recommendations for CVS clients too.
#9
moving to 2.x There is some early support for views based paths and the 2.x branch does support export of different paths. I won't mark this fixed though as I haven't done a lot of testing / implementation around exporting views. It is now at least possible
#10
Re html_export_added_features.patch cron support:
When the export is running as a cron job; does it re-export everything or only items that have changed since last run?
#11
This patch will need to be rerolled against the latest 2.x-dev branch as it's completely different. cron support would be great. My guess would be that there would be a total rebuild but again I'll accept patches that get this going in the right direction. I think a date would have to be stored as to when it was last run and then an option given. Also, changing blocks / theme settings / adding new modules that might add things to the output will not be reflected in this "what content has changed" concept so I'd recommend a full overwrite each time with the ability to override that via hooks.