Back to Project
Getting Started
- How to install Client Portal
- Can I use it without WordPress?
- Setting up your first portal
- Using content pages
- Importing and Exporting Portals
- Icon Cheatsheet
Customisation
- Customise project status modules
- Remove the project status modules
- How to change the fonts in Client Portal?
- How to change the 'Client Portal Archive' text
- How to change the 'Client Portal Login' text
- Change Error Message on the Login Screen
- How to add, move, and delete phases
- Redirect to the homepage after logging out
- How to change the slug/permalink
- Edit the "Phase 1, 2, 3" etc. text
Troubleshooting
- Troubleshooting problems with Client Portal
- I’m not getting Client Portal updates
- Find and edit the Client Portal Login page
- I'm getting a 404 error message
- I'm getting an Nginx error message
- Trouble with logging into a portal
- Forgot password isn't working
Security
- Are my files safe in Client Portal?
- How do I hide Client Portal from search results?
- How do private file uploads work
Users & roles
Working with Client Portal
- Introducing Client Portal to your clients
- How clients can mark as complete
- Create a to-do list with Google Sheets
- Accepting file uploads in Client Portal
Integrations
What is the error message on my Client Portal pages talking about the “Nginx” stuff?
If you see the error message on top of your Client Portal pages in the WordPress admin area, that’s because your website is running on Nginx instead of Apache.
On Apache we use the “.htaccess” to help you lock down the private files folder so the files you upload cannot be access with their physical URLs, the ones you can see after you upload files to the the Media Library (see more details in the next section).
Because Nginx doesn’t support “.htaccess”, we cannot lock down the folder automatically for you, you MUST change your server setting to get it locked, or your files are still accessible with their physical URLs.
For most of you who don’t know how to update the Nginx config, please just relay the message (the config rule) to your hosting company or your IT person. And once they said it’s done, please double check if your private files can be accessed. You should just simply see the following screen if the folder is locked down correctly, when you try to access the physical URL.
(This is the Apache server error.)
(This is the Nginx server error.)