NEW 7839 Support for documents as a file type in Files and images
NEW Add warning if viewed SiteTree object class is obsolete
… cases (fixes #7694)
…#7694) Original bug fix contributed by @kmayo-ss
This is caused by the input date values entered by the user are passed into query without converting in a correct format first.
BUG Session namespace sharing for CMS controllers (#7815)
Ideally we could do this without session, but pragmatically we still need it, because of the inflexible routing system, and because of performance considerations. Example: The tree is lazy loaded via a generic URL (admin/pages/treeview). While we could add ?ID=<currentpage> to make the view (more or less) stateless, it would trigger a full tree reload on every tree navigation action. Instead, we assume that all "reachable" nodes are already cached, and simply mark a different one as current. For this to work, we need shared session state between CMS controllers. See http://open.silverstripe.org/ticket/7815 for detail.
Related to #7740. The sort field gets stale if the current record is moved in the tree. Since the sort value can't be altered by interacting with the form, its not required as a hidden field, either.
Enable page sorting by Page name in list view (see #7601)
BUG: Installer templates
BUG: Fixing a issue with a undefined variable in getLink
It uses the correct live URLSegments for its parents by setting the global Versioned reading mode correctly, see 8a514d8 for detail.
Was fetching the record from live (and its direct URLSegment), but all of its parents from the current stage, which might be draft, leading to "mixed" draft/live nested URLs which might no longer be reachable in live mode.
… the list should not filter by folder ID
BUG Visual cue that URLSegment is updating
FIX Dont refer to framework module in config rules
Might be called sapphire instead, in which case routing rules will end up in the wrong place
VirtualPageTest was adding fields to Page via a decorator, but Page might not have any fields itself. This changed Page from not having a table to having a table, which then caused a problem on tearDown
By renaming fields to "StageLink" and "LiveLink", which means they don't get influenced by the model getters on Form->loadDataFrom(). Its also a more accurate name for the field value, since it contains a full (nested) URL rather than just a segment. Only used internally, so no API change.
Removed ineffective FieldGroup->subfieldParam setting, replaced with a specialised template, as well as a new "stacked" styling (both added to framework codebase)
…m/tractorcow/silverstripe-cms into tractorcow-3.0-translation-compatibility-fixes Conflicts: code/controllers/CMSMain.php