Drupal 6 - Migrate from Nodewords 6.x-1.6 to 6.x-1.7

Hey,
I recently experienced problems from updating to a new version of nodewords and removing the nodewords_by_path module. Looks like the format in the DB for nodewords table has changed to the serialized format. The old meta information was still in the database, but it was not recognizable since the format was plain.

So I made a quick script to port the meta tags (abstract, copyright, keywords and description) from one format to another:

Create a page with PHP content and write the following: (it's recommended to backup the database first)

Working with contextual links

In Drupal 7, some modules supply contextual links that allow privileged users to quickly perform tasks that are related to regions of the page without navigating to the Admin Dashboard. For example, when you hover your mouse over a block or node, links are displayed that allow you to make changes to the block or node.

Uses

You can enable and disable contextual links and you can specify the user roles that have permission to view and use contextual links.

Enabling contextual links

To enable the Contextual links module:

  1. Navigate to the modules administration page (Administer > Modules).
  2. In the Core section of the Modules page, enable the Contextual Links module
  3. Click Save Configuration.

Configuring contextual links permissions

To set permissions for different user roles to access the contextual links:

  1. Navigate to the Permissions page (People > Permissions tab).
  2. For each role you can enable or disable the Use contextual links permission.
  3. Click Save Permissions.

Note that contextual links are not displayed if the user does not have permission to perform the specific action represented by the link.

Working with the overlay

The administrative overlay makes it easier to administer a Drupal site by displaying administrative pages as a layer over the current page (using JavaScript), rather than replacing the page in your browser window. Once an overlay is active, you can use the close link on the overlay to return to the page you were viewing before you clicked the link. In a "Standard" install, the Overlay module is enabled by default.

Uses

Example

Administrative interface without the overlay:

Amazon S3

This service is for Amazon S3 and CloudFront.

No third-party library is required. Be sure that the time on your server is accurate.

A container is an S3 bucket and an S3 account. Access key ID and Secret access key must be provided.
Access keys can be from the account credentials that have rights to all services or from credentials that have limited IAM policies attached. Read how to control access credentials.

The bucket may already exist, but if it is, it must be empty and owned by the account associated with the access key ID.

S3 buckets have a global namespace, so it is not possible to get a bucket that someone else is already using. For that reason, this service will never attempt to delete a bucket.

If the 'Serve with CloudFront' option is enabled, then a CloudFront distribution will be attached to the S3 bucket. This takes several minutes. Storage API will poll CloudFront during cron to determine when the distribution has been deployed. Until this occurs files will be served directly from S3.

If the 'Stream with CloudFront' option is enabled, then a CloudFront streaming distribution will be attached to the S3 bucket.

The geographical location of the bucket can also be selected. The options are US Standard (default), US-West (Northern California) and EU (Ireland).

Rackspace Cloud Files

CURRENTLY UNSUPPORTED
Rackspace has changed their API library and it will require a re-write of the code in Storage API module. You can help by contributing code to update to the latest Rackspace API if this capability is a requirement for you. If not you may consider more popular storage services such as Amazon S3, FTP, or Google Storage.

This service is for Rackspace Cloud Files.

Before Storage API can work with Rackspace you need to:

FTP

A container is a directory in an FTP account. Username and password need to be entered.

If the container is serving, a base URL must be specified. The base URL can use any protocol, e.g. HTTP / FTP.

Security depends on the FTP account / server.

Pages

Subscribe with RSS Subscribe to RSS - Site administrators