Content editing experience

Test from the server.

First Project to learn module and git.

This module would map webform submissions to a node. It was for Drupal 6 but never was developed far enough to be worth sharing with the community, project went in another direction.

Introduction

The lognode module is an attempt to log events occuring on a node.

The types of events logged are:
* create: logs an event when a node is created.
* update: logs an event when a node is updated.
* delete: logs an event when a node is deleted.
* new revision: logs an event when a new revision is created on a node.

How is this different from dblog?

Dblog is a logging system while with lognode, you can see all changes your
content has been through.

How is this different from revisions?

Their goals are different.

With revisions, you'll not know what has changed if the user do not click on
"Create new revision". Then, if I update a node, one will only know that the
node has been modified, but will not know WHAT has been modified. The only way
to know what what was changed is to click on "Create new revision".
But not all users are allowed to do it.

With lognode, each time a node is modified, you know what has changed. But
let's explain what we understand when we say "MODIFIED".

With drupal (dblog) , every time you save a node, the node is marked as
"updated", even if NOTHING has really changed within the node. But with lognode,
the node is saved in logs ONLY when we detect something has changed.

Then, you're able to know the real life of a node. What the node has been

Context Daylight provides a new condition for the Context module to use. The condition is whether or not the sun light is out for a particular location and timezone.

The purpose of this module is to provide a simple way for non-tech-saavy users to easily process content in commonly needed ways, including:

• Preprocessing Blocks
  • Adding first and last classes
  • Adding the block's source module and delta as classes
  • Adding simple 'configure,' 'edit block,' and 'edit menu' buttons on block hover
  • Integrating with common block modules, such as: Menu Block, Nice Menus, Menu Admin Per Menu, Skinr, etc.
• Preprocessing Pages
  • Adding classes to reflect front page, is_admin, content type, node id, etc.
  • Adding classes based on URL arguments
  • Adding classes for current user's role
  • Adding classes based on current user's browser client
  • Adding classes based on current page's taxonomy terms
  • Adding new template suggestions for content types like Panels (considering a separate ui for adding new suggestions)
• Preprocessing nodes
  • Adding classes based on node variables such as published, sticky, teaser, ownership
  • Adding classes based on current user's access to current node. E.g., user-node-update, user-node-delete, etc.
• Preprocessing Comments