-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Edit template references non-implemented version model #553
Comments
Yes, versioning is not fully implemented yet. We discussed this internally and came to the following conclusions:
|
baumannsven
added a commit
that referenced
this issue
Nov 11, 2020
…e versioning comes as feature in a later version. #553
baumannsven
added a commit
that referenced
this issue
Nov 11, 2020
This is a bugfix release. This release has: - Disable the versioning in the legacy data definition if is enable. The versioning comes as feature in a later version. #553 - Add missing select in DefaultDataProvider#getVersion() - Fix typo in active version retrieval - Fix versions fetch in DefaultDataProvider - Fix typo: 'tl_version.formTable' -> 'fromTable' - Add exception if palettes null in the palette collection #556 - Change operations to fix DBAL error see #549 - Add fallback for id property in tree picker - Fix the amount for filter all in the default limit element
baumannsven
added a commit
that referenced
this issue
Nov 11, 2020
This is a bugfix release. This release has: - Disable the versioning in the legacy data definition if is enable. The versioning comes as feature in a later version. #553 - Add missing select in DefaultDataProvider#getVersion() - Fix typo in active version retrieval - Fix versions fetch in DefaultDataProvider - Fix typo: 'tl_version.formTable' -> 'fromTable' - Add exception if palettes null in the palette collection #556 - Change operations to fix DBAL error see #549 - Add fallback for id property in tree picker - Fix the amount for filter all in the default limit element
baumannsven
added a commit
that referenced
this issue
Nov 11, 2020
This is a bugfix release. This release has: - Disable the versioning in the legacy data definition if is enable. The versioning comes as feature in a later version. #553 - Add missing select in DefaultDataProvider#getVersion() - Fix typo in active version retrieval - Fix versions fetch in DefaultDataProvider - Fix typo: 'tl_version.formTable' -> 'fromTable' - Add exception if palettes null in the palette collection #556 - Change operations to fix DBAL error see #549 - Add fallback for id property in tree picker - Fix the amount for filter all in the default limit element
=> We implement the missing parts of version handling (probably) in 2.3.0. |
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist before I submit this issue report
I confirm that:
My environment is:
Issue description
Editing a record based on a DCA that uses versioning causes this exception:
Steps to reproduce
Cause/Background
dcbe_general_edit.html5
includes the following code added in b909a20:$this->versions
is assumed to be an instance ofVersionModelInterface
, however, there is no implementation of that interface. What is actually passed to the template is aDefaultModel
.As this is my first time working with DC_General, this initially caused me to think that versioning support is so far incomplete. However, after applying the fixes provided in PR #552 and reverting the template code to what it was before b909a20, versioning seems to be available without any issue.
As I'm not particularly deep into the DC_General lore, I don't know whether this would be considered a bug or simply a result of versioning support being a work in progress.
The text was updated successfully, but these errors were encountered: