EES now handles both original and typo-corrected versions of error for PDF failing to be indexed (RM#3614).
Recommitted fix from rev:be2188b3 that moved title to an "extra" attribute when files were uploaded. (RM#2768)
Fix the logic of previous commit. Errors for corrupt PDF files not being indexed should be filtered out.
Fix issue with the Details screen overlay where a null thumbnail change would be sent even though the thumbnail is not editable (RM#3613).

If the user has effective write permission to links (which, eg. an admin should unless the asset is in workflow), the thumbnail would be deleted
in this situation (generally speaking this is when live with workflow applied, where EES restricts editing of the thumbnail but permission to do
so still exists underneath). In cases where there is no write permission (eg. in workflow) it may appear to be deleted but it would actually not
be because the link delete would be denied by Matrix.

Reason: the code was expecting the wrapper "#ees_thumbnailPicker" to be non-existent when thumbnail not editable - but it seems to stick around
although not with the asset picker inside it. So handling either way, either non-existent wrapper or wrapper not having an asset picker
(.ees_assetPicker) inside.
Fix syntax error.
Dev design file template for troubleshoting unminified individual file references
Remove unneeded folders.
Merge branch 'dev' of github.com:squizlabs/EES into dev
First stage of RM#3180: allowing bridges to be expanded into its shadow assets, so image varieties can be displayed - bringing it into line with the backend asset map.
They cannot be selected yet, because these assets are usually defined as "dependant" which is blocked from selection.
In lieu of finding a better way of showing an expandable bridge with an unknown number of parents, they are shown in the GUI as expandable with "?" children (would be shown as "N/A" in the backend).
Fixed an edge case that was causing internal EES redirects to fail in certain scenarios (fixes SM#3661).
In short, to replicate, an asset needs multiple lineages, needs to be accessed through a lineage not returned
by EasyEditAsset's web_path property, and that lineage contains more than one URL (or one URL with both protocols).
1. Backed out previous "? children" changes.
2. If bridge, call getChildCount on the applicable asset (batching those assets with the same parent) and use that as child count.
3. Allow setting of an itemRefiner in the asset finder's options, allowing items to be modified before display on an asset finder request level.
   eg. an image plugin that wants image varieties to be selected may unselect the "dependant" flag on image varieties, that currently stop it from being selected.
For now, disable expansion of shadow assets into further children (if they themselves have children). Bridges will still expand into first-level shadow assets.
This requires assetExists() to be properly implemented in bridges to make JSAPI calls work.
This change also requires URI-unescaping the child asset ID earlier in the asset finder.
Revert three commits relating to shadow assets (such as image varieties) in the asset map.
Not possible to make SM#3180 fully work without Matrix changes, so pushing these off the dev mainline and into a branch instead.
New version number display for the new (non-SVN-based) versioning.
Fixed bug in the wizard where, if more than one Recurring Calendar Event was created, only one would succeed.
Was caused by all frequency radio buttons having the same name, which means when one asset's recurrences were clicked, it would remove all selections from the others.

So:
- Renamed the radio buttons with their queue numbers so they were grouped properly.
- Added a fieldset around them with a class name.
- Used the fieldset as a target to find the appropriate recurrence selected in the wizard gather create data decorator.

Fixes SM#3689.
General cleanups:
1. Consistent unix line endings (LF) instead of DOS/Windows ones (CRLF).
2. Remove @version doc comment as Git is unable to handle keyword substitution.
On the linking screen, where a lineage is clicked that is not based on a site at the highest level in the Matrix hierarchy,
fix bug that would see the asset finder simply ignore the selected lineage and show the current URL lineage.
Fixes SM3672.
Remove effect of assetid cache in Asset Manager, and use the now-completed function to clear the current asset rather than manually nulling the asset manager private var.
This should fix SM#3702 as it means that re-getting the current asset should use the lookup rather than the assetid (which provides no lookup information for building a primary lineage).
Clearing the current asset occurs after an add or remove where the page is not redirected.
Merge branch 'dev' into stable