transmothra

Those are of course excellent ideas. Unfortunately, I have done all of the above without any difference. I switched to the 2023 default theme, and deactivated every single plugin, and it still behaves this way. The console (and i’m no expert) doesn’t really point me anywhere either. I’m at a loss. The only thing different about that page is it uses its own template, which of course wouldn’t have been the case using the latest default theme.

Sent details

Thanks! I was already getting prepared for that and have an admin account set up for it but I’m away at the moment. I’ll do that when I get home. Thanks again!!

Ok, so now i tried to make a post using Classic Editor, and Publicize options were there. But they showed up as disconnected. Clicked Twitter, authorized that or whatever that step was, then the page seemed stuck on a progress bar type modal thing. Whatever, went off and did something else for a minute. Came back and it was back to the New Post page. Twitter (and others) still not connected. Clicked on Tumblr, Twitter, and both say Sorry, you are not allowed to access this page.

Checked Gutenberg editor and no Publicize options showing up there at all (not sure what the expected behavior is). Went back to Classic editor and noticed Jetpack itself is back to being disconnected again and wanting me to set it up.

Hope that helps.

Thanks!

Can somebody tell me how to reliably make the header image on interior pages position itself like the front page, and stay fixed?

I just published a test post and still nothing. Any ideas, @macmanx or @supernovia? Thanks.

• This reply was modified 6 years ago by transmothra. Reason: added links

And now Jetpack is back to prompting me to set it up yet again.

@macmanx I was able to manually share a post with no problem. I then published a test post with no result. I also note that Tumblr isn’t seeing any new posts either.

I just set up Jetpack (twice in a row, after being prompted like i had only just activated it), and published a new post. Nothing new on Twitter.

Thank you @macmanx

Okay i’ve done that. I also created a rule:
(http.request.uri eq "/xmlrpc.php?for=jetpack" and ip.geoip.country eq "US")
…although i’m not sure if that was a Good Idea, or a Really Terrible Idea.

What should i be doing at this point?

@macmanx Sorry! It’s set at medium currently.

I do see the following triggering a block: /xmlrpc.php?for=jetpack …but i’m not sure what to actually do.

• This reply was modified 6 years ago by transmothra. Reason: added info about xml-rpc blockage

@macmanx I’m using full SSL on Cloudflare. Here is a full list of plugins i’m using:

• Advanced Custom Fields
• Akismet Anti-Spam
• Autoptimize
• Classic Editor
• Cloudflare
• Gutenberg
• Jetpack by WordPress.com
• Really Simple SSL
• Smush
• The SEO Framework
• UpdraftPlus – Backup/Restore
• WP-Optimize
• WP-Polls

Some of these are probably redundant. That’s because i’m borderline stupid, frankly, and am fully unsure of what i’m doing most of the time. Please do feel free to castigate me!

• This reply was modified 6 years ago by transmothra.

Thank you. I’ve added several requests there, although i’m (sadly pathetically) not knowledgeable enough to be able to actually contribute.

Okay @supernovia – just now i

1. cleared cookies/cache,
2. revoked WP from Twitter,
3. deactivated/deleted Jetpack
4. reinstalled/activated Jetpack
5. attempted to connect Twitter via Sharing settings
   Result: 500 status code for "POST /sites/52891030/publicize-connections/new"