jayo

My Jetpack setting page is blank. I tried to fix it by uninstalling and reinstalling the plugin, but not after reinstalling, the page is blank and cannnot even connect Jetpack. Is there any issue, or something specfically to our website?

For some reason, when I enable Jetpack it works, but I disable it, it doesn’t.

Sorry guys. The code does work. I must have done something wrong the first time around.

Thanks for your help though.

Thanks Jon, that post gives me a headache. I usually find examples of what I need and mod it. I’ll look over it and figure it out.

MICHAEL, it just spits our error. Doesn’t work. Im using in INDEX.php

Same here.

Seems to have worked itself out.

It was happening for nearly a week, and now, it’s magically working again. Not sure why.

You have to manually insert slideshow into the Instant Article. I haven’t found a way that it will publish slideshow automatically.

https://developers.facebook.com/docs/instant-articles/reference/slideshow

@harryshawk

No, when I look there, the new articles have not shown up. That’s the issue. They’re not showing regularly any longer… since last week.

I get same error trying to activate any Jetpack modules.

Here’s what I see in the RESPONSE tab.

{“code”:”rest_no_route”,”message”:”No route was found matching the URL and request method”,”data”:{“status”:404}}

PLEASE HELP.

Okay great. Thanks for the update.

I actually cannot active any features from Jetpack. Not sure what the issue is. I tried to disable plugins, one by one, all together, etc. Nothing works.

All have the same message:

…failed to activate. Error: No route was found matching the URL and request method

• This reply was modified 8 years, 1 month ago by jayo.

Tech support at our hosting company tweaked server settings to force the URLs with trailing slash, which seemed to fix the problem for us 99% of the time.

Got the same issue here.

Aside from just saving draft, Im seeing that even if I put in title, it remains the Post ID sporadically. Cant figure it out.

Any update here?

Same question here.

I’ll wait for some feedback before upgrading.

The recent update seemed to fix this issue for us.