Avoid site file clutter by creating custom pages with a blank slate, useful for e.g. custom iframes, site validation XML files, etc. That said, this should be used as a last resort, it is strongly recommended to use customized solutions, e.g. Site Verify, instead.
My first git project on drupal.org.
Proof-of-concept module providing HTTP caching for authenticated users.
By default any response - currently only pages rendered through drupal_render_page() - may be cached locally by the user agent, except if explicitly set not to (e.g. certain paths, or if the page contains dynamic content that changes every request). Along each cacheable response an ETag HTTP header is passed containing identifiers of all displayed data (entities, etc).
The purpose of this module is to migrate fields created from the References module to the Entity Reference module. This is a continuation of the amazing work from #1308490: Migration from references module.
Mainly two things:
The DOM Window module includes a drush command that will download the jQuery plugin for you.
$ drush domwindow-plugin
Allows videos embedded using the video_embed_field module to be displayed in a DOM Window overlay.
Well, first it defines a new format for the video_embed_field fields called overlay. Then, using a pretty standard theme function, combines the preexisting display modes into one, thus producing a thumbnail that is linked to the embed code (inline hidden div) which will be displayed in an overlay window using the DOMWindow jquery plugin
With millions of form posts, the forum frontpage becomes a bit slow.
In this sandbox a cache table is used to cache the query results for the frontpage, clearing the cache-entry per forum-topic when there is a new/updated post.
- Alter Node views in order to use only COUNT.
- Create a subset of API for Data Charts, in order to standardize everything.
- Create a first integration with Google Chart tools.
