salih24by7

@miloss84 We are also facing the same issue. We have a react app embedded on our page, and the urls from that app is showing as – Invalid selector: ‘#/profile/657358fcc5160c002b401748’ and this message is running continuously. In the app we have urls like this -https://mysite.com/subpage/#/profile/6515ee7b1a46c30056c0b7e7

Oh, if the content is coming through the_content() then only it will get restricted. If the template has custom coding and not using the_content then, is there is any workaround or actions or filters that we can use so we still get the content restriction feature!!

@artneo Glad to here that ??

@imani3011 Have you got any solution for this?

for a quick solution – you can add “token/validate” to your request path or in a query string argument, and that will cause jwt bypass the token verification. For eg: https://example.com/wp-json/v1/callback?path=token/validate

The above solution will work, but I dont know this is a proper way or not? I dont see any filters to do this in the codebase too.

In the Plugin Changelog – Version 1.3.0 they are talking about this: Allow for Basic Auth, by not attempting to validate Authentication Headers if a valid user has already been determined (see: https://github.com/Tmeister/wp-api-jwt-auth/issues/241)

I dont know if they are referring to the same issue, if it is, that is not working. I can see there is no reply for almost all support questions here, so not expecting much.