Between thought and the real, there is no necessary or natural transition.
As a Solutions Architect for Channel Enablement, I spend a good deal of my time thinking about how to better integrate our delivery partners in the digital lifecycle of client sites deployed on the Acquia platform. The vast majority of our partners have their own “secret sauce” in the form of knowledge, best practice, and process spanning the gamut of the digital experience: search engine optimization, marketing campaign analytics, mobile and responsive design, content and UX strategy, and much more. This value-add is captured at the time of delivery, but remains even more important to continuously monitor and improve the site experience. Acquia Insight is a tool that partners can use today-- for the low price of free-- to deliver this value-add in real-time and feature their own services.
In our monthly training newsletter I’ll present you with news and helpful links to Drupal tutorials. I keep on finding great tutorials I want to share, and tell you about all that’s going on with the training program. So please do Sign up to our training newsletter for notifications about webinars, freebies and tutorials.
The monthly Drupal core bug fix release window is this Wednesday, and since it has been a while since the last one, I plan to release Drupal 7.28 on that date. However, in practice the release might not happen until Thursday, to give people a bit more time to test the latest code. Per our release policy, this will be a bug fix release only (no security fixes).
The final patches for 7.28 have been committed and the code is frozen (excluding documentation fixes and fixes for any regressions that may be found in the next couple days). So, now is a wonderful time to update your development/staging servers to the latest 7.x code and help us catch any regressions in advance.
Drupal 7.28 does not have any new features or API changes that are large enough to warrant an official change record, but there are numerous significant improvements, including:
- A change which should make the Update Manager module more reliable about reporting correct information about security updates to site administrators. This change has some possible performance implications though, so we're particularly interested in any testing and feedback on the drupal.org issue: "No available releases found" - fetching update information exceeds timeout.
If you do find any regressions, please report them in the issue queue. Thanks!
Upcoming release windows after this week include:
- Wednesday, May 21 (security release window)
- Wednesday, June 4 (bug fix release window)
A group of indie developers have launched a new game dev forum, where they hope to encourage fellow creators to get feedback, share their work, and take part in "pageants," all in a harassment-free environment. ...
Wow, what a couple of intense weeks for the Drupal 8 initiative for porting Search API. There were many improvements made lately and we hope to properly explain them all to you but for now I want to shout out a couple things. First and foremost I want to thank everyone in the community and especially Intracto because because of all of you we were able to reach our intended goal to help the funding of Search API for Drupal 8! We managed to raise 20% more than expected, which means we raised $2400!
As explained in the drupalfund.us project, this is intended to organize 2 sprints and to help drunkenmonkey to spend time during business hours on Search API without going bankrupt. This means that 60% of the raised money will go to Thomas (Approximately $1300) and the rest will be used (approx $1000-$900) for organizing 2 Sprints and help other community members to join these events.
The next sprint will be held at the Intracto offices during the 13th till the 15th of June. Intracto has been so kind to not only sponsor the project with money but also offer their location as a sprint location for 3 full days.Location
Intracto Group nv
13th till the 15th of June (Friday till Sunday)Accomodation
To be defined. We'll update this as soon as possible!Joining?
RESTful module is a new approach to providing a REST server in Drupal. Its concepts and philosophy appears in the module's README so I won't repeat it, but I'd like to go over some of the key points.<?php // Handler v1.0 $handler = restful_get_restful_handler('articles'); // GET method. $result = $handler->get(1); // Output: array( 'id' => 1, 'label' => 'example title', 'self' => 'https://example.com/node/1', ); // Handler v1.1 extends v1.0, and removes the "self" property from the // exposed properties. $handler = restful_get_restful_handler('articles', 1, 1); $result = $handler->get(1); // Output: array( 'id' => 1, 'label' => 'example title', ); ?>
In the past year almost every site we have is either completely decoupled from the server side where AngularJs serves the webapp, or AngularJS plays a smaller part, and we just embed web components inside a Drupal page to provide a slick UI.
Up until now our go to module was RestWs by the wonderful Klausi, which wraps around Entity API module's metadata wrapper. Basically, it hands over to the metadata wrapper the responsibility for the access and for the actual value it spits out.
It works fine, however the JSON it exposes has too much information.