Hi,

We already checked that. The error log showed that tagdiv did something that took down our site, and we’d like to know what that was. We have paid for support for this product and would like to speak to someone technical about this.

Hello,

We found the issue. It was a conflict between newspaper 11.4/Tagdiv and Loginpress Pro. Removing loginpress pro fixed the issue and tagdiv now loads.

I have tried that but tagdiv still does not work. I have looked through the articles provided but nothing in them helps. Tagdiv still does not load. There is no error message either, just a gray screen. How we get it to work?

Hello!

We have already tried manual update of theme but there is no success for these issues.

kindly check the URL and help for resolving this issue http://websitedesignerwestchester.com/

Hello Anamaria,

I have updated the WordPress, Newspaper Theme and all plugins to the latest version but still, I am not able to edit my post and pages with TagDiv Composer.

https://prnt.sc/ysr896

https://drive.google.com/file/d/1K8Lb6NQNScpXFOexBy5Sky8NuhxsnV72/view

I request you to please guide me on this issue so that we can use the TagDiv Composer.

Thanks!

• This reply was modified 5 years by shelmes@liebertpub.com.

Hello Calin,
Thanks for your response. let me try with your above instructions and get back you.

Thanks

It just displays the thumbnail image of the video on the page as the background for the row, it does not play the video.

Yeah I did that and it does not work.

@Calin,

Thanks, we have resolved the previous issue, but we have another issue with the site.

The main navigation menu sub-items just spin and don’t load when both the mobile theme plugin + amp plugin are active.

You can see what I mean here: https://nimb.ws/kKpdsR

Here’s what the ajax request for fetching category content returns:

https://nimb.ws/gmnFxz

I’ve investigated a bit on this issue before and I found that its because of this line in – td-composer\legacy\common\common.php file:

if ( ! td_util::is_mobile_theme() ) {
	td_api_autoload::add('td_more_article_box', TDC_PATH . '/legacy/common/wp_booster/td_more_article_box.php');
	add_action('wp_footer', array('td_more_article_box', 'on_wp_footer_render_box'));
}

for some reason its detecting that its viewing in mobile version and that module does not get added for ajax reqeusts.

Can you help with this issue?

ps: the site -> https://sandbox.clinicalomics.com/, passcode: tempvieweraccess123*

Thanks

• This reply was modified 7 years by shelmes@liebertpub.com.

@altpress

Yes, it’s been moved to the td-composer plugin in the 9.7.3 release

Some of the options you show in your screenshot do not show for me in the AMP plugin’s general settings. Seems you are looking at an older version of the AMP plugin. Please see screenshot here of what I see for AMP plugin settings: https://app.box.com/s/jv0cguoyo0ilb38s8dvo9hnig5e6d8a7

Also, when the tagdiv mobile theme is active, the AMP plugin’s listing in the left nav of WP-Admin does not show for me. I can only see it / access it when I disable the tagdiv mobile theme.

@uscho

Glad to hear that it was useful for someone!

I posted the piece of code on my blog

http://webdevsguide.com/blog/allow-child-theme-templates-in-tagdiv-newspaper-theme-after-9-7-version/

I am using the classic editor with newspaper theme version 9.7.2. I have the tagdiv mobile theme active and I have the AMP plugin active and “AMP” is the selected option in the theme panel settings for the mobile theme. I do not see the toggle switch option in the classic editor to disable AMP from the homepage. Why is this? I have cleared my caches so that is not the issue.

OK cool,

BTW.

This is what I did to enable overriding the single templates in the child theme:

td_api.php file line 365, added the following code:


if((stripos($the_component['file'], td_global::$get_template_directory) !== false)) {

if (isset($child_path) && file_exists($child_path)) {
$the_component['file'] = $child_path;
}


Hope you can integrate something like that in the near future.

OK found a way by overriding your core templating engine.

I found a bug in the 9.7 version of the Newspaper theme in the “td_api.php” file:

on line: 365 -> and (stripos($the_component[‘file’], td_global::$get_template_directory) == 0)

you are checking if a stripos of a file path is == 0, which means you are testing if the string position is at 0 or it is actually “false” / if the file is inside the theme or if it’s not inside the theme, which makes the condition useless – its true in either case.

should be: !== false

Feels like this is not intended behavior.

Hi Simion,

Thanks for the reply, yes I see where they are located, could you include a special folder in the child theme to override these templates in the near future?

I meant to say “post or page” above not “post of page”.

So then what content will show on the AMP version of the post of page if no content is in the mobile editor?

So an AMP version of my pages or posts will be created if I select the “AMP” option from the mobile theme and it will use the content from my regular post editor then on the AMP pages/posts, correct? Therefore I only need to create one version of post content for each post, not a separate version of post content in the mobile editor?

But then for the AMP version that gets put out in the above option you recommended do I still need to create a version of the post in the mobile editor? That’s what I’m trying to avoid.

+1 I would like it to be by percentage too if possible, it makes more sense as not all articles are the same length so percentage can keep the pop out uniform in its behavior.

Any idea when the header builder will be fixed? I was testing it out on my newspaper theme powered site and as soon as I imported a header template and tried to add something to it (I didn’t even save it in TD composer) it would make the page I placed it on not render and would just timeout. The way I fixed the issue so I could load my original header (not the one from the cloud library header manager) was to remove the “tdc_header_template_id” custom field value from the page in the wp backend and then update the page there. It then reverts back to load the page on the front-end fine but with my site’s original (non header manager built) header.

Perfect, that is how I’d like it to work. Thank you!

Will this only hide the element on desktop on the given page that you are editing or will it hide the element on all desktop pages that the selected element is used on?