Works fine with PHP 8.2, but not 8.3.
Works fine with latest WordPress.
(My setup anyway; also on Plesk.)

However, not all third party plugins may be compatible. So, generally you would activate *current* version of theme and td-composer plugin, and leave everything else off temporarily.

You will also need to clear caching if used, and you may need to restart PHP on your server (and restart nginx if using that in front of apache).

7.4x will still work for awhile, but yes, time to move to 8x — which, ironically I’m doing for one of my sites literally right now today! 🙂

(I don’t work here; just 7+ year TagDiv user.) 🙂

I guess I could have just looked it up 🙂

https://forum.tagdiv.com/topic/kiss-amp-goodbye/

I posted last year on how to use the ‘redirection’ plugin, and setup proper 301 redirects for /amp -and/or- /?amp=1 versions of URLs. I think you can click on my name for past posts. Or maybe search AMP 301 redirects?

Basically, following Google’s recommendations. Luckily all the original pages were always canonical, and amp pages were alternates.

Probably need to login on desktop where you have more control vs phone tiny screen and fat fingers (my issue anyway), and go to settings > appearnace > themes and switch back to the correct theme.

I’ve been using Tagdiv themes for 7+ years on dozen sites and have never seen this happen!

(I DONT WORK HERE)

Might need to email them with the specififc license codes that are not working.

add AKISMET plugin

and stupidly WordPress still allows comments on posts created with comments ‘on’ … ugh.

I think on our sites we ended up adding custom code to force disable all comments sitewide – as the snippet found here:
https://www.wpbeginner.com/wp-tutorials/how-to-completely-disable-comments-in-wordpress/

(I dont work here.) 🙂

I don’t work here, but likely need more info than that for admin help.
What are you trying to do, what error are you getting? Did you try disabling any plugins other than the tagdiv page builder? Clear cache? Were you able to make posts in past, now cannot?

You first need to install the plugin, which should be in the all files download from Themeforest, in the plugins folder.

considering Google abandoned AMP two years ago, 2025 a good time to move on

What I mean was if you check the feed URL with the validator, it will tell you if you have a bad encoding or similar and if an error, no feed reader can intake it. If the validator says it is “okay” then it would work with Feedburner, unless Google having some weird issue again. 🙂

Might be issue with your data in your feed.
Did you check that it renders in Chrome when pasting your site.ooo/category/feed/ into chrome as normal URL?

And check validators like this?
https://www.feedvalidator.org/

FYI, generally, if the featured image and og tags are noted in the head of the post content, but also found in the multimedia attachment in the RSS feed (inspect in Google), it’s really up to the recieving platform to capture the image properly.

i change this on my sites by simply adding css over ride, use inspector in chrome to find css, then add new css to customizer or theme panel

You might look at ‘bbpress’ which is made by same folks who make WordPress as good place to start

also some info
https://www.wpbeginner.com/plugins/5-best-forum-plugins-for-wordpress/

make sure you have proper open graph tags (‘og tags’) in the header of your posts; this is usually done with something like Yoast, Rank Math, etc.

probably on your sign up page

UPSHOT: Google’s own docs say no penalty to killing AMP and setting up 301 redirects. It will generate errors in search console for a bit since inbound links no longer there, but that is why you have the 301 for /amp and /amp?=1 or whatever. The canonical link is the real main version of story, and even the amp versions linked to the canonical to not create duplicate posts. Essentially you are killing the duplicate posts. We did this for PDF versions 2 years back, also, same deal. 🙂 do it!!

#weird — my two follow up replies to this thread not showing ? Maybe ’20’ is max items in thread now.

hi, i posted the amp rewrite rules few months ago…might find under my name, posts

create subheads with h2 tag in your content?

In our case, usually issue with “too many” modules on home page, randomized elements, queries to external sites (socials), infinite loads, etc. Main thing is try to plan on limiting number of “modules” used on sidebars and home page. 2-3 sidebar modules max on posts; and maybe 4-5 max on home page.
(I don’t work here.)

Jumping in to say we finally removed AMP from all our sites and setup 301 redirects and the “errors” finally cleared out of our search console.

At this point, AMP serves no purpose, and frankly, the way Google works, coming up on two year mark, they could just anounce it’s no longer supported and stop working.

Advisable to move on from AMP and rely on mobile theme or optimized desktop site only (how we roll here).

🙂 Chris

Also note, Google does not choose to show all pages it indexes. It now decides if some pages will not appear or rank. Right now they are migrating to new AI based algorithm testing; they no longer accept new site requests for Google News and many searches like “company name” are not working.

As long as your site pages are in your sitemap, and are not showin in search console with an error, they have them, they are just not doing much with them.

Just some feedback as SEO pro since 1995.
(I don’t work here.)

AMP was abandoned by Google almost 2 years go.
No reason to use it anymore, nor should you.

Ideally, optimize your desktop version to “drop down” to mobile view with smart optimized responsive layouts.

🙂
(I don’t work here.)

On our sites, we found stuff like infinite load, too many modules in sidebar, too many modules on home page, dynamic queries for mega menu, dymanic queries to socials – all use hella lot of resources. You can test this by disabling things, and see what happens. Upshot: anything that has to do calculations like most popular, random, dbase lookup, etc — all use CPU.
(I don’t work here.)