|
ucancervive
|
March 31, 2017 at 9:49 am
I am getting the same errors others have posted about on the forum, but still getting them after troubleshooting.
I have reached out to the hosting provider GoDaddy and we checked permissions and they should be able to access.
Not sure what I need to do to get this working properly on the mobile device (iPhone)
|
|
Josh
|
March 31, 2017 at 10:13 am
It’s probably the Authorization header isn’t getting passed. That’s a common problem with GoDaddy hosting and usually can be resolved by making an edit to the .htaccess file. Did you make the edit to the .htaccess file that’s outlined in the documentation under “For Apache servers with FCGI”?
https://eventespresso.com/wiki/ee4-event-apps/#troubleshooting
|
|
ucancervive
|
March 31, 2017 at 11:31 am
I did update and that stopped that error. But now I have a new one.
Error Occurred
The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible.
What do I do now? Thanks.
|
|
Josh
|
March 31, 2017 at 12:14 pm
You can try resetting the site’s rewrite rules. You go to the WordPress > Settings > Permalinks page from your WordPress dashboard and WordPress will automatically reset the rewrite rules when the page loads.
|
|
ucancervive
|
March 31, 2017 at 12:43 pm
Thanks. When I update the permalinks, that it updated my .htaccess file thus removing my changes I made.
How do I do this with keeping my changes on .htacess and also updating permalinks so I do not get a 404 page.
|
|
ucancervive
|
March 31, 2017 at 12:51 pm
Also, the update for the work around for the .htaccess file has HTTP should that be updated to HTTPS if my site is this?
|
|
Josh
|
March 31, 2017 at 1:46 pm
You could try this edit instead:
On the line immediately after the line that has
# BEGIN WordPress
add this:
# Begin Custom htaccess
SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1
# End Custom htaccess
I don’t have access to a Godaddy server to test this, but others have reported it works.
Also, the update for the work around for the .htaccess file has HTTP should that be updated to HTTPS if my site is this?
No.
|
|
ucancervive
|
March 31, 2017 at 2:23 pm
That did it!!!
Thank you!
|
|
Josh
|
March 31, 2017 at 2:44 pm
You’re welcome. It looks like you’ll need to move the custom htaccess so it’s before the line that has # BEGIN WordPress to avoid WP overwriting it later when the rewrite rules get refreshed. I’ll add this note to the documentation.
|
