I did this a couple of times — this is AI answer, possibly wrong —
Manual HTML Iframe (More Control)
Use this if the standard embed block does not display correctly or if you want to customize the dimensions.
Get Embed Code: On the Facebook Reel (desktop), click the three dots (…) or the Share button and select Embed.
Copy Code: A popup will appear with an HTML snippet. Copy this code.
Insert in WordPress:
In the WordPress editor, add a Custom HTML block.
Paste the copied code into the block.
Use the Preview tab to see how it looks before publishing.
Among other things, the version of simplepie was updated in core and breaks anything using the old version!
A *lot* of plugins are not compatible (yet) with WP 6.9 – Yoast, WooCommerce, Elementor all had to do emergency updates – one plug I rely on, FeedWordPress generates error trying to run. WP 6.9 changed some core code, which breaks a *lot* of stuff.
I rolled back to 6.8x on five sites to ensure they work.
(I don’t work here.)
We have had some issues on some sites, unrelated to tagdiv with the new WP 6.9 update today. Rolling back to 6.8x solved it. (I don’t work here.)
Probably a bug in RM if it breaks websites.
Probably want to migrate site to new hosting first using any of the modern host-provided move tools. Once moved, you’d then probably look at using something like the newsmag theme. You will need to install the new theme, disable existing plugins, back up working site on new server including server dbase, then activate new theme, then activate new copy of td-composer included with newsmag, then you will need to go in and change settings to preferred default templates for posts, archives; then make a new home page layout using the theme builder.
Works great with PHP 8.3x — most WP stuff does *NOT* yet work on PHP 8.4 which has edge-tech for all kinds of changes to dbase and functions. 8.3x is the current mainstream version of PHP to use.
Did you, via FTP; after disabling caching plugin;
a) delete old theme
b) upload new, uncompressed theme folder, not the ‘all files’ folder
c) delete td-composer plugin
d) upload new td-composer plugin
e) login
f) re-enable td-composer plugin
??
This works for me on every site, running PHP 8.3x.
I have always found using manual update via FTP works best – I am literally doing this right now 🙂
Many sites and plugin builders, themes, and platforms use images as “backgrounds” – this is a normal practice, not unique to TagDiv.
No problems here.
Themeforest sent out a notice this morning that update is available to download.
Best way to update, is decompress files on local drive; then login via FTP to site, remove old theme, upload new version; remove old plugin for td-composer; upload new version.
Log into panel, activate composer plugin. Check menus and footer.
Always make backup of site prior to update!
i update via ftp, deleting old theme and applicable plugin folders, the uploading new versions from themeforest download and decompressed, then login, and reactivate plugins
ah, thanks ! will try.
my brain is still stuck on v3; keep forgetting the stuff now in the plugin.
🙂
For anybody testing, make sure to test some of the javascript optimizations on/off, as one broke the menu, where menu items would not leave front page. Those really should be output as pure CSS, but managed to tweak and resave and no issues.
ajax counter works great
oh…now i have to remember how to set view counter to keep working with caching
isnt this set on the wordpress settings general tab?
I don’t work here, but generally it’s not advisable to use two different page builders with the same theme.
Be sure to install the IndexNow plugin also.
And, be aware Google has started “whacking” a lot of news sites in search, when you don’t have “first origin” stories, such as sites with too many cloned press releases, or follow on content from major sources like AP, NYTimes, etc.
We have run into this issue recently after updating our version of Newsmag theme earlier this year, and several sites dropped out of Google News as well, but it’s not just us. Just weird timing.
We’re also suddenly, recently, started getting a lot of the “not indexed as not found in any sitemaps” even though in the Yoast sitemap. 20 year old website!
We have been doing some house cleaning on old content, also optimizing and retiring images, and also doing some “manually request indexing” on some pages which should be in results, and are not since the revamp.
I can only chaulk this up to Google trying to roll out AI snippets vs actual links to news sites — providing AI summary of your content vs your actual content, which some publishers have now sued Google over.
It’s a Google thing, as one site having “trouble” with Google since revamp, is still showing up top of all *other* search engines, so it’s a unique thing with Google.
Pardon the epic poem — just thought I’d give you a supportive “it’s not just you” support note.
(I don’t work here.)
fyi, for anybody running across this thread regarding optimizations …
for quick band-aid I re-installed Autoptimize, which I’d not used for years, and also added back the deflate rules to my htaccess file which I’d removed while debugging the issue with php8 ignoring htaccess directives.
These two fixes took the site from 83% to 95% on GTMetrix.
Finally, for those thinking of doing WP-Rocket, if you add or renew a paid subscription to GTMetrix for testing, they will give you 20% off coupon for the first year of WP-Rocket, so no brainer there.
Thanks. I know on the prior version of NM I went nuts on hacking things to remove any and all code, and unhook stuff. Didn’t do that this time and combined with loss of server side optimizations, sites really took a hit in Google. Trying to do damage control on that now.
Probably going to try wp-rocket.
Stuff like ThickBox.js is being loaded on post pages where never used, so really making a lot of fluff in page size and ttfb.
I really went nuts on the old versioh, subsetting font awesome, etc. — trying not to do that again as just a nightmare if any theme updates.
Peace out 🙂
