updated site and now projects are missing

[Toby]

Hi Armin

I updated my website - and when I revisited all my projects were missing on the front end.
The layout however is still visible in the backend.

all plugins are up to date.

can you help?

www.tobyneilan.com

[sinaschwarz]

Hey, I do have the same problem. It says:

Beschädigte Themes

Die folgenden Themes sind installiert, aber nicht vollständig.

Name Beschreibung
lay Es fehlt ein Stylesheet.

a stylesheet is missing.

Please help!

[sinaschwarz]

@sinaschwarz meanwhile i re-installed the theme. now it's visible in the backend but still not visible on the front end. i also installed the "seo all in one pack"-plugin … is it possible, that that's the problem?

[sinaschwarz]

@Toby Hey Toby, I visited your website and as far as i can see there are all projects visible. What did you do? Can you help me?

[Toby]

@sinaschwarz

Hi

Armin told me it was to do with my webhost.

The webhost needs to change a mod_security setting, to make URL's like "http://tobyneilan.com/wp-json/wp/v2/posts/625" reachable.

This is an email I sent to my hosts - tweak the urls to your site and see if they can help.

Hello

My problem is that a javascript ajax GET request returns a 403 error on any "/wp/v2/posts/<id>" WordPress Rest API endpoints.

My wordpress theme uses the wordpress rest api.

I fetch json from an api endpoint like this in Javascript:

jQuery.ajax({
url: frontendPassedData.wpapiroot+'wp/v2/posts/'+id,
method: 'GET',
…

I guess there is nothing wrong with the javascript code that is doing the GETrequest above, as the same code works well on hundreds of other websites using this wordpress theme.

Basically I'm sending a GET request to a URL, for example:
http://tobyneilan.com/wp-json/wp/v2/posts/625

This is one of the pages where the problem occurs:
http://tobyneilan.com/copious-colour/

The GET request always returns a 403.

I have read on wikipedia:
"Status code 403 responses are the result of the web server being configured to deny access to the requested resource by the client."

Do you think this might be a server configuration issue? Do you have an idea about how this problem could be solved?

Thanks

Toby

[arminunruh]

hey toby, yeah unfortunately this is a new issue that has popped up, i think with the new wordpress version. really not sure why this happens now because before it worked :/