OK there is a problem with Woody Snippets and your header ad now.
If I run the above edit to your theme, I can no longer create new snippets in Woody Snippets.
If I change it BACK to showing, the new snippets drop down is INSIDE of your ad and is interacting with your code. So somehow either your ad or Woody Snippets isn’t respecting each other’s space.
Your non-dismissable ad is now breaking my website… so frustrating.
Kim
Hi Anamaria,
Thanks, that set me in the right direction. I noticed that several posts had other data in the td_post_theme_settings. I don’t know if it’s supposed to be there or not but it is. It looks like Yoast data…
An example:
a:3:{s:10:"has_review";s:10:"rate_stars";s:14:"p_review_stars";a:3:{i:0;a:2:{s:4:"desc";s:26:"Very simple, rugged design";s:4:"rate";s:3:"4.5";}i:1;a:2:{s:4:"desc";s:27:"Clean design inside and out";s:4:"rate";s:3:"4.5";}i:2;a:2:{s:4:"desc";s:11:"Easy towing";s:4:"rate";s:3:"4.5";}}s:6:"review";s:218:"The Rustic Trailer Teardrop Campers Koala Bear travel trailer is a small, rugged and very simple option for campers who wish to elevate their tent camping experience or downsize from a complicated more traditional RV. ";}
So instead of just nulling that field for all posts, I located the standard pack template we were using and replaced just the portion of the text that I needed. This is what I used:
UPDATE wp_postmeta SET 'meta_value' = REPLACE('meta_value', 's:17:"single_template_5";', 's:15:"single_template";') WHERE 'meta_value' LIKE '%s:17:"single_template_5";%' COLLATE utf8mb4_bin
That fixed the problem completely.
This is yet another example of how poorly tagDiv managed the upgrade path from v9 to v10 (I have posted about this at length). This kind of thing >should< have been taken care of by your team or at least made a tool to make the one time upgrade from an older v9 site to the v10 without using the standard pack plugin.
The legacy code from the standard pack is killing our CPU usage (and probably costing us $100-$200 USD a month in CPU charges). I’ve put off removing the standard pack as long as I can but now I have to essentially rebuild the entire site.
Believe me when I say that another theme and page builder was calling my name the entire time I have been struggling with this problem…
Thanks for the info, I’ll get back to work and quit complaining now.
Kim
Hi Bettina,
I am so disappointed in your reply. That is a terrible response.
I came to you with a tested and confirmed bug that was caused by TD Composer and your response is “that’s your problem, not ours”.
Well here is an update for you:
I downloaded and tested every single Stripe payment option for WordPress from the repository.
ALL OF THEM FAILED WHEN TD COMPOSER WAS ENABLED except one.
The only one that worked is “Stripe Payments Plugin”.
The rest of them failed. Another one initiated a session with Stripe but then failed to open up the actual window to enter CC info.
So the problem the problem is with TD Composer v2.8 blocking the javascript that Stripe uses to connect to their credit card processors. This started after I applied the 10.4 theme update.
Another wrinkle is that since the JS is being blocked, the log files from WPForms showed no errors, the JS just never fired.
WPForms is just one of the users of said JavaScript. Why it works with “Stripe Payments Plugin” is unknown at this time, but also irrelevant to me because if TD Composer wasn’t blocking the JS that Stripe relies on I wouldn’t be using any other Stripe plugins.
Let’s try this again shall we and actually see if we can find a solution or at least a general direction for a solution? I would hate to have to roll back Newspaper to 10.3.9 but I will if this isn’t taken seriously by TagDiv.
Best,
Kim
I’ve tried turning these off with some code I wrote.
Here is the code that worked for me.
You can add other nodes to the list if you have other plugins crowding your admin bar on the front end.
Best,
Kim
function wps_admin_bar() {
global $wp_admin_bar;
$wp_admin_bar->remove_node( 'tdc_edit' );
$wp_admin_bar->remove_node( 'tdc_page_mobile_template' );
$wp_admin_bar->remove_node( 'tdc_create_mobile_page' );
$wp_admin_bar->remove_node( 'tdb_template_load' );
}
add_action( 'wp_before_admin_bar_render', 'wps_admin_bar', 999 )
My problem was resolved with a re-clone of the site and re-install of 10.3.2. I’m still having some minor interface issues but they are of little concern and the site is now working properly. Calin logged into my site and confirmed the issue but in trying to fix it the whole site became unstable, so clearly it was a bad clone because on setup of the new clone, it worked just fine. Thanks Calin!
Now I can get back to getting rid of the legacy code and using the newer blocks that are not dependent on the Standard Pack.
And I’ve finally found the combination of elements that replace the old block 11, which is flex block 1, image alignment set to float left and then spacing to suit your needs.
Other than a world wide pandemic, things are moving right along…
