This was resolved when I moved the site live and reinstalled the SSL certificate.

Thank you, Calin. Just to confirm, what I need to do is create a copy of the cloud header I created and select that new header to modify it with the menu I want?

Please disregard, it was the sub-menu with anchor links that was causing the issue.

Please disregard, I found the issue – it was the file structure of the child theme that caused the issue. Hope you guys have a great holiday and new year!

I like your site, nice design! You may want to try clearing your cache in your browser and/or caching plugin. I can see the mega menu under Math.

Thank you, Simion. I understand the process of translating the pages but it seems that WPML does not recognize the elements on the page to allow me to translate existing pages in English into Chinese.

Working with WPML’s support team, they believe the issue is that the shortcode used by elements in the TD Composer is not being recognized by WPML and that I will need to add code in the WPML XML Editor in order to make this work. Here are the steps I am being told I need to take: https://wpml.org/documentation/translating-your-contents/page-builders/how-to-register-page-builder-modules-and-theme-options/

Did WPML work before without requiring this additional step in the past? Did this change after the recent update to the Newspaper 10 theme? I only ask because I’m hoping there is a simpler path to resolving this then following steps in their support article.

I found documentation on WPML site (https://wpml.org/documentation/theme-compatibility/create-multilingual-wordpress-websites-using-the-newspaper-theme-and-wpml/) and it looks like I will need to declare the shortcodes used by TD Composer so that it can translate the individual elements. Is there any documentation on what the shortcodes are for the various elements used by TD Composer?

Update: I have been fiddling with a staging copy of one of our sites that I upgraded to 5.3 and it appears that the issue is due to a conflict between the new Gutenberg editor in WordPress 5.3 and the tagDiv Composer.

I confirmed this by disabling tagDiv Composer and the issue with not being able to add / edit posts and pages went away. Needless to say that is not a solution, but I have some good news. Since the conflict is between the theme’s composer vs. gutenberg, I installed a plugin called “Disable Gutenberg” (https://wordpress.org/plugins/disable-gutenberg/) and the problem was fixed.

For what it is worth, it should not be a surprise that this happened because running multiple visual composers will break a site.

I’m restoring my sites to previous version of WordPress until this is resolved. @tagDiv team can you please let us know if you are experiencing this same issue on your end after updating to WP 5.3?

@co50 I think Calin was trying to tell you where the dpi settings were, if you would like to adjust the threshold to display retina images down to 100dpi.

Also a part of retina is set in this file -> http://prntscr.com/pt251i -> wp-content/plugins/td-composer/legacy/common/wp_booster/td_util.php and this file -> http://prntscr.com/pt25ns -> wp-content/plugins/td-composer/legacy/Newspaper/js/tagdiv_theme.js if you change the tagdiv_theme.js you’ll need to mimify the code en replace the one from tagdiv_theme.min.js

That seems to be the main cause of your issue and I would personally not consider it a “bug” – its just how they have their theme configured to keep images / page sizes optimized for faster load times.

Hi Simion,

Good news, I was able to resolve this with the plugin developer last night. I’d like to share the solution here (in case someone else has similar issue with this plugin) and get your feedback whether this solution will impact anything else on the site.

First to answer your questions, the plugin (Job Board Manager) creates a post for each job. So adding a job is similar to adding a post but with custom fields.

The solution was to comment out line 75 and 76 in the td-composer/legacy/newspaper/footer.php file via the plugin editor and add the following two lines in its place (thank you Nur from Job Board Manager).

$post_content = do_shortcode($footer_page->post_content);
$content = str_replace( ']]>', ']]>', $post_content );

Please let me know if you think this will cause any issues elsewhere – so far the site is working great.

Shaun

Thank you Vlad. I found the action hook in the footer.php that is pulling in the job description in place of the footer do_action('tdc_footer') but when I comment this out it breaks the footer.

What I don’t understand is why this Job plugin will work if I use one of the standard footer options, but when I use a custom footer, it breaks – resulting in the job post appearing twice on the page, replacing the custom footer. Here is a link to a job post so you can see what I’m talking about: https://mp.adcreview.com/job/process-development-engineer-associate-experience-will-dictate-exact-title/

Is there a way to call the custom footer, similar to how you call the standard footer templates that could resolve this?

Thank you Calin!

Please disregard, found the issue was being caused by plugin.

Correction, its also not working on Safari.

I’ve tried adding both versions of the code to the function.php file and it is still not working. Could there be any other files in the theme that would override the function.php file settings for number of columns?

• This reply was modified 6 years by smehr1.

Just wanted to share how I resolve this issue with the Column Text not working, even in Firefox. The issue we were having was being caused by our CDN, Cloudflare. When we reinstalled Cloudflare, it activated a setting under “Speed” tab called “Rocket Loader”. Once this was turned off, everything worked perfectly.

Figured it out. Here is the code I ended up using in the Advanced CSS settings for desktop: .woocommerce ul.products li.product a img{
width: 200px;
}
Here is CSS for both tablet modes: .woocommerce ul.products li.product a img{
width: 75%;
}

If there is a better way to do this, please advise – no expert at css :o)