Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
Jennifer Beadles Posted January 31, 2023 Posted January 31, 2023 Hello, I am having an issue with the API. I generated the API key and was testing it. After a while I noticed that I could no longer see the API keys. Any ideas on what caused it? Thank you
Daniel F Posted January 31, 2023 Posted January 31, 2023 Has anything changed on your server? Is the htaccess file still present in the api directory? faraz111 1
Jennifer Beadles Posted January 31, 2023 Author Posted January 31, 2023 Not sure what happened. The file is not there and when I uploaded it nothing changed. Also, my members can no longer login to the community. They keep getting redirected to the login page. Not sure if both issues are related.
Jennifer Beadles Posted January 31, 2023 Author Posted January 31, 2023 11 minutes ago, Daniel F said: Has anything changed on your server? Is the htaccess file still present in the api directory? The only thing I did today was to create and test the API key.
Jim M Posted January 31, 2023 Posted January 31, 2023 Did you apply the .htaccess for the API directory to your root directory by mistake? Sounds like this is happening if it is impacting other areas of the site. The .htaccess in ACP -> System -> Search Engine Optimization -> Rewrite URLs goes in the installation root of our software. The .htaccess in ACP -> System -> API, goes in the api directory of our software.
Jennifer Beadles Posted January 31, 2023 Author Posted January 31, 2023 1 minute ago, Jim M said: Did you apply the .htaccess for the API directory to your root directory by mistake? Sounds like this is happening if it is impacting other areas of the site. The .htaccess in ACP -> System -> Search Engine Optimization -> Rewrite URLs goes in the installation root of our software. The .htaccess in ACP -> System -> API, goes in the api directory of our software. No, everything was working fine, and then I started getting that screen out of the blue. I put the .htaccess file in the correct directory but nothing changed.
Jim M Posted January 31, 2023 Posted January 31, 2023 It looks like you're using WordPress at the root of your domain. Have you altered the .htaccess configured there recently? This can impact subfolders down the chain, which may also be your issue. I would suggest replacing the .htaccess as recommended in my previous post to ensure you have the correct ones in place and then you may wish to temporarily disable your WordPress .htaccess to see if that impacts anything.
Jennifer Beadles Posted January 31, 2023 Author Posted January 31, 2023 2 hours ago, Jim M said: It looks like you're using WordPress at the root of your domain. Have you altered the .htaccess configured there recently? This can impact subfolders down the chain, which may also be your issue. I would suggest replacing the .htaccess as recommended in my previous post to ensure you have the correct ones in place and then you may wish to temporarily disable your WordPress .htaccess to see if that impacts anything. I restored yesterday's backup but nothing changed. I still have the issue.
Jim M Posted January 31, 2023 Posted January 31, 2023 We would need to look further into this for you, however the access details on file appear to be incorrect or missing. Could you please update these details by visiting your client area, selecting the relevant purchase, then clicking "Review/Update Access Information" under the "Stored Access Information" section. We look forward to further assisting you. Jennifer Beadles 1
Jennifer Beadles Posted February 1, 2023 Author Posted February 1, 2023 9 hours ago, Jim M said: We would need to look further into this for you, however the access details on file appear to be incorrect or missing. Could you please update these details by visiting your client area, selecting the relevant purchase, then clicking "Review/Update Access Information" under the "Stored Access Information" section. We look forward to further assisting you. The issue has been resolved by itself. Thank you for your support.
Marc Posted February 1, 2023 Posted February 1, 2023 1 hour ago, Jennifer Beadles said: The issue has been resolved by itself. Thank you for your support. Please could you let us know what you found to be the cause? Others may find the same issue, and its always handy if people know when they search the community
Recommended Posts