raw note

For a how-to, see Using JavaScript in Behat tests (manual steps for installing, running).

For my stumbling around in the dark... read on.

On the unenviable proposition of having to add JavaScript support to Behat

behat mink extension cannot find fields

Are your builds failing because of this?

...it's probably because there is already content in the text area that is set to something to which the user no longer has access.

It seems really freaky when you have access to one text format, and it says:

"This field has been disabled because you do not have sufficient permissions to edit."

So you add another text format, and now you have access to the field... and the format it must have been saying you didn't have permissions for before, what???

Presented by Ian Mariano

[Need to ask NorthPoint Digital for the slide showing Drupal's API role in the whole mix:

UX: ASP.NET MVC, Angular.JS, HighCharts.JS
API/Admin: PHP/Drupal
Solr
MongoDB]

Mongo: All governments. Very flexible.

Extended MongoDB with JavaScript functions, including for forecasting data with best-fit curve projection. Also normalizing imported data, flattening data for SOLR search.

Field template are run before the row template.

This:
views-view-field--products--page-4--field-imagecrop-fid.tpl.php

is processed before this:
views-view-fields--products--page-4.tpl.php

The individual fields are run and then handed off to the row.

That is, the row template isn't run and given the chance to call and pass info into the field templates.

Had this suddenly up in the content where it shouldn't be, and nothing that should have loaded was there.
=0)document.write(unescape('%3C')+'!-'+'-') //-->

apparently caused by Omniture, since that exact code occurs here (but really it was a stupid quotation mark not closed error) --

"exanded" elements of a menu-item-rooted tree aren't expanded
http://drupal.org/node/398888

Working modified function (the patch has more):