On this page you can find all versions of the php package
/. 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.
Auditor module installs a series of extension hooks into the Framework to monitor activity of authenticated users. Audit
trail is written into LOG_AUTH syslog facility through Monolog, and includes:
Login attempts (failed and successful)
Logouts
Page manipulations that may potentially affect the live site
Security-related changes such as Members being added to groups or permission changes.
Installation
Custom audit trail
You can add your own logs to the audit trail by accessing the AuditLogger, which is easiest done through the Injector:
AuditLogger is guaranteed to implement the PSR-3 LoggerInterface,
events can be logged at multiple levels, with arbitrary context:
Here is what will appear in the audit log on your dev machine (the exact format will depend on your operating system):
Troubleshooting
We are using a dynamically generated class for capturing database manipulation events. This class is cached, and in
some cases it may retain an old, incorrect version of the class. You can wipe it by removing your cache, specifically
the file called <ss-cache-dir>/<user>/.cache.CLC.SearchManipulateCapture_SilverStripeORMConnectMySQLDatabase.
Contributing
Submitting a pull-request gives the highest likelihood of getting a bug fixed or a feature added.
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 / contains the following files
Loading the files please wait ....
Loading please wait ...
Before you can download the PHP files, the dependencies should be resolved. This can take some minutes. Please be patient.