Thanks. Even though it says ‘Thumb Placeholder’, if uploaded at 1920 x 1080, would it also be used as the featured image on all single post templates as well as blocks?

For the time being, I’ve uploaded my custom thumbs to the plugin directory and simply replaced the default versions.

Thanks
Matt

Is it also a short-term idea to delete the ‘td_live_css_local_storage’ row in the database entirely or does the vulnerability allow it to be created and populated?

Incidentally, I’ve deleted the complete Option Value (below) and my background ads have now started to work again.

The full option value was as follows.

a:2:{i:0;s:0:””;s:3:”css”;s:125:”</style><span style=”position: absolute; left: -9655px;”>
test
</span>
<div>”;}

Again, should I be concerned?

Hi Guys, I’m using version 12.3 and have the following in my database.

Option Name
td_live_css_local_storage

Option Value
a:2:{i:0;s:0:””;s:3:”css”;s:125:”</style><span style=”position: absolute; left: -9655px;”>

I spotted this when trying to diagnose an issue with background ad spaces on my site where the hyperlink had stopped becoming clickable. I was looking through the source and spotted the following random code. This is near the top of the page.

<span style=”position: absolute;left: -9655px;display: none;”>
test
</span>

Should I be concerned?

Hi, given that is_single() doesn’t seem to identify the current post ID I’ve managed to get around this by using get_the_ID() which does seem to be able to identify the current post ID.


$current_post_id = get_the_ID();
$post_id_array = array(1,2,3,4,5);
if (in_array($current_post_id, $post_id_array))
{
echo 'CUSTOM ALERT';
}


This seems to work fine.
Thanks
Matt

Hi Bettina, I get that cloud templates are CPTs but when echoed on the page, get_the_id() shows the ID of the currently queried single post, not of the CPT template file.

When we use a conditional statement using if ( is_single (12345) ); it doesn’t recognise the 12345. We’ll have to try and design a workaround if you’re suggesting this is custom work. We’d still have expected core WP functions to work within templates.

Thanks
Matt

Hi Bettina, thanks for the reply, I don’t need customisation services, I simply need to know why is_single() doesn’t seem to work, even when just checking a single post and not an array.

Thanks
Matt

Hi Anamaria, is that not for ACF Fields, not Custom Taxonomies?

Matt

Hi Anamaria, thanks for the confirmation.

The ability to have these as and/or fields/filters would be really useful. We use tags for ‘Featured’ content too, so being able to show content from the current category that also has a specific tag would be really useful.

Thnaks
Matt

Hi Anamaria, we’re adding the Flex Block 1 onto a Category Template.

The filter is set to ‘Current Category’ and the ID of the Custom Taxonomy ’11’ is added in the ‘Multiple terms filter’ field. Please see the attached screengrab for confirmation.

When we save those settings and return to the live site, no matter what category archive we view, the four articles are always from the ’11’ taxonomy and all categories, not just the ‘Current Category’.

Should this work or are the two filters not && ?
Thanks
Matt

Thanks Anamaria, email just sent.

Matt

Hi Anamaria, the site is currently in Maintenance mode as it’s brand new and not live yet.

Do you have an email where I can send a bypass link to?

Control Panel Screengrab

Google Console Screengrab

Hi Anamaria, the workaround I’ve found is as follows.

.td-header-desktop-wrap .tdc_zone {max-width:1164px;margin:auto; box-shadow: 0 -10px 10px 2px rgba(0,0,0,0.1) !important;}
.td-main-content-wrap {box-shadow: 0 0 10px 2px rgba(0,0,0,0.1) !important;}
.td-footer-wrap .tdc_zone {max-width:1164px;margin:auto; box-shadow: 0 10px 10px 2px rgba(0,0,0,0.1) !important;}
.td-main-page-wrap {overflow: visible !important;}

The .tdc-zone needed a max-width of 1164px to remain at the boxed width along with auto margins to centre align it. This seems to have done the trick.

Is tagDiv Composer 3.9 different to tagDiv Composer 4.1? What’s caused the difference between the two sites, I’m intrigued.

Thanks
Matt.

Hi Anamaria,

I’ve added the suggested CSS to my custom stylesheet but it still doesn’t work for the header or footer. The only way I can get it to render properly is if I add the additional CSS, otherwise, the header and footer wrap is full width and the drop shadow renders outside of the full browser width.

.td-header-desktop-wrap {width:1164px; margin:auto;}
.td-footer-wrap {width:1164px; margin:auto;}

I have the website background colour set to #ffffff and have the boxed layout selected.
I also have the rows in the cloud header and footer templates set to ‘Default’ so they should be obeying the boxed layout setting from the theme panel but they aren’t.

The shadow works fine for the .td-main-content-wrap.

Thanks
Matt

Perfect, thanks Bettina.

I knew there would be a simple solution.

Thanks
Matt

Hi Bettina, I’ve been using tagDiv Newspaper for quite some years on numerous projects so I’m familiar with the block filters, I can’t however find any way to tilter a block from a custom taxonomy value.

Is this possible?

Hi Bettina, thanks for that, it seems to have resolved the issue.

Would we have to use a similar definition for custom taxonomy cloud templates to check the queried term_id?

Matt

Yes, we’re initially trying to use it in a cloud template for a custom post type.

I’ve tried to use the_title() in the same shortcode template file but this prints ‘Custom Template Name’ instead of the title of the post being displayed.

If we use ACF fields they display nothing.

If we then add the $mk_current_post_id = $this->post->ID; or $post_id = $this->post->ID; to the shortcode template file it creates a fatal error.

Hi Bettina, I’m trying to use ACF fields as part of custom shortcodes used in tagDiv Composer. If the post id isn’t defined the fields don’t return any values, so the shortcodes I’m using need to have some way of setting the queried post id.

This is how I’ve done it previously.

$mk_current_post_id = $this->post->ID;
if ( get_field( ‘mk_acf_contributor_primary_role’ , $mk_current_post_id ) ):
the_field( ‘mk_acf_contributor_primary_role’ , $mk_current_post_id );

This returns a fatal error.

Hi Guys, it’s been a while since I originally experienced this issue but I just wanted to pick it up again as I’m having similar problems again.

I’ve recently updated to tagDiv Composer 3.9 and I’m using the same method outlined in this thread to display ACF custom fields inside custom shortcodes in composer.

I can see from the td_module.php file in tagDiv composer you use the following to select field values from the current post too.

$post_id = $this->post->ID;

But this also causes a fatal error if I include it in my shortcode template file.

This is what my shortcode looks like.

$post_id = $this->post->ID;
if ( get_field( ‘mk_acf_contributor_primary_role’ , $post_id ) ):
the_field( ‘mk_acf_contributor_primary_role’ , $post_id );

Am I missing anything obvious?

I’ve seen you’ve added ACF support in composer but I need to do compile more complex elements which add links from ACF fields etc too so I need to be able to define my own custom template parts compiled from ACF field data.

Thanks
Matt

Hi Bettina, thanks for the feedback. I’ve worked out how to assign a global template for custom post types but I wanted to know whether we can assign a template on a per-custom post type basis like we can for default posts in ‘Page Settings’?

So in the below screengrab, we can select from standard pack templates AND custom cloud templates for posts, this isn’t an option for custom post types.

Thanks
Matt

Also, and I’m not sure if this is related, but even though I’m using the latest version of WordPress I’m still seeing this issue in Jquery Migrate Helper.

jQuery Migrate Helper — Warnings encountered
This page generated the following warnings:

https://www.pbctoday.co.uk/news/wp-content/plugins/td-composer/assets/js/js_files_for_wp_admin.min.js: jQuery.fn.load() is deprecated
Please make sure you are using the latest version of all of your plugins, and your theme. If that is the case, then you may want to ask the developers of the code mentioned in your warnings to update it.

Here are the three warnings which are being logged with trying to edit a page (load the composer).

Notice: jQuery.fn.load() is deprecated
Theme: Newspaper
Location: /wp-content/themes/newspaper/js/tagdiv_theme.min.js

Notice: jQuery.fn.load() is deprecated
Plugin: tagDiv Composer
Location: /wp-content/plugins/td-composer/assets/js/js_files_for_wp_admin.min.js

Notice: jQuery.fn.load() is deprecated
Plugin: tagDiv Composer
Location: /wp-content/plugins/td-composer/assets/js/js_files_for_wrapper.min.js

Hi Anamaria, is there not a quick solution we can implement? Updating our entire site is quite a long winded process. We were hoping there would be a short term solution
to save having to update everything and potentially break everything.

Thanks
Matt