Releases: sitegeist/Sitegeist.Taxonomy
Releases · sitegeist/Sitegeist.Taxonomy
v1.4.0 Backend Module uses fluid instead of fusion
What's Changed
Also limited extensibility was added with this pr:
Additionally Packages can now add additional fields to the forms of taxonomies and vocabularies. To do this
the following steps are required.
- Extend the NodeTypes
Sitegeist.Taxonomy:Taxonomy
orSitegeist.Taxonomy:Vocabulary
in your package. - Add tha path to your additional
Root.fusion
to the Setting in pathSitegeist.Taxonomy.backendModule.additionalFusionIncludePathes
. - In the fusion code define each field as prototype that accepts the props
name
plustaxon
&defaultTaxon
resp.vocabulary
&defaultVocabulary
. - Register addtional prototypesNames by adding them to the Settings
Sitegeist.Taxonomy.backendModule.additionalVocabularyFieldPrototypes
orSitegeist.Taxonomy.backendModule.additionalTaxonomyFieldPrototypes
Full Changelog: v1.3.9...v1.4.0
v1.3.9 Reduce filesize by compressing javascript
What's Changed
Full Changelog: v1.3.8...v1.3.9
v1.3.8 Adjust fe build for taxonomy editor to support Neos 8.2
Sort vocabularies and taxonomies alphabetically
Merge pull request #54 from sitegeist/sorting Sort vocabularies and taxonomies alphabetically
Declare compatibility with Neos 8.x
v1.3.6 TASK: Declare compatibility with Neos 8.x
Bugfix: Hide delete button for autocreated vocabularies.
Thanks to @breadlesscode for providing the fix.
Neos 7.0 compatibility
Merge pull request #38 from sitegeist/task/adjustmentsForNeos7 TASK: Adjust for Neos 7
Bugfixes
Avoid template error when taxonomy node was not created yet
v1.3.2 BUGFIX: Render dimension menu only when context node is found
Fix Problems with Neos 5.x
ViewHelper arguments and access to FlashmessageContaienr were not yet compatible with Neos 5