Download the PHP package sitegeist/criticalmass without Composer

On this page you can find all versions of the php package sitegeist/criticalmass. 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 criticalmass

Sitegeist.CriticalMass

Tools for managing large amounts of nodes

Automatic creation of node-hierarchies

In Neos it is sometimes hard to handle high amounts of documents below a single parent node. In such cases it is hard for editors to find a specific document again. On top of that the performance and usability of the current navigate-component will suffer if too many nodes are on a single level.

To overcome this we suggest to use a hierarchical structure of collection-nodes to create a node structure that is appropriate for the current project and that helps editors to find documents. This solution has the additional benefit of representing that structure in the document-url aswell, that makes url-collisions much less likely.

Since the creation of such a node hierarchy is a repetitive task we provide this package to help automating that.

A common use case would be to automatically create NewsCollection Nodes for Year and Month and move any News Node into a matchig collection node.

Importing of nodes from CSV-Files

It is a repeated requirement to import data from table-structures into neos that usually requires the implementation of custom import controllers. This package allows to configure the import into nodes or even into node hierarchies.

NOTE: The import works together with the automatic node-hierarchy creation. So if you want to import into a structure you can configure both options.

Exporting of nodes to CSV-Files

For exporting nodes into a table-structure the package allow the configuration of the expression to query for nodes and expressions for each column of the imported table.

Authors & Sponsors

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

Usage

Commands

The import- and export-commands are expecting the field-names in the first line of the csv-file.

The import and export commands have an optional parameter --site-node that can be used to specify the site for the import. If this parameter is not given the default of the current Neos-setup is used.

Limitations

The following issues and side effects are known at the moment:

  1. Currently there is no way to notify the navigate component about a needed reload. So after a node was moved behind the scene, the navigate component will keep displaying the node on the current position until the next reload.
  2. The automatically created nodes are in the user workspace and still have to be published. If you want to avoid this use the option autoPublishPath.

Installation

Sitegeist.CriticalMass is available via packagist. Just add "sitegeist/criticalmass" : "~1.0" to the require-dev section of the composer.json or run composer require --dev sitegeist/criticalmass. We use semantic-versioning so every breaking change will increase the major-version number.

License

see LICENSE file

All versions of criticalmass with dependencies

PHP Build Version
Package Version
Requires neos/content-repository Version ^3.0 || ^4.0 || dev-master
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/criticalmass contains the following files

Loading the files please wait ...