covers versions 3.8.9 stable, 3.10.4 stable, 3.12.0 RC1, 3.13.0 development
The Search Page asset now allows you to select between Standard and Custom Grouping formats, allowing you to avoid the overhead of the latter. Previously, it used the Custom Grouping format and this could not be changed.
This change was made to the development version only.
Added to: 3.13.0 development
This feature allows you to search for relevant assets inside the Insert Link, Insert Image and Embed Movie WYSIWYG popups. For the most part, it works like the regular Quick Search in the backend interfaces. The main difference is that clicking on the asset's name will populate the main asset finder on the page with the relevant data, saving you having to find the asset in the asset map manually to use it.
In the case of Insert Image, the search will only find assets of Image type. In the case of Embed Movie, the search will only find assets of File type (with strict type check).
Added to: 3.13.0 development
This new metadata field type allows the storage of multiple arbitrary text values. It is filled on metadata screens using an Option List attribute, stored and indexed similar to a Selection metadata field, and is searched using a regular text box.
Added to: 3.13.0 development
The List Sorting drop-down available as a front-end keyword on listing- type assets now allows you to disable the No Sorting and Random options if they are not necessary.
Added to: 3.13.0 development, 3.12.0 stable
The Quick Search in the Administration and Simple Edit interfaces now have a "Search in Progress" message when it is sent, as confirmation that the search request was sent. Since searching the system for a keyword can take a while on large systems, this type of confirmation feedback is desirable in this situation. The new WYSIWYG popups in 3.13.0 also show this popup message.
Added to: 3.13.0 development
Assertion exceptions now no longer display the file and line number if the SQ_CONF_DEBUG setting does not request that file and line number be displayed (ie. it is not set to either 1 or 3).
To be added to : 3.13.0 development
Estimated start date: already in development
Estimated end date: 8th January 2007
This development will allows users who cannot trash an asset due to Safe Trash conditions to mark the asset to be trashed as soon as the conditions are met.
This is done by setting a new Cron Job that checks on each Cron Manager run that the Safe Trash conditions are met (or Safe Trash has been since turned off).
A new section of the Details screen, only shown if the asset has been marked for safe-trashing, informs users of whether the asset will be deleted on the next run, or which Safe Trash conditions are still to be met.
Two administrative features will also be added: a Safe Trash Report, which lists all assets that are currently marked for safe-trashing; and a Safe Trash Escalation Cron Job. This Cron Job will likely run on a daily basis, and message administrators of assets who are causing the Safe Trash conditions to be failed - of the asset itself if it is due to status, or of assets linked to the marked asset if it is due to there being TYPE_3 or NOTICE links made to the marked asset.
Additional queries: No additional queries are required for upgrades.
Additional comments: No additional upgrade steps are required.
| Bug ID | 3.10.x | 3.12.x | Dev | Description |
| 1958 | N | Y | Y | WYSIWYG Popup throws an error when trying to find a paginated asset |
| 1960 | Y | Y | N | WYSIWYG Visual Aid Plugin doesn't remove the visual aids |
| 1961 | Y | Y | Y | Query Builder screen layout is wrong for the DB Data Source |
| 1962 | Y | Y | Y | PHP Notice for the DB Data Source |
| 1964 | N | N | Y | Field styles should refer to search fields, not asset attributes |
| 1965 | N | N | Y | Permissions ignored on Paint Layout bodycopies |
Bug #1928 (WYSIWYG Special Character Encoding) was reported by aganatra on 9th December 2006 but was marked as Can Not Replicate after no feedback was received from the poster for almost 3 weeks after a suggestion had been made to test the effect of HTML Tidy on the reporter's system.
| Bug ID | Description |
| 1956 | Backend Search should have a "search in progress" message |
| 1957 | Custom form edit screen needed |
| 1959 | Error text for DNS failure on Links Report is confusing |
| 1963 | "Print this page" button for the Administration Interface |
| Bug ID | 3.10.x | 3.12.x | Dev | Description |
| 1955 | Y | Y | Y | Date metadata "allow blank" actually sets undesired values |
| 1960 | Y | Y | N | WYSIWYG Visual Aid Plugin doesn't remove the visual aids |
| 1961 | Y | Y | Y | Query Builder screen layout is wrong for the DB Data Source |
| 1962 | Y | Y | Y | PHP Notice for the DB Data Source |
There are currently no comments for this newsletter.