Notably if you are making a Xortify Cloud Client for your framework, CMS or Portal like eCommerce. You will also have to building in the function on banning from the Protector Module.
The Standalone PHP Module is very basic it doesn't do this. Protector prevents SQL Injection attachs, DoS and other attacks and bans locally on the XOOPS website it is on. Xortify will then pick up the log and details of this module and ban those details on the cloud!
This is why you will have to build in parts of the Protector module as well when you are making a convergence or client for Xortify outside of XOOPS CMS.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Notably if you are making a Xortify Cloud Client for your framework, CMS or Portal like eCommerce. You will also have to building in the function on banning from the Protector Module.
The Standalone PHP Module is very basic it doesn't do this. Protector prevents SQL Injection attachs, DoS and other attacks and bans locally on the XOOPS website it is on. Xortify will then pick up the log and details of this module and ban those details on the cloud!
This is why you will have to build in parts of the Protector module as well when you are making a convergence or client for Xortify outside of XOOPS CMS.