Download the PHP package sandstorm/contentcomments without Composer

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

Sandstorm.ContentComments

ARCHIVED -> today, please use https://github.com/networkteam/Networkteam.ContentComments instead - as this is further developed.

Created by Sandstorm Media in 2015.

This Package Adds Content Comments / Sticky Notes to TYPO3 Neos. You can comment on arbitrary nodes.

Supported Neos Versions:

Usage

Internal Working

Why did we choose this implementation?

There generally are multiple ways of storing comments:

As a first step, we wanted the exact same publishing behavior than with normal content, i.e. a content note should appear exactly in the workspace/content dimension where the specific content is located. Furthermore, we thought it would be very strange if the user created completely new content, leaves TODO notes for himself, but does not publish yet -- and still notes would already be visible to other people in their workspaces. I think that behavior does not really make sense -- that's why we handle the notes currently in the same manner as normal content, with all the same workspace and shine-through logic.

TODOs

This is currently beta quality; expect to find bugs.

License

GNU GPLv3 or later.

All versions of contentcomments with dependencies

PHP Build Version
Package Version
Requires typo3/neos Version >=1.2
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 sandstorm/contentcomments contains the following files

Loading the files please wait ....