assuming you looked at the Google info?

https://support.google.com/culturalinstitute/partners/answer/10968067?hl=en

https://blog.google/web-creators/embedding-web-stories-across-your-site/

I don’t work here

Might be your site is too new, or your FB page not enough followers, etc. — Facebook is a bit more twitchy lately due to campaign season (elections).

they would need to double the theme price to handle the support….much better yo use on of the established ad sales platforms out there

i think with most thems you specify a featured image, but then you can simply insert an image however you want

do you mean wordpress plugins, or some addon for tagdiv themes?

https://www.wpbeginner.com/beginners-guide/step-by-step-guide-to-install-a-wordpress-plugin-for-beginners/

i dont work here

they are seeing wrong time at site or server level…trick is tracking that dow, and i do not remember how we sorted looking that up…might have been php time setting…i think you can install a simple test.php file in your root to sniff all php settings. that would identify what timezone php is using.

you can try setting via htaccess aloso
https://www.a2hosting.com/kb/developer-corner/php/using-php-directives-in-custom-htaccess-files/setting-the-php-time-zone-in-an-htaccess-file/

Google has retired AMP, so good to move on and focus on mobile usability. we just retired it on all our news portals.

May not be related, but latest version of WordPress had some funky change to java/js/jquery. Try hard reloading your browser cache (e.g., in Chrome shift+F5), while on your post admin page (making post or editing one), as we had oddities like not being able to set a schedule time, and couple other things for ACF fields.
( I don’t work here, just loooooooong time user.)

Could be random bug in Google, because let’s face it, they really don’t give a bleep. I know we used to sometimes see an oddity with “scheduled” posts where we would create it at 11:30 and shedule for 7am and somehow Google could see it as 11:30 vs 7:00 which was annoying and turned out to be a Yoast foobar. Cleared up eventually. You can try stuff like resaving your permalinks from the WP settings page to clear transients. Also, look for patterns – is it just the one, or ALL of your posts way out of correct time? No easy answer. Been there, but awhile back.

Check your XML sitemap to see what time is noted, if applicable, also the meta data of the post for any timestamp; double check the time location setting in the main WP settings; finally, this used to bite us, “server time” may be totally different than “local time” and that might be what is actually be printed with all the post data. Check the ‘example’ output on the WP settings page, to see what time is shown for the time formatting, as if it does not match your actual local time, you may need to adjust that or offset it.
(I don’t work here; just looooong time user.)

If you just updated to WordPress 6.5, try doing hard cache clear in browser. We had jquery error when trying to set a shedule date, clicking on the date nothing would happen, so could not schedule anything. Took us a while to note something changed with jquery and java in latest WP.

a) in Chrome hit shift + F5 to reload admin page without cached JS files
b) do “save permalinks” in main WP settings to clear some transients

Not theme related as far as java weirdness we were getting. Might not apply to your issue.
(I don’t work here)

I would wait for WP 6.5.1 as we had some notable issues with other themes, woo commerce, and caching. On one site, we were unable to schedule posts – two uninstall/reinstall, and then tried simply hard clearing cache(s) including browser cache for the admin pages. That cleared it – was basically getting jquery errors with the post admin pages. Not this particular theme. No issues with the ‘sister’ theme, Newsmag, but it’s a bit lean. We are holding off on any more updates across our news network until WP 6.5.1.

(I don’t work here; just some feedback.)

I think it’s based on the domain name not the IP. So, you likely need to ‘release’ or ‘deactivate’ license on the old domain, and activate the new one.
I don’t work here, but I’m sure TD support will follow up on Monday 🙂

• This reply was modified 2 years by simchris.

We started usingthe WP-Staging plugin as neat way to do alt version in same place

If you updated to latest WordPress 6.5; try going to admin and F5 in Chrome or whatever browser to clear jquery cache. We were unable to set schedule for next day posts; clearing the cache of admin code, was only way page would work properly after 6.5 update. Might not be your issue, but try it 🙂
( I don’t work here.)

Theme and plugin wer updateed to fix the issue; however, if your site already infected only you can scrub and repair your installation *then* install the latest “safe” theme and plugin versions.
(I don’t work here; just loooooong time user.)

Sorry, forgot to mention, Google has made it harder to do the ‘clear amp cache’ thing. SHould have been a button in the official wordpress for amp plugin, but nooooooo.
If you serve 404s for the AMP endpoints, or do optional 301 redirects, that should suffice. There are no penalties or anything with removing AMP forever. Do it! 🙂
(I don’t work here, just loooooong time user.)
__ Chris S.

My pleasure. Also, note that Google has actually made it harder to clear the amp cache. So, really, no need to bother with that as either the 404 amp endpoints, optional 301 redirects, and removing the rel= links in the post meta data will solve that. At some point they will just switch AMP off entirely as they really don’t care.

We started building websites March of 1995; so have seen a lot come and go. AMP was a good idea if you had a busy site someplace with slow server, etc., but when Google basically ‘forced’ people to be on AMP for mobile search results (much like G+ was *required* for a local business listing), their “do no evil” mantra was dead and buried. So, they keep abandoning things (RIP, Feedburner), that I won’t invest in any of their tech unless no other choice. We were so happy to see AMP go the way of another bad idea, as far as I was concerned. The idea of having to waste huge amounts of time building second version of content was dumb when stuff like ‘print friendly’ pages have been around for 25+ years. Anyway… good riddance, I say 🙂

if using redirection plugin

REGEX

Redirect AMP pages
http://site.com/article/amp/ ⇒ http://site.com/article/
Source
^/(.*?)/amp/$
Target
/$1/
Redirect ?amp pages
http://site.com/article/?amp=12 ⇒ http://site.com/article/
Source
^/(.*?)/\?amp=.*
Target
/$1/

if using redirection plugin

REGEX

Redirect AMP pages
http://site.com/article/amp/ ⇒ http://site.com/article/
Source
^/(.*?)/amp/$
Target
/$1/
Redirect ?amp pages
http://site.com/article/?amp=12 ⇒ http://site.com/article/
Source
^/(.*?)/\?amp=.*
Target
/$1/

I would wait for 6.5.1 for edge bug fixes; and to allow all plugin folk to ‘catch up’ .. e.g., Yoast and ACF and others are pushing updates today. On one of our sites, we were unable to ‘schedule’ posts, and had to roll back from 6.5 to 6.4x (done via FTP).

Note: we had bunch of issues with WordPress 6.5 last night, and had to roll back to 6.4x. Waiting for 6.5.1.

Do you have proper open graph tags setup? When you ‘view source’ of your posts, do you see the FB image data there? Without OG tags, they cannot pull the image.
(I don’t work here.)

sure if you cannot type in numbers in a form, screen cap works… my plesk/parallels system is not noting this issue…
you will hear from support on monday, im sure 🙂