Drupal Projects

Drupal as a Model-View-Controller Framework

Our ultra small team of two have just completed switching our university from using Websphere to using Drupal to host the intranet portal. This was a huge project, but using agile methods and the nimbleness of Drupal we were able to accomplish this with just two developers and half-time from a systems administrator. There will shortly be a full write-up and presentation available here.

Drupal Module: Save to FTP 

The Save to FTP module allows for saving a node as a .html file via FTP. It was created for SF State University. The purpose of the module is to allow Drupal to be used as a content management system, but to have the actual content exported as static .html pages to an FTP/web server. 

The Save to FTP module allows for saving a content node as a .html file on an FTP Server. The latest 6.x-2.x release automatically adds all of the necessary Drupal css, js, and images as well. Please see below for more information on the options.
After a node has been saved, and a path is given, if the user has been given the "Save to FTP" permission a form is added on the node edit page which is activated by selecting the "Publish to FTP" button.
6.x-1.x releases
An administrative setting form is added which allows for editing the HTML wrapper of the node on the publish .html page.
6.x-2.x releases
The module automatically handles all html, css, and js. Important: This release requires PHP 5 >= 5.1.2
 
Now, this module presents the user with 3 options for publishing to FTP.
  1. By default, the 'Everything' checkbox is selected. When this checkbox is seleced, all Drupal core and contributed CSS, JavaScript, and images will be uploaded to the FTP server. A regular expression replace will be run on the HTML to point to these new files unless the next checkbox is selected.
  2. The Links checkbox will change the CSS, Javascript, and image links to point back to the full URL of your Drupal server. So, if these files are accessible to the public  (which by default they usually are if you set your Drupal files directly up correctly), then the files will be accessed from where they currently reside in your Drupal server. This saves you the load and time from having to move all the files to the new server. 
  3. The Anonymous check box makes it so that the page you return will appear as how it would appear to an anonymous user of your site. This is good to check if you are an admin and have stuff like Admin_menu and Drupal for Firebug running which add to your node's HTML stuff that you probably don't want to show on the web server you are sending the file to. 
5.x-2.x releases
5.x releases will continue to be available, and I will fix bug requests filed in the issue queue. However, no new feature requests will be done unless they are paid work.
This project was tested to run a WAMP and LAMP stack in production use, however memory and time limits may prevent you from being able to use all of its features.

All releases

Dependencies: Drupal's core 'path' module must be turned on.
Optional: QueryPath provides some minor cleanups
Issues, feature requests, and other questions should be added to the Issues queue

Subscribe to the issue queue for this module: 

Enter your email address:

Delivered by FeedBurner