Download the PHP package sitegeist/taxonomy without Composer

On this page you can find all versions of the php package sitegeist/taxonomy. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package taxonomy

Sitegeist.Taxonomy

Manage vocabularies and taxonomies in Neos as node in a separate subtree /taxonomies distinct from /sites

Authors & Sponsors

The development and the public releases of this package is generously sponsored by our employer http://www.sitegeist.de.

About

If taxonomies are defined as documents in the /sites subtree of the Neos ContentRepository, things tend to get complicated:

Sitegeist.Taxonomies store vocabularies and taxonomies as nodes outside of the /sites hierarchy in the content repository. This way, the meaning of the taxonomy relations can be expressed better, taxonomies can be used across multiple sites and the taxonomy documents can be defined without interfering with the taxonomy meaning.

It also provides a separate backend module for managing vocabularies and taxonomies.

Installation

Sitegeist.Taxonomy is available via packagist composer require sitegeist/taxonomy. We use semantic-versioning, so every breaking change will increase the major version number.

Storing vocabularies and taxonomies in the ContentRepository

Sitegeist.Taxonomy defines three basic node types:

If you have to enforce the existence of a specific vocabulary or taxonomy, you can use a derived node type:

And configure the taxonomy package to use this root node type instead of the default:

Referencing taxonomies

Since taxonomies are nodes, they are simply referenced via reference or references properties:

If you want to limit the selectable taxons to a vocabulary or even a taxonomy, then you can configure a more specific startingPoint:

Content-Dimensions

Vocabularies and Taxonomies will always be created in all base dimensions. This way, it is ensured that they can always be referenced. The title and description of a taxons and vocabularies can be translated as is required for the project.

CLI Commands

The taxonomy package includes some CLI commands for managing the taxonomies.

Privileges

Sitegeist.Taxonomy brings the following privilege targets to allow you to restrict read access, management and editing of taxonomies:

Reading and referencing taxonomies from other nodes is currently not limited.

Extensibility

Packages can add additional fields to the forms of taxonomies and vocabularies. To do this the following steps are required.

  1. Extend the NodeTypes Sitegeist.Taxonomy:Taxonomy or Sitegeist.Taxonomy:Vocabulary in your package.
  2. Add tha path to your additional Root.fusion to the Setting in path Sitegeist.Taxonomy.backendModule.additionalFusionIncludePathes.
  3. In the fusion code define each field as prototype that accepts the props name plus taxon & defaultTaxon resp. vocabulary & defaultVocabulary.
  4. Register addtional prototypesNames by adding them to the Settings Sitegeist.Taxonomy.backendModule.additionalVocabularyFieldPrototypes or Sitegeist.Taxonomy.backendModule.additionalTaxonomyFieldPrototypes

Contribution

We will gladly accept contributions. Please send us pull requests.

License

See LICENSE


All versions of taxonomy with dependencies

PHP Build Version
Package Version
Requires neos/neos Version ^7.1 || ^8.0 || dev-master
neos/neos-ui Version ^7.1 || ^8.0 || dev-master
neos/fusion-form Version >=2.1.0
neos/content-repository Version *
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package sitegeist/taxonomy contains the following files

Loading the files please wait ....