NodeOne

More videos: 
Vimeo
NoneOne.se/en
Twitter: 
nodeone_dk

Publisher tutorials

Learn the Rules framework, part 29 – creating simple back links...
total favorited
2
total views
0
by NodeOne
1 year 30 weeks 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:

Learn the Rules framework, part 28 – deleting orphan tags (...
total favorited
2
total views
0
by NodeOne
1 year 31 weeks 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

Learn the Rules framework, part 27 – extra path aliases (intro)
total favorited
2
total views
0
by NodeOne
1 year 31 weeks 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:

Learn the Rules framework, part 26 – Rules Bonus Pack: Using...
total favorited
2
total views
0
by NodeOne
1 year 31 weeks 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.)

Learn the Rules framework, part 25 – Rules Bonus Pack: Views and...
total favorited
3
total views
0
by NodeOne
1 year 31 weeks 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.

Learn the Rules framework, part 24 – More Rules Link
total favorited
2
total views
0
by NodeOne
1 year 31 weeks ago | 11:06

This screencast shows some more settings in the Rules Link module:

-How to use the visibility conditions in Rules Link.
-That the entity the link is attached to is always available as a parameter.
-That you can add more variables to the Rules Link by passing them in the URL – and that you need to set up the parameters settings to tell the link how to interpret the data.
-That each link is available as a field in Views.
-That you can add parameters to links displayed in Views.
-That there is a bug preventing links for non-node entities to be displayed in Views.

Learn the Rules framework, part 23 – Rules Link
total favorited
2
total views
0
by NodeOne
1 year 31 weeks ago | 12:50

This screencast shows the Rules Link module, and some basics in how to use it.

It covers:
-That Rules Link adds links to entities (and that you set up each link separately).
-That these links triggers rule sets.
-That the links may be displayed as links on (for example) comments and nodes.
-That Rules Link is useful when you previously used Flag, but didn’t really need the 1/0 data that Flag provides (but rather just the Rules trigger effect).
-That access to each configured link can be controlled using the standard permission system.

Learn the Rules framework, part 9 – Notify of comment replies
total favorited
2
total views
0
by NodeOne
1 year 32 weeks ago | 13:38

This screencast shows how to set up Rules to allow comment writers to be notified when replies are posted to their comments.

It covers:
-Adding a checkbox to the comment form, turning on or off reply notifications
-Sending e-mails to the comment author when new comments are posted
-Not sending e-mails when replying to own comments
-Some words about checking “entity has field” on the correct entity

Learn Relation part 11 – Relation selector
total favorited
2
total views
0
by NodeOne
1 year 32 weeks ago | 13:47

This screencast shows the Relation select module, allowing the following:

-A new field, pretty similar to the Relation dummy field
-A new widget for creating relations from the field above, which is much more slick than the Relation dummy field
-Integration with Views, to allow using Views to select which entities to relate to
-The possibility to edit relation end points [sic!] using the widget above
-An administrative list of all relations on the site

Note that Relation select depends on Subform and EntityFieldQuery Views Backend.

Learn Relation part 10 – The Relation Add block
total favorited
4
total views
0
by NodeOne
1 year 32 weeks ago | 06:40

This screencast shows the new nice Relation Add block module in the Relation project. It allows you to add new relations in a pretty slick user interface, placed in a block and available when viewing entity pages. Two cool features are:

-You can not only create relations, but also populate any fields attached to the relation type. Sweet!
-There is an autocomplete function that allows you to list end points of any entity type.

The block assumes that the first end point always should be the currently viewed entity.