DaGardner supports this item


This author's response time can be up to 2 business days.

Popular questions for this item

Where do I have to store the SAFE.php (where the class is stored) file?

This totally depends on you! You have to make sure, that the include path (require_once ‘path/to/the/file/SAFE.php’) is correct. We recommend to have only ONE class-file stored on your server in order to make updates easier. This means that you may have to modify the include path if your php-site is not in the same directory as the class file. If you want to be super fancy you can also set an include path by having this line in every file:
ini_set('include_path', '/main/root');

If you now put the login.php file into /main/root/login.php you only have to include ‘login.php’ wherever the current file is stored; fancy, isn’ t?!

In version 4 you removed backward compatibility to previous versions. How can I now switch to version 4?

This depends on the mode you used. If you are using a non-database protection the upgrade is as easy as pie. Just redo everything. This is just one line to change. Take a look at the documentation (password is ‘demo’) on how the syntax has been changed.
If you have used the database everything is getting complicated. Since the password hashing has been changed you need to extend SAFE and overwrite the SAFE::generatePassword and SAFE::verifyPassword methods and inject the old password hashing method.

But I advice you to just drop your existing database and start from scratch if you want to use version 4. Otherwise stick with version 3.3.

Contact the author

This author provides limited support for this item through this item's comments.

Item support includes:

  • Availability of the author to answer questions
  • Answering technical questions about item’s features
  • Assistance with reported bugs and issues
  • Help with included 3rd party assets

However, item support does not include:

  • Customization services
  • Installation services

View the item support policy