[#23479] - Preparing 3.10 for 4.0 content versioning
- Fixed in Code Base
- 19 Dec 2019
- Medium
- Build: 3.10-dev
- # 23479
- Diff
- Hackwar:j3versioning
- Success continuous-integration/drone/pr the build was successful Details
- Success continuous-integration/travis-ci/pr The Travis CI build passed Details
- Success continuous-integration/appveyor/pr AppVeyor build succeeded Details
User tests: Successful: Unsuccessful:
This PR backports a few classes that would be necessary to implement versioning of content items in the same code for extensions in 3.x and 4.0. To support both 3.x-style and 4.0-style versioning, you'd have to implement the 3.x-style first. Good luck with that. To get 4.0-style working, simply let your table class implement the interface VersionableTableInterface (and the method that that defines) and let your item controller and model use the respective Versionable trait. In 3.x, these traits are empty, in 4.0 they contain all the logic necessary for versioning.
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Libraries |
| Labels |
Removed:
J4 Issue
|
||
| Status | Pending | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2019-12-19 12:48:14 |
| Closed_By | ⇒ | zero-24 |
This has not been merged into 4.0, so it seems not a good idea to merge this into 3.10
Done thanks.
Hey, yeah, so... We actually did merge in this feature shortly before the beta release, so we need to add this to 3.10 again...
Can you do a PR and tag me? I'm happy to review and merge as this PR here has been reverted.
The original PR to refactor the versioning feature is #23432.