michael favia

Content Overlay

I traditionally find content overlays extremely useful for simple content operations and modal dialogs. For instance I patched and advocated an issue that would promote the delete operation on a node to a Menu Local Task like Edit and View currently are. This is in line with my views on implementing actions as decorators on the objects they perform their work on.

The proper use of a content overlay in this situation would be as a confirmation dialog for the delete operation.

I've recently begun a project to create a drupal install capable of handling multiple domain names with independent front ends and themes for each site and a shared code and database. This project will be tailored to the online marketing needs of the modern service professional and will allow each to post company information, profiles, portfolios, service lists, products for sale, as well as integrate into their twitter, facebook and craigslist accounts for social media appeal.

I worked with some kind folks in the UX team to promote the delete button on the node edit form to a local menu task (aka tab) like edit, view, track and revisions are. The general consensus is that this is a good thing but Dries would like to unify the interaction model across core if we push it through. I couldnt agree more.

I have had a seemingly constant battle with webdav for some reason over the years. We use it to hold Kate's graduate work and temporary work storage so it is constantly needed. TO its credit the problems ive had have never been its own making but rather a conflation of issues from installing so many services on top of eachother (Subversion, Drupal, Webdav). My most recent battle involved not being able to write to the webdav folder that existed as a subdirectory of a drupal site.