Views Mail

Notes on setting up and using Views Mail 6.x.

Installation, Configuration and Sending Mailing

Simplenews is a requirement for installation.  Basically, you need to create a Newsletter series specifically for Views Mail, then create the newsletters you want to be able to send in Views Mail mailings under that series.

1. Install simplenews and views_mail.  Install mimemail if you want your newsletters sent in HTML format.

Sorting fix for cyrillic (Ukrainian BTW)

Bottom text in Ukrainian - fixing sorting trouble with "і" "ї" "є" letters

При сортуванні матеріалів за допомогою модуля views було замічено
помилку. Матеріали з українською буквою "і" поміщаються вище ніж
матеріали з буквами "а", "б",... і т.д.

Вирішення цієї проблеми полягає в заміні порівняння кодування з
utf8_general_ci на utf8_unicode_ci.

В моєму випадку сортування проводив по загаловках матеріалів. Виправлення:

utf8 COLLATE utf8_unicode_ci NOT NULL;

Оскільки сортування прводяться не тільки по цих полях, тому варто
змінити це у всій базі.

snippet fix by Brun

User friendly paths

Publications do not have a URL setting. You have to define a URL alias. epublish/1 becomes d-theme_da_newsletter. You can hand out as a link people can use to see your newsletters. Perhaps publication could be changed to a node type so that URL aliases will be standard.

The breadcrumb incorrectly shows you at Home » D-theme Da Newsletter » Volume 9. The only thing I can think of is that when you set an edition as current, you are sent to the current edition. If I turn off current edition, the breadcrumb does not change. There are issues posted for breadcrumbs.

Editions have URL aliases. You can add a URL path settings when creating or editing an edition. The alias was not used in my one test.

I have not tested sections and topics. Please add your experience.

Section and topic content is added as normal content nodes. Those nodes can have their own URL. When referred to in an edition, there should be a named anchor for each session and topic. Using the example of a section New themes in the example newsletter d-theme_da_newsletter and december_2009, we should be able to refer to:

D6 Multi-Site Prior to D6.24 - Add a patch to synchronize file paths between dev and prod/live sites

The patch this page references has been closed and is now included in Drupal 6.24+.

If you have built your Drupal site on a development machine using multi-site configuration, you've discovered that there's a headache that will occur once you've ported your site to its live box. If you are about to do this, then you'll soon see the problem.

The problem lays within the site/files directory. Once you've uploaded your development site to its live server, you'll discover that you have to go into your tables and change the paths for images and other files. On your development box, you named, just for the sake of example, your site: drupal/sites/ And in both of these directories, you've added a files directory.

To the world, that site will be: and its file structure is drupal/sites/ Once you went live, you'll see that the paths to your images, pdf and other files looks something like this:

On one hand, you gulp at the length of that url. Next, you sigh because you realize that you have to change the path -- in the database.

Drupal 7 has a fix for this -- not the length (that's another story) but for the path problem.


Download E-publish from You will also need You can now assign nodes to publications with editions and sections within editions and topics within sections.

Disable the permissions interface using Secure Permissions

Secure Permissions disables the user interface for creating and assigning roles and permissions.

Secure Permissions is an advanced security module for Drupal 7. It disables the Roles and Permissions editing screens and lets all user roles and permissions be handled through code. This adds an extra layer of security, as the site's permission can no longer be misconfigured accidentally.

This module was inspired the security paradigm of the Plone platform. See, in particular, 'Problem A2: Broken Access Control' in the Plone documentation.

1. Use case

This module is designed for cases where you want control of Roles and
Permissions only in a development environment. When fully enabled, this module
will make it so that the live site cannot have its permissions modified, except
through code.

It may be sufficient for most users to simply enable this module on the live
site, and to disable it when it is no longer needed.

2. Installation

Before installing this module you should configure the site Roles and
Permissions as you see fit. After installing and configuring this module,


Subscribe with RSS Subscribe to RSS - Site administrators