NodeOne

[ni]
Twitter: 
nodeone_dk

Publisher tutorials

1
total favorited
5
total views
0
by NodeOne
23 weeks 2 days ago | 13:38

This screencast shows how to use the aggregation setting in Views in combination with relationships. The secret is that all the settings works just as normal with aggregation - but you should also know that it seems that the aggregation doesn't apply to the relationship handler (though it looks like that when you're setting it up for the first time).

That's it!

1
total favorited
4
total views
0
by NodeOne
23 weeks 2 days ago | 15:06

This screencast shows how to use the "aggregation" setting, lurking in the advanced options in Views. The aggregation setting makes Views return not one row per item in the database, but one row per aggregation group. Perhaps more importantly, it also makes it possible to count the number of items baked into each row, or sum them up, or calculate their average, or count the number of unique items, or…

To use aggregation in a sensible way:

Turn on the aggregation setting (duh!)

0
total favorited
1
total views
0
by NodeOne
29 weeks 2 days ago | 04:54

User story:
As site owner I would like content to be passed through two separate workflows, being approved both from a text/content and a legal perspective. Only when both aspects are approved, the content should be published. This is important since it helps the company stay out of trouble.

Required preparations:
A content type with two “workflow fields” (text lists) – see attached feature
Recommended module: Rules Link

Downloads:
The content type used in this exercise

0
total favorited
1
total views
0
by NodeOne
29 weeks 2 days ago | 02:48

User story:
As site editor I would like to be able to schedule content to be promoted to front page. I would also be like to set an end time for front page promotion. Naturally, I would also like to see what is scheduled for front page promotion. This is important since it helps me keeping our most visited page updated even when noone is manually updating the site.

Note: There is an important correction in the comments to this exercise. Bonus if you can spot the mistake made in the suggested solution!

Required preparations:
A content type with a date field (see attached feature)

0
total favorited
2
total views
0
by NodeOne
29 weeks 2 days ago | 02:01

User story:
As site editor managing content with multiple “see also” links, I would like each target content to link back to the content I’m updating. The back links should be added without changing the existing links. This is important since it helps visitors find related content, and it lowers the need for manual work from my part.

Required preparations:
A content type with an entity reference field to other content (see attached feature)
Required modules: Entity reference

Downloads:

0
total favorited
1
total views
0
by NodeOne
29 weeks 2 days ago | 03:24

User story:
As site editor managing content with “see also” links, I would like the target content to link back to the content I’m updating – if it was not already linked to something else. This is important since it helps visitors find related content, and it decreases the need for manual work from my part.

Required preparations:
A content type with an entity reference field to other content (see attached feature)
Required modules: Entity reference

Downloads:

0
total favorited
1
total views
0
by NodeOne
30 weeks 3 hours ago | 02:00

User story:
As site editor deleting an article, I would like to have all tags used by this article only deleted as well. This is important since it reduces the number of orphan tags on the site, that may confuse both human visitors and search robots.

Required preparations:
The suggested solution requires Rules Bonus Pack and Views.

Downloads:
Feature with the completed setup

0
total favorited
1
total views
0
by NodeOne
30 weeks 3 hours ago | 02:26

User story:
As site member I would like to have a nice URL on my content list, saying “users/MY_NAME/content”, rather than “user/MY_USER_ID/content”. This is important since it makes it easier to remember the path, and also easier for search engines to understand the page content.

Required preparations:
A view available as a tab on each user page, listing content created by that user. (See attached feature for this setup.)
Required/recommended modules: Pathauto, Token, Rules Bonus Pack

Downloads:

0
total favorited
1
total views
0
by NodeOne
30 weeks 6 days ago | 16:09

This screencast shows how you can use Rules to alter the presentation of your Drupal site, such as:

-Enabling, disabling and moving blocks around
-Setting HTML title element and also on-page titles
-Setting body classes
-Setting the active menu item (using Menu Position)
-Some bigger questions about using Rules for altering presentation is also discussed:

-Using Rules for presentation altering is relatively heavy. (It consumes about 2.5 MB more PHP memory than Context, and has about the same loading times – judging from a first, rough comparison.)

0
total favorited
2
total views
0
by NodeOne
30 weeks 6 days ago | 14:59

This screencast shows some functionality included in Rules Bonus Pack, as an example of how to make Rules integrate with other modules on your site. In particular it shows some Views and CTools/Page manager integration.

-Condition: Check the number of results from a view.
-Action: Load the sum of a Views column as a number. (Currently only D6!)
-Action: Load the first result in a view into Rules.
-Action: Clone a full node object.
-Action: Convert a number into a date
-Event: Trigger a rule when a custom page is rendered.