|
Ryan Wilsey
|
October 6, 2016 at 9:43 am
My developer and I have been working on this issue for 3 days now, and we can not find a solution as to what may be causing it.
We are getting the message ” Error Occurred – The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible.
We have tried a couple of solutions:
1) set up a fresh install of WordPress on the same server with nothing but event espresso installed and it worked okay.
2) tried setting up the current website on an apache server with no such luck.
The website is as follows: https://lehighvalleyoutpost.com
Any help as to how we can solve this issue for this weekend’s non for profit event would be greatly appreciated.
Best Regards,
Ryan
|
|
Josh
|
October 6, 2016 at 9:57 am
That’s actually a conflict with the Yoast SEO plugin. For now, you can deactivate the Yoast SEO plugin, or add this to a functions file on your site:
add_action( 'init', 'my_remove_yoast_api', 9 );
function my_remove_yoast_api() {
remove_action( 'init', 'wpseo_init_rest_api' );
}
The above code will disable the Yoast SEO configuration wizard, so if you need to use the config wizard, you’ll remove that code.
We sent a ticket over to the app developers and they’re going to put a fix in the apps so that the Yoast SEO endpoint is ignored.
|
|
Ryan Wilsey
|
October 6, 2016 at 10:35 am
Josh,
Thank you. So I input that code into the functions.php file and now I am getting the following error. “Sorry, you are not allowed to list events. Missing permissions: ee_read_events,ee_readothers_events,ee_read_private_events .
Where would I update these permissions?
Best Regards,
Ryan
|
|
Josh
|
October 6, 2016 at 10:51 am
You shouldn’t need to update those permissions. What’s actually probably happening is the app is not authenticating. You’ll see that error
Authorization header isn’t getting passed to the app, and that’s usually a server configuration issue. It looks like your site is running nginx, so you can contact the server admin and ask them if they can add the following directive to the nginx configuration:
fastcgi_pass_header Authorization;
|
|
Ryan Wilsey
|
October 6, 2016 at 7:56 pm
Hi Josh,
We applied the changes and are unfortunately still receiving the error message.
Please see settings applied below:
listen 74.208.46.42:80 default_server;
server_name lehighvalleyoutpost.com;
server_name http://www.lehighvalleyoutpost.com;
server_name ipv4.lehighvalleyoutpost.com;
client_max_body_size 128m;
root “/var/www/vhosts/lehighvalleyoutpost.com/httpdocs”;
access_log “/var/www/vhosts/system/lehighvalleyoutpost.com/logs/proxy_access_log”;
error_log “/var/www/vhosts/system/lehighvalleyoutpost.com/logs/proxy_error_log”;
if ($host ~* ^www.lehighvalleyoutpost.com$) {
rewrite ^(.*)$ http://lehighvalleyoutpost.com$1 permanent;
}
location / {
proxy_pass http://74.208.46.42:7080;
proxy_pass_header Authorization;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;
}
|
|
Josh
|
October 7, 2016 at 7:50 am
Can the server admin look into why the Authorization headers are not passing? If this isn’t a server configuration issue, then you can try disabling other plugins.
|
