Richard Griffith
Richard Griffith
Rework notifications module to implement notifications using Xoops\Core\Service\Provider mechanism.
A standard for namespace use in modules needs to be defined. Some elements to consider: - namespace key in xoops_version.php - autoloader conventions, for example psr-4 autoloading for the declared...
I've given a lot of consideration to modules, and have a few ideas I want to present. If you have comments, alternatives, objections or other feedback, _please_ respond. Baring objections,...
Investigate inclusion of PHPIDS (See https://github.com/PHPIDS/PHPIDS) or a derivative as a suplement to current Protector module. See discussion in PR #93
Implement mailer using Xoops\Core\Service\Provider mechanism.
@bitcero, Eduardo Cortes, is currently working on an improved GUI layer for system administration.
Using a Namespace for classes is considered best practice. Some kernel classes have been converted to the Xoops\Core\Kernel namespace, but more remain.
There are several issues and limitations with the current Locale solution that need to be resolved.
A XoopsBaseConfig object was introduced with PR #241. (The commentary there covers the motivations and objectives.) This needs to be consistently implemented through out, replacing constructs such as `XOOPS_ROOT_PATH` with...
A upgrade to the installer is needed. Some areas of concern: - use predefined configuration file as the defaults - command line mode allowing automated installation - leaner UI, improved...