Instructions in using EFFI’s Drupal CMS
Drupal is rather fond of using browser caches. For site visitors this is a big benefit, but for editors and authors this might seem a little frustrating. Refreshing the screen with the reload buttong (F5 or CTRL-R) is a good idea, when you feel that the stuff you are reading is not up-to-date.
Support requests and bug reports are best sent vial the `EFFICMS project page `_. You can also ask for help by `emailing the webmaster `_.
There are 4 user access levels (= roles) at the moment:
– Authenticated user = Can read and comment on drafts, but cannot create or edit anything
– Vieraskynä = Can write blog entries, but nothing else
– Editor = Full access to content
– Administrator = Full access to everything, including user management
A page/article (Node in Drupal jargon) is published by selecting “published”. To the current web pages it can be taken (with a delay of max 30 seconds) by checking “Promoted to front page”
When you create a node, selecting its type is important. The types are, in order of importance:
Most flexible (and complex) content type.
Features: summary field, published by default (not on front page), version control, attachment files
**NOTE:** Unlike other node types, the title of a page is *NOT* automatically appended
to the body, but instead it is assumed to be written in the body. (Like e.g. in **a press release**).
Even though the title is shown twice in *preview*, after publishing it behaves like this.
Quite self-descriptive. Short article
Features: summary field, published by default AND on the front page. Attachment files. No version control
**NOTE:** The author and the date is shown automatically after the title. Nodes in this category
are autoaliased as ‘blog/YYYY-MM-DD-
A picture can be published as is on its own page (rarely), or it can be attached to other nodes.
Not surprisingly, fit for publishing news.
Features: Like *a blog article*.
**NOTE:** The author and the date are *not* shown after the title. Nodes in this category are
autoaliased as ‘uutiset/YYMMDD-
E-mail form. Relatively complex to use. Seems to work fine.
Example page: `e-mail the webmaster `_,
Bug/Issue/Support request system.
Can be used to coordinate different projects, or as e.g. a TODO list.
Please let the webmaster know before creating a new project.
A bug report form, tied closely with the project type nodes.
Please don’t create these with the “create content”-page, but instead
by going to the correct project, and selecting “submit issue” (Or something like that).
Please remember to classify your writing carefully! The whole system is based on the assumption, that the content is properly classified. At the moment, there are 4 classes, or “Dictionaries” in Drupal jargon. For one reason or another, they are not localized, at least on the edit page 🙁
| Julkaisutyyppi (Type)
| Toiminta-alue (Field of activity)
| Erityistila (Special)
The first 2 are extremely important, because the aliases of the content (URLs, see below) are created automatically based on them. “Multimedia” is meant to indicate pages that contain pictures, videos, and so on. The Special category contains only one term at the moment. If it is set, authenticated users can comment the page.
NOTE: In creating index or compilation pages (Such as “tekijanoikeus/“ , “yksityisyys/“ and FAQs) you do *NOT* select any Type or Field. Otherwise they are shown as just one of the pages.
The internal identification of nodes in Drupal is based on numbers. For example, Ville’s piece ‘Tekijänoikeus kääntynyt kulttuuria vastaan’ internal URL is http://www.effi.org/node/9, but because it has a defined *alias*, users see it as http://www.effi.org/kirjoitukset/tekijanoikeus-kaantynyt-050213.html.
Janne has created a pretty good set of rules, with which the system can automatically generate sane URLs. Even the previous example was created automatically, based on the classification, title, and date.
Of course, you can define an alias by hand also. This is done by filling the “Path alias” field in the content edit page, or by editing the alias list by hand afterwards. This is something you must do when moving pages from the old EFFI site to Drupal. (Instructions left out, all current editors probably know Finnish 😉
If your page has PHP code, `ask the webmaster `_ to take care of it.