-
Notifications
You must be signed in to change notification settings - Fork 19
Security and Caching
RG2 uses similar principles to RG1. It stores an encrypted password file (rg2userinfo.txt) in the kartat directory. User names and passwords must be at least five characters. If the file does not exist then it is created the first time that anyone tries to log in. The file can be deleted at any time if you have the necessary privileges. This would normally be via an FTP account. There is no ability to reset or retrieve passwords (other than by deleting the user file), and only one user can be created.
This is NOT the same login and password as an RG1 account.
If you are having problems then the first thing to do is log on to your site via FTP and delete the rg2userinfo.txt file. You will then be able to create a new user name and password.
You can improve the RG2 response time quite a lot (at least 0.5 seconds for big events!) by enabling caching of the JSON files. To do this create a directory called "cache" in the kartat directory. Every time RG2 gets a request it will look for a cached JSON file first, and will only recreate details from the .txt files if it cannot find one. The save functions delete the cached files every time something changes, so it should all work automatically. You can always delete any of the .json files or the whole cache directory at any time to force things to be done from first principles.