There are a few tips for issues with logging in to the site. Once our support is open, please feel free to send us a ticket if you can't resolve issues.
| Table of Contents |
|---|
www & non-www Conflicts
When first installing your site, phpFox sets the domain of the current URL you are using during the installation. So if you install the site using www.site.com, you must use this as your primary domain. On your server if a user would visit site.com without the www and click on the Login popup, it won't work as your browser will see this as two completely different sites. To resolve this you need to make sure your web server sends all traffic to your primary domain, which in this example is using the www.
...
- Log into your Phpmyadmin.
- Find the table phpfox_user_group_setting
- Find the setting_id for can_stay_logged_in and change it to 1 for the admin user group or registered or whatever user groups can't log in (except for banned).
- The setting itself is also in phpfox_user_setting. Make sure you remember the setting_id for this and go in the phpfox_user_setting to change it also for those user groups.
- You will need to manually clear cache after this change. On your server, find the cache folder in PF.Base/file/cache and rename it to cachebu. Once you've renamed the cache folder, make a new cache folder and copy one of the index.html files into it (this just prevents nosy people from being able to see what's in your cache folder if they try to go to direct url). This folder should immediately start filling with files which are needed to run the site. Check your site and if everything is fine, delete the cachebu folder you renamed earlier.
No one can log in or they get redirected back to visitor page
This is normally an issue with crashed database or database tables. Your host can repair the database or you can see this guide. In most cases, it would be the phpfox_log_session or phpfox_user table that crashed. Note that crashing tables are a bad thing as it can cause damage if it is a common occurrence. You would want to check with your host and either upgrade the server or perhaps change the database to its own server.