Very nice! Does this mean, however, that the traditional hook-based workflow will get replace by an event-driven one? Or will this change be more of a end-user transparent change in core and for modules defining hooks?
control what should happen when the entity is being viewed at its own page. You have the ability to
Deliver an access denied page.
Deliver a page not found page.
Issue a page redirect to any Drupal path.
Or simply display the entity (regular behavior).
This is configurable per bundle and per entity
We have build a prototype that explores how the Blocks & layout initiatives it's ideas could look in Drupal 8. This following the page & component library and concept model discussions.
Any module should be able to extend the system by providing additional thingies that can be chosen from, but at any given time, only the actually chosen one(s) should be invoked. For example, the Image module lets you create image styles by choosing from a set of image effects (scale, crop, rotate, desaturate, etc.). Any module can add more effects to the system. However, a particular image style is configured as a particular sequence of effects, and when it's time to generate an image of that style, the Image module wants to invoke just that particular sequence of effects.
the 'right way' to do this is to work with entity approach and avoid the ['und'][0] business but I never got it to work in views. i.e. code $node=menu_get_object(); $field = field_get_items('node', $node, 'field_event_artistref'); return field_view_value('node', $node, 'field_name', $field['target_id']); code. Here's a link I was following on the topic computerminds.co.uk/articles/…
Next time you find yourself thinking about using the words “click” or “here” on your links, remember the effects it’ll have on the user experience. The challenge is to make your links say “click here” without actually saying “click here”, and there are many ways to do this. It will take some thought and effort on your part, but in the end, your users will benefit with a better experience of your interface. You can take the easy way out and use “click here” on your links, or you can spend some time to find the right phrasing for your links that’ll click with your users. The choice is yours.
Machines don't have a universal noun - that's why they suck. Every programming language, database, or other kind of system has a different way of talking about nouns. That's why the URL is so important. It let's all of these systems tell each other about each other's nouns.
Wife: But when I'm looking at a web page, I don't think of it like that.
Ryan: Nobody does. Except Fielding and handful of other people. That's why machines still suck.
Wife: What about verbs and pronouns and adjectives?
Ryan: Funny you asked because that's another big aspect of REST. Well, verbs are anyway.
A /drupalgive page highlights the great work that your organization is doing for the Drupal project. Not only does your organization receive credit for the work you do, but we also nudge other organizations to give back as well. I expect that employees and potential hires from non-contributing organizations will start demanding to give back. This initiative gives those folks something to point to when advocating and educating inside their organization.