- NewsmagtagDiv Composer Tutorial
- TutorialsFrom WPBakery to tagDiv Composer
- NewspapertagDiv Composer Tutorial
- NewsmagHow to use the Visual Composer plugin
- Apitd_api_block::update_key
- Apitd_api_block::update
- Apitd_api_block::add
- NewspaperCredit System
- NewspaperCreate a frontend submission form
- NewspaperHow to Use the Tabbed Content shortcode
- NewspaperCreate a form contact page
- NewspaperFilters and sorting for taxonomies
- NewspaperUser review system
- NewspaperModal Popup
- NewspaperFlex Block Settings Guide
- NewspaperSocial Sharing
- NewspaperSingle Post Shortcodes
- NewspaperInfinite Loading for Single Posts
- NewspaperThe Newspaper Mobile Theme: Introduction
- NewspaperHow to Add a Logo in Newspaper
Hi,
If you want to display articles based on a tab slug, use a single post template and edit it with tagDiv Composer, then add a block and in the filter tab, use the tag filter to display only the articles containing that tag slug – https://forum.tagdiv.com/flex-block-settings-guide/ https://i.imgur.com/ioechtM.png
In case that you are using a standard template, you can use the theme panel option for related article and set the type on by tag – https://i.imgur.com/TdRTe4u.png
Hi, I’m having a problem with TagDiv Composer on my website: https://www.conocerasturias.es
When I create a new page, it doesn’t load. It also doesn’t work with my existing pages, and the following text appears: ‘, footerTemplateId: ”, footerTemplateContent: ”, mobileMenuId: ’35’, tdbPInfiniteLoadStatus: ‘on’, tdbPInfiniteType: ”, tdbPInfiniteCount: ‘3’, isMobileTemplate: ‘0’, tdbTemplateSettings: [], }; // Set the local storage to show inline the iframe wrapper and the sidebar window.localStorage.setItem( ‘tdc_live_iframe_wrapper_inline’, 1 );
Here are some screenshots.
The headers also don’t work.
thank you
Hi team, just to inform you on this
Message: A non-numeric value encountered
Path:/var/www/vhosts/xxxx.xxx/httpdocs/wp-content/plugins/td-composer/legacy/Newspaper/includes/shortcodes
Script: td_flex_block_4.php
Line: 54
Plugin: td-composer
As it is a warning, it might be of interest for next release?
Thank you.
Hi,
Please replace the current td-composer plugin with the one in this link and the problem with Newsmag/js/tdAjaxSearch.js will be resolved.
Thank you!
Hi,
That would mean the post content begins with a video link, the automatic excerpt is picked from the beginning of the post.
One solution would be to set a manual excerpt in the post edit screen
– https://forum.tagdiv.com/excerpts-introduction/
But that could take some time if there are many posts in this situation.
Another way would be to un-comment this code in the highlighted file wp-content/plugins/td-composer/legacy/common/wp_booster/td_util.php
– https://imgur.com/LYoktzT
Doing this will remove all the links at once. I will make a note of this and check why that code is commented.
Thanks
Hi,
Please make sure you’re using the latest version of the theme Newspaper v12.7.1. After that, check the browser console when publishing a post to identify which request is causing the delay.
If you’ve already tested with only the tagDiv plugins active and the issue persists, I recommend replacing your current tagDiv Composer and tagDiv Cloud Library plugins with the versions below:
– https://cdn.tagdiv.com/wp-content/uploads/2025/05/td-composer.zip
– https://cdn.tagdiv.com/wp-content/uploads/2025/06/td-cloud-libraryfix.zip
Thank you!
Calin
Hi,
Unfortunately, the button can be moved only with css, you can use this css:
body .tdw-search-form .tdw-search-form-inner .wpb_button {
position: absolute;
}
You can set the css in tagDiv Composer in css zone – https://i.imgur.com/TUjcyHr.png
To have the same space between menu elements, please set the Elements space 0 and use Elements padding 0 15px – https://i.imgur.com/qCwmxpM.png adjust the padding after your needs.
The login elements can be set to the right using this custom css:
body .tdw-block-inner .tdw-wml-wrap .tdw-wml-menu{
text-align: right;
}
The code can be set in tagDiv Composer in css zone – https://i.imgur.com/JddsYrk.png
To adjust the space between the shop and my account element, select the shop cart and select the cs tab, then remove the left 30px margin and set 30 to the right margin – https://i.imgur.com/fIGCFt4.png https://i.imgur.com/Yu3OYD1.png (it is possible to me more elements that need to be fixed like this, because the css was set for LTR direction and does not need to be changed for RTL)
Thank you!
Hi,
Ok, so the first step is to have an RTL language selected on wordpress, for example, I will select Arabic – https://i.imgur.com/90vPjA9.png, then go to Cloud templates and click on + on Header templates – https://i.imgur.com/XguMYXz.png, then search for “makeup” https://i.imgur.com/GW3D4L2.png open the template in tagDiv Composer – https://i.imgur.com/Kuk7maO.png, then it should look like this https://i.imgur.com/gpGfdsC.png then just drag and elements in the palce you want (change logo) …. for example drag the left column with the menu in the right – https://i.imgur.com/TK0k9vI.png https://i.imgur.com/AM5hv6u.png the menu elements to be display from ltr to rtl use this custom css :
.rtl .tdb_header_menu .tdb-menu {
flex-direction: row-reverse;
}
I hope this will help you!
Calin, that’s it, I figured it out! )
It was necessary to duplicate the code of the “Forum” page in the field with the “Mobile Editor” admin panel
https://skr.sh/sXCMW6Lqa3R
Sorry, the last question remains. How are these block headers https://skr.sh/sXC6kd9z7ML should I convert it to Russian in English so that the KOI8 encoding is supported?
I changed it in the file /public_html/wp-content/plugins/td-composer/mobile/includes/shortcodes/td_block_related_posts_mob.php the title is in Russian https://skr.sh/sXCrAHgnuy1 , but on the website, the word НОВОСТИ is displayed with question marks <?>.
In theory, the “tagDiv Mobile Theme” plugin should inherit the default font of the theme.
===========
Calin, все, разобрался! )
Надо было код страницы “Форума” продублировать в поле с админкой “Mobile Editor”
https://skr.sh/sXCMW6Lqa3R
Извините, последний вопрос остался. Как эти заголовки блоков https://skr.sh/sXC6kd9z7ML на английском языке переделать на русский, чтобы поддерживалась кодировка KOI8?
Я поменял в файле /public_html/wp-content/plugins/td-composer/mobile/includes/shortcodes/td_block_related_posts_mob.php заголовок на русский https://skr.sh/sXCrAHgnuy1 , но на сайте слово НОВОСТИ отобразилось знаками вопроса <?>.
По идее плагин tagDiv Mobile Theme должен наследовать дефолтный шрифт темы.
Fehler-Details
==============
Ein Fehler vom Typ E_ERROR wurde in der Zeile 3276 der Datei /home/expomaxt/public_html/gartenwoche_2024/wp-content/plugins/td-subscription/includes/td_subscription.php verursacht. Fehlermeldung: Uncaught TypeError: array_key_exists(): Argument #2 ($array) must be of type array, null given in /home/expomaxt/public_html/gartenwoche_2024/wp-content/plugins/td-subscription/includes/td_subscription.php:3276
Stack trace:
#0 /home/expomaxt/public_html/gartenwoche_2024/wp-includes/class-wp-hook.php(324): td_subscription::td_post_theme_settings_mb_save_filter(NULL, ‘3213’)
#1 /home/expomaxt/public_html/gartenwoche_2024/wp-includes/plugin.php(205): WP_Hook->apply_filters(NULL, Array)
#2 /home/expomaxt/public_html/gartenwoche_2024/wp-content/plugins/td-composer/legacy/common/wp_booster/wp-admin/external/wpalchemy/MetaBox.php(880): apply_filters(‘wpalchemy_filte…’, NULL, ‘3213’)
#3 /home/expomaxt/public_html/gartenwoche_2024/wp-content/plugins/td-composer/legacy/common/wp_booster/wp-admin/external/wpalchemy/MetaBox.php(2081): WPAlchemy_MetaBox->apply_filters(‘save’, NULL, ‘3213’)
#4 /home/expomaxt/public_html/gartenwoche_2024/wp-includes/class-wp-hook.php(326): WPAlchemy_MetaBox->_save(8441)
#5 /home/expomaxt/public_html/gartenwoche_2024/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
#6 /home/expomaxt/public_html/gartenwoche_2024/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#7 /home/expomaxt/public_html/gartenwoche_2024/wp-includes/post.php(5110): do_action(‘save_post’, 8441, Object(WP_Post), true)
#8 /home/expomaxt/public_html/gartenwoche_2024/wp-includes/post.php(5212): wp_insert_post(Array, false, true)
#9 /home/expomaxt/public_html/gartenwoche_2024/wp-admin/includes/post.php(2003): wp_update_post(Array)
#10 /home/expomaxt/public_html/gartenwoche_2024/wp-admin/includes/post.php(2104): wp_create_post_autosave(Array)
#11 /home/expomaxt/public_html/gartenwoche_2024/wp-admin/post.php(336): post_preview()
#12 {main}
thrown
We ran into a reproducible issue with the Newsmag theme (tagDiv Composer) when importing a demo on PHP 8.2.
Symptoms:
tagDiv Importer stops with error:
Fatal error: Uncaught TypeError: Cannot access offset of type string on string in td_demo_util.php
Log also shows Undefined variable $sidebars_widgets and Automatic conversion of false to array is deprecated.
Root cause:
In td_demo_widgets::add_widget_to_sidebar(), the code uses $sidebars_widgets before it’s retrieved from get_option(‘sidebars_widgets’) and normalised.
PHP 8.x is stricter about this than PHP 7.x — in PHP 7 it silently converted null/false to array; in PHP 8 it throws a fatal error.
Workaround:
Patch the function to fetch and normalise $sidebars_widgets before using it. Here’s a minimal fix:
static function add_widget_to_sidebar($sidebar_id, $widget_name, $atts) {
$tmp_sidebars = td_options::get_array('sidebars');
if (empty($tmp_sidebars)) {
$tmp_sidebars = array();
}
if (!in_array('td-' . $sidebar_id, self::$hard_coded_sidebars) &&
!in_array($sidebar_id, $tmp_sidebars)
) {
self::kill(__CLASS__, __FUNCTION__,
'No sidebar with the name provided! - td-' . $sidebar_id,
array_merge(self::$hard_coded_sidebars, $tmp_sidebars)
);
}
// Normalise $atts
if (!is_array($atts)) {
if (is_string($atts)) {
$tmp = json_decode($atts, true);
$atts = is_array($tmp) ? $tmp : array();
} else {
$atts = array();
}
}
// FIX: Get and normalise $sidebars_widgets BEFORE using
$sidebars_widgets = get_option('sidebars_widgets');
if (!is_array($sidebars_widgets)) {
$sidebars_widgets = array();
}
$sb_key = 'td-' . td_util::sidebar_name_to_id($sidebar_id);
if (!isset($sidebars_widgets[$sb_key]) || !is_array($sidebars_widgets[$sb_key])) {
$sidebars_widgets[$sb_key] = array();
}
// Normalise widget instances
$opt_key = 'widget_' . $widget_name;
$widget_instances = get_option($opt_key);
if (!is_array($widget_instances)) {
$widget_instances = array();
}
// Add instance
$widget_instances[self::$last_widget_instance] = $atts;
update_option($opt_key, $widget_instances);
// Assign widget to sidebar
$sidebars_widgets[$sb_key][self::$last_sidebar_widget_position] =
$widget_name . '-' . self::$last_widget_instance;
update_option('sidebars_widgets', $sidebars_widgets);
self::$last_sidebar_widget_position++;
self::$last_widget_instance++;
}
Notes:
Tested on PHP 8.2.29 with Plesk Obsidian and Newsmag 5.4.3.3.
This patch allows the demo importer to complete successfully without downgrading PHP.
The EXIF warnings you may see in logs during import are unrelated and non-fatal.
If tagDiv devs see this — moving the $sidebars_widgets = get_option(‘sidebars_widgets’) block up in the function would resolve this for all PHP 8+ users.
Hi,
I’m running into a fatal error when trying to import a demo in Newsmag 5.4.3.3 (registered) with tagDiv Composer on a Plesk server.
The issue occurs on PHP 8.2 and PHP 8.4 during the demo import process.
Error Details
swift
Kopier
Rediger
PHP Fatal error: Uncaught TypeError: Cannot access offset of type string on string
in /wp-content/plugins/td-composer/legacy/common/wp_booster/wp-admin/panel/td_demo_util.php:2620
Stack trace:
#0 /…/td_import.php(159): td_demo_widgets::add_widget_to_sidebar()
#1 /…/td_demo_installer.php(319): require_once()
…
Additional warnings/notices during import:
Multiple exif_read_data(…): Incorrect APP1 Exif Identifier Code warnings
_load_textdomain_just_in_time called too early (WordPress 6.7.0 notice)
The fatal error prevents the demo from completing.
Environment
Theme: Newsmag 5.4.3.3 (registered)
tagDiv Composer: bundled version (legacy importer paths)
WordPress: 6.7.0
PHP Versions Tested: 8.2.x (FPM), 8.4.x (FPM) — both fail
Server: Plesk Obsidian, Apache2 (proxy_fcgi)
What We Found So Far
The error happens inside the legacy demo importer, specifically in td_demo_widgets::add_widget_to_sidebar() — looks like a PHP 8.1+ type handling change is breaking it.
The /legacy/… path suggests the importer code hasn’t been fully updated for PHP 8.2+.
No public changelog entries mention a fix for this specific fatal error.
There’s no pinned forum post or KB article covering it.
Rolling back to PHP 8.1 might work, but my current server doesn’t have it installed — planning to try that as a temporary workaround.
If the vendor has already patched this in a newer Composer or theme build, it’s not mentioned in docs.
Questions
Is this a known issue with the current demo importer on PHP 8.2+?
Has it been fixed in a newer release of Newsmag/tagDiv Composer (non-legacy importer)?
Is there an official workaround besides downgrading to PHP 8.1?
If I install PHP 8.1 just for the import, will that be supported, or do you recommend patching the importer code for PHP 8.2+?
Thanks in advance — happy to provide full error logs or run tests if it helps.
— Terje
[STDERR] PHP Fatal error: Uncaught TypeError: Unsupported operand types: int – string in /home/livingin1/public_html/wp-content/plugins/td-cloud-library/state/single/tdb_state_single.php:1338\nStack trace:\n#0 /home/livingin1/public_html/wp-content/plugins/td-cloud-library/shortcodes/single/tdb_single_date.php(216): tdb_state_single->{closure}()\n#1 /home/livingin1/public_html/wp-content/plugins/td-cloud-library/shortcodes/single/tdb_single_date.php(216): Closure->__invoke()\n#2 /home/livingin1/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_global_blocks.php(27): tdb_single_date->render()\n#3 /home/livingin1/public_html/wp-includes/shortcodes.php(434): td_global_blocks::proxy_function()\n#4 [internal function]: do_shortcode_tag()\n#5 /home/livingin1/public_html/wp-includes/shortcodes.php(273): preg_replace_callback()\n#6 /home/livingin1/public_html/wp-content/plugins/td-composer/includes/tdc_composer_block.php(222): do_shortcode()\n#7 /home/livingin1/public_html/wp-content/plugins/td-composer/includes/shortcodes/vc_column.php(440): tdc_composer_block->do_shortcode()\n#8 /home/livingin1/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_global_blocks.php(27): vc_column->render()\n#9 /home/livingin1/public_html/wp-includes/shortcodes.php(434): td_global_blocks::proxy_function()\n#10 [internal function]: do_shortcode_tag()\n#11 /home/livingin1/public_html/wp-includes/shortcodes.php(273): preg_replace_callback()\n#12 /home/livingin1/public_html/wp-content/plugins/td-composer/includes/tdc_composer_block.php(222): do_shortcode()\n#13 /home/livingin1/public_html/wp-content/plugins/td-composer/includes/shortcodes/vc_row.php(1204): tdc_composer_block->do_shortcode()\n#14 /home/livingin1/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_global_blocks.php(27): vc_row->render()\n#15 /home/livingin1/public_html/wp-includes/shortcodes.php(434): td_global_blocks::proxy_function()\n#16 [internal function]: do_shortcode_tag()\n#17 /home/livingin1/public_html/wp-includes/shortcodes.php(273): p
2025-08-12 06:39:54.154375 [NOTICE] [100585] [T0] [213.183.63.23:44728>87.97.241.170#APVH_livinginashoebox.com:443] [STDERR] reg_replace_callback()\n#18 /home/livingin1/public_html/wp-content/plugins/td-composer/includes/tdc_composer_block.php(222): do_shortcode()\n#19 /home/livingin1/public_html/wp-content/plugins/td-composer/includes/shortcodes/tdc_zone.php(771): tdc_composer_block->do_shortcode()\n#20 /home/livingin1/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_global_blocks.php(27): tdc_zone->render()\n#21 /home/livingin1/public_html/wp-includes/shortcodes.php(434): td_global_blocks::proxy_function()\n#22 [internal function]: do_shortcode_tag()\n#23 /home/livingin1/public_html/wp-includes/shortcodes.php(273): preg_replace_callback()\n#24 /home/livingin1/public_html/wp-includes/class-wp-hook.php(324): do_shortcode()\n#25 /home/livingin1/public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters()\n#26 /home/livingin1/public_html/wp-content/plugins/td-cloud-library/wp_templates/tdb_view_single.php(189): apply_filters()\n#27 /home/livingin1/public_html/wp-includes/template-loader.php(106): include(‘…’)\n#28 /home/livingin1/public_html/wp-blog-header.php(19): require_once(‘…’)\n#29 /home/livingin1/public_html/index.php(17): require(‘…’)\n#30 {main}\n thrown in /home/livingin1/public_html/wp-content/plugins/td-cloud-library/state/single/tdb_state_single.php on line 1338\n
I bought this plugin in 2019 and installed it in the available wordpress version back then.
The plugin version is 2.3 in tagDiv Composer and 4.5 in tagDiv Social Counter.
My wordpress version is 6.4.6.
As I wrote on the title, the problem is that every day, both plugins get disabled for no reason and It breaks the website UI.
I’ve tried to search some reason in the logs but I didn’t find anything.
I’ve tried to update them to the last version but I got this error:
Fatal error: Cannot redeclare td_include_user_compiled_css() (previously declared in /var/www/html/wp-content/themes/Newspaper/includes/wp_booster/td_wp_booster_functions.php:344) in /var/www/html/wp-content/plugins/td-composer/legacy/common/common.php on line 59
Hi,
Please replace the current tagdiv composer plugin with the one from below:
– https://cdn.tagdiv.com/wp-content/uploads/2025/05/td-composer.zip
I hope this will resolve the problem.
Thank you!
Hi,
Just to make sure that I understand correctly, in the first image provided, you have an image from the mobile version and the tagDiv Mobile theme plugin, to display ads on it you need to set the ads in the mobile theme in the theme panel – https://i.imgur.com/wnGpwtd.png
Also, on desktop, the ad should be displayed using the ad box element that can be set using tagDiv Composer – https://i.imgur.com/nSFvDN6.png
Thank you!
Thank you for the clarification.
Just to confirm: in my case, I’ve added an extra class like .title { position: absolute; background-color: red; } to an element that already has the default TagDiv Composer class .td-module-title { position: relative; background-color: black; }.
– Does the custom class .title which is add an extra class get loaded after the default TagDiv styles in terms of CSS order or not?
– If both classes are applied to the same element, and my custom CSS is overriding the default styles, does that mean the default styles are still being unwanted css code unnecessarily in css file?In such cases, is it possible to remove the default TagDiv CSS code?
Since we’re applying custom styles through an extra class, the default CSS becomes unnecessary for that element. This adds unused code to the stylesheet, making the overall CSS heavier. Is there a recommended method to safely remove or exclude such default styles? If possible?
Thanks,
Atul
Hi TagDiv,
I have a question regarding custom CSS code. Let’s say I’ve added an extra class help of tagdiv composer to an element and applied custom CSS to it. Will this conflict with the default CSS provided by the TagDiv Composer?
For Example:-
I’ve added an extra class .title { position: absolute; , background-color: red;}
While the default TagDiv Composer class is .td-module-title { position: relative; , background-color: black;}
Will these two styles conflict with each other? or will the CSS code I’ve added to my extra class take priority?
And second question is Can I use Inspect Element to find the default CSS classes assigned by TagDiv Composer to the element, and then add my custom code directly to those same classes?
Would this be considered a good practice?
Also, could having multiple classes on a single element have any negative impact on SEO?
Thanks,
Atul
Hello @Calin and team, in continuation to another post, I want to report another error I see on upgrading to PHP 8.2 – funnily, in a non-logged in view only.
Deprecated: Function WP_User_Query was called with an argument that is deprecated since version 5.9.0! who is deprecated. Use capability instead. in /home/customer/www/staging3../public_html/wp-includes/functions.php on line 6121
Problem seems to be with td_composer.
I also use a child theme… any idea what could solve this?
Getting an error code all of the sudden with TagDiv Composer
Need help to fix it!
https://gregwyatt.com/the-life-journey-of-greg-wyatt-70-years-strong/
Warning: foreach() argument must be of type array|object, null given in /home/blndrx12/www.gregwyatt.com/wp-content/plugins/td-composer/includes/tdc_util.php on line 608
Warning: foreach() argument must be of type array|object, null given in /home/blndrx12/www.gregwyatt.com/wp-content/plugins/td-composer/includes/tdc_util.php on line 608
It’s showing up on all the pages.
Thank you!
I’m not having this issue on our sites.
You might try
a) via FTP, delete theme folder; upload new copy (do not over write old)
b) delete TD composer plugin; upload new copy (do not overwrite old)
Login and make sure both activated. Test a page edit.
If using something like Pagespeed that compresses js files, consider disabling to debug.
(I don’t work here.)
Hello, this is Carlo from the Altervista Hosting development team.
We identified that the website https://www.saluteperfetta.it/ and https://www.sportcultura.it hosted by us is having issues due to an incorrect usage of the hook the_post called by your plugin td-composer: in the file td-composer/includes/tdc_main.php on line 1174 your code calls the action the_post with just one argument, which is incorrect.
Starting from WordPress 4.1.0 (released in 2015) the action the_post always passes *two arguments*, please check also the official documentation https://developer.wordpress.org/reference/hooks/the_post/.
Could you please fix your code in order to always call the the_post action in a correct way? This would not only fix the incompatibility issue with our service but would also increase compatiblity with any other plugin or theme that expects to receive both arguments in the_post.
If you need more details, please contact us at basic_feedback@altervista.it
Thanks,
Carlo
Hello Calin,
I have successfully installed td-Composer, but td-Couldliberyfix has declined (it indicates no plugins were found). So the problem is still there.
Kindly note that I have the latest version 12.7.1
Hi,
I recently bought the Newspaper template and used the Forest Beat theme and found the experience to be so extremely difficult-to-use and cumbersome.
It doesn’t come with a page template – which is fine – but clearly there’s no way for me to even create a tagdiv template at all that my non-post pages can use. A hacky way I did was to import any random template into “Page”, and copy-pasted the Base64-encoded source.
I went through your knowledgebase and there doesn’t seem to be any way to figure out how this can be used?
1. How do you even add your own template such that it can be used by pages? I only just need a simple page layout but seems to be an impossible task.
2. If I want to customise the “Single Post Author” component on a page, I noted the default Forest Beat overrides font-size as 16px, somehow I cannot replicate that via the tagDiv composer?
3. I wanted to change the theme colours of Forest Beat, from the theme colours tab, I can only change the primary accent and a bunch of other colours, but I cannot find these:
--light-green-forest-beat – where can I modify this?
The entire tbd-global-colors block (via view-source) is:
--mm-custom-color-4:#C2A25D;--mm-custom-color-5:#F7F9F9;--mm-custom-color-1:#053426;--mm-custom-color-2:#B79259;--mm-custom-color-3:#79847E;--accent-color:#fff;--accent-forest-beat:#5c6b28;--dark-green-forest-beat:#1D2110;--white-forest-beat:#FFFFFF;--transparent-white-forest-beat:rgba(255,255,255,0.25);--transparent-white-2-forest-beat:rgba(255,255,255,0.6);--transparent-white-3-forest-beat:rgba(255,255,255,0.7);--transparent-dark-green-forest-beat:rgba(29,33,16,0.8);--transparent-dark-green-2-forest-beat:rgba(29,33,16,0.25);--light-green-forest-beat:#F3F7EE;--transparent-dark-green-3-forest-beat:rgba(29,33,16,0.65)
Is the experience intended to be like that?
Hello,
The featured image on the single post template 12 will not resize correctly for mobile. I have changed every single option in the composer tab, custom CSS, and the image will not move or do anything.
What do I need to change to get the image to respond to mobile size?
Thanks
