Side Channel

Iterating over list of object (array) is easy. Given the following template:-

and our data (in json):-

$this in the template refer to the object that we pass to JsEvalContext constructor.

Find out this only through reading the views.module code. In case of your views block display has a long name (> 32 chars)(the views name would be used as delta in block table), Views would hash it through md5. You can get the list of hashed names stored in the variable table as views_block_hashes. For example, mine:-

Array
(
    [ba843477361f490ca5c9e42548f0127d] => imagegallery_block_latest_images-block_1
)

The related code is in line 298 of views.module.

Using twill because until Drupal 7, there's no way you can install Drupal without opening the browser.

It's pretty crude at the moment but I guess a good start. Couple with some other tools I'm working on, installing Drupal can be fully automated. The next step is to convert this twill script into Python equivalent to be more flexible.

Update

Here some good and better explanation on this from Lin Clark's blog.

If you have custom field added to the node form (probably using hook_form_alter), you have to manually set the #weight properties to order the element the way you want on the node form. CCK user definitely would miss the 'drag and drop' UI to rearrange CCK fields.

Turn out it possible to somehow 'register' your custom fields so that it can be rearranged using the CCK UI. Cool. I first found this in an old issue queue. Further 'googling' lead me to this blog post which describe it further.

The key is the hook_content_extra_fields that you can implement to return an array of fields to be managed by CCK. Then function content_extra_field_weight($node_type, $fieldname) can be use to set the weight properties on hook_view or hook_nodeapi view op.

A bug poping out with some files failed to download, returning 404. Looking closer at the issue, turned out the files that failed contained ampersand "&" in the filename. PHP would translate the "&" in request path as a key in $_GET variable. So something like:-

would result in PHP $_GET as:-

urlencode'ing' the path is not enough because PHP would still translate that to an ampersand.

One thing everyone like in PHP, print statement just work. You don't need any fancy debugger.

DebuggingTechniques does explain it well on how to debug your WSGI apps. It also explain why print would not work, all for good reason. My favorite debugger is the web debugger from Werkzeug but as explained in the wiki, to make it work with mod_wsgi you must make sure subsequent request from the debugger end up in the same process that trigger the error. That mean:-

StartServers 1
ServerLimit 1

Just a note for future references. Tools to build Debian package for Python modules:-

• Stdeb - http://github.com/astraw/stdeb/tree/master

Stdeb is not in Ubuntu Hardy repo so we need to build a package for itself first.

"Segmentation fault"

Got this every time running PHP from the command line, especially when working with Drupal. It doesn't caused any harm (script working just fine) and that's why I never look into it. But accidentally found this post and the suggested fix did remove the "Segmentation fault" message from appearing.

• Commented pgsql in pgsql.ini
• Load pgsql extension in curl.ini, before the curl extension.

Wrote about internal CCK storage in my personal blog sometimes ago but looking through issues coming up recently in our issue tracker suggest that some of developers here still not sure where their CCK content are stored in the database. Briefly revising this topic to give some clue on where to look after when something goes wrong with our CCK related content.

Not aware of this until it was too late. All CCK field was stored in a flat container in table node_field. It's not unique per content type. That means you cannot have two fields with a same name although that field was used in different content type. From the UI, if you create field with a same name, it'll just append an arbitrary number such as _0, _1 to make it unique.