Coding standards
Security in ResourceSpace
Developer reference
Database
Action functions
Admin functions
Ajax functions
Annotation functions
API functions
Collections functions
Comment functions
Config functions
CSV export functions
Dash functions
Debug functions
Encryption functions
Facial recognition functions
File functions
General functions
Language functions
Log functions
Login functions
Message functions
Migration functions
Node functions
PDF functions
Plugin functions
Render functions
Reporting functions
Request functions
Research functions
Slideshow functions
Theme permission functions
User functions
Video functions
Database functions
Metadata functions
Resource functions
Search functions
Map functions
Job functions
Tab functions
Test functions

Managing code dependencies

From version 11 ResourceSpace is officially managing its PHP dependencies using Composer.

Regular development tasks

As part of your developement workflow, as good practices dictate, you should the assert the state of your code changes (e.g. run the automated tests, statically analyse the code, etc.).

To help with such tasks we've added a custom Composer command (dev:beforeCommit) which you can call independently or create your own alias for "svn commit" to ensure it's running it beforehand.

Applying downstream changes

Unfortunately sometimes we have to fix bugs in our dependency code. We should update the build:applyDownstreamChanges command to ensure we always patch vendor with our fix.

Releases

From an sysadmin user perspective nothing will change for you if you are checking out from our SVN /releases/ branches.

We have a custom Composer command (build:release) which will include everything needed in the release branch (e.g. the vendor directory).

System administrators

Sysadmins can use Composer to check that the PHP version they use in production has all the necessary modules installed by running:

composer check-platform-reqs --no-cache --no-dev