PJAX or PushState AJAX is a small script that allows you to load HTML content without a full page reload. It's purely created for a better browsing experience. The source and a working example can be found at: https://github.com/defunkt/jquery-pjax The beauty is that it updates the browser location field - thus allowing you to navigate back and forth through your history while it's actually doing nothing more than AJAX requests. Which means fewer resources need to be (re)loaded in the browser.

oEmbed is a format for allowing embedded content off a URL on third party sites. This simple API allows a website to display embedded content from for example Youtube. So you can only use the url of a Youtube video and get the video player back, it's that simple.

No parsing of html is needed because you'll get the embedded code back from Youtube, so this should be OK, in many cases you only store the url in your db.

This post is my effort to guide you through the whole new abstraction layer for accessing the database server, which comes with the Drupal 7 core distribution. In this blog-post I’ll try to explain to you guys (girls) how this new layer works, without diving into all the details, in order to give you a clear view on this new system.

Situation:

I use Zend_Layout to create a global view template for my website and the view (.phtml) that corresponds to a controller/action will be loaded into the $this->layout->content variable automatically.

All good but what to do with a form in your global template?

Building the form (Zend_Form) into your view isn’t really a clean option and what about validation of the form? There is no controller/action from where the form was build and so there is no controller/action where to post the form to.