Hi Anamaria. Thanks for this … we’ll check it out and let you know!

Seriously? Creating two completely separate templates seems crazy.

First, how do you even conditionalize it so that a post would use one template if the created / modified dates are the same, and a completely different template if the created / modified dates are different? You can’t within TagDiv.

Second, that is completely inefficient especially on sites where you may have 4, 5 or more different post templates for different kinds of content or display formats. You’re saying that a publication should DOUBLE the number of templates just because the Single Post Modified Date field isn’t smart?

What should happen is that the Single Post Modified Date field should NATIVELY be conditional and only show if the modified date does not match the created date. Even better, there should be a toggle in the Single Post Modified Date element: “Show only when different from create date” If checked it would only show if they are different. If not checked it would always show.

Thx, Anamaria. That fixed the issue. I appreciate the help.

Thank you so much! Works perfect.

Hi Bettina. As requested, I just emailed contact@tagdiv.com the login info for the Arlington Magazine staging site.

You’re awesome, Bettina. Thank you! And please let me know if you need any additional info or access to help troubleshoot this. Cheers!

Hi Bettina. More info on the flex loop filters, but with a different site this time … Arlington Magazine. Here is a video that shows the issue:

https://www.loom.com/share/0b4a0a32247a4bc3b6975e0ddd1499b2?sid=0e4b16be-d9d5-40b6-9652-191ff263300b

Please note that the URL in question right now is https://staging.arlingtonmagazine.com/listings/top-doctors/, but we are launching the site live today so the URL will be https://www.arlingtonmagazine.com/listings/top-doctors/ after we launch.

The flex loop filter element is “preselecting” the first value … Addiction Medicine. The filter hasn’t actually been applied yet, but it’s displaying the first value. Instead, it should be displaying — Select Category — … you’ll see this behavior in the video.

This seems to only happen when the filter is a category … when the URL needs to change to the proper category slug. It doesn’t seem to happen when the filter is a tag because in that case TagDiv handles the filter as URL parameters.

Anyway, please check the video. We’re going to launch this today with the dropdown so that your team can look at it. But we’ll need to change it back to the buttons soon because of this bug.

BTW, the buttons aren’t really an option because this list has a LOT of categories that make it too long for mobile. We really need to display this filter as a dropdown as soon as the bug is fixed.

Thanks and have a great day!

–Eric

Bettina,
The Clear all filters button is already there. I just emailed contact@ as you requested. Thank you.

Hey Bettina,
I have temporarily lifted our block on international traffic. You should be able to view those links now.

We have tried the Multi option and have saved and resaved many times with no luck on it actually filtering.

1.) We are using a custom post type, and it appears when you enable hide empty terms it just doesn’t show any posts, even though they are all in the custom taxonomy we are filtering by. Are you testing with a custom post type and a custom taxonomy?

I can confirm when using standard posts, and default category and tags, the filtering works as you mentioned. But is does NOT work when you utilize a custom post type and custom taxonomies

I too have the same issue on a couple of sites. Our issue is specifically with Block 17. All other blocks work, but Block 17 throws

[28-May-2024 16:01:38] WARNING: [pool www] child 24552 said into stderr: "NOTICE: PHP message: PHP Fatal error: Uncaught TypeError: array_filter(): Argument #1 ($array) must be of type array, bool given in /var/www/x.com/wp-content/plugins/td-cloud-library/state/single/tdb_state_single.php:959"

[28-May-2024 16:01:38] WARNING: [pool www] child 24552 said into stderr: "Stack trace:"
[28-May-2024 16:01:38] WARNING: [pool www] child 24552 said into stderr: "#0 /var/www/x.com/wp-content/plugins/td-cloud-library/state/single/tdb_state_single.php(959): array_filter(false, Object(Closure))"
[28-May-2024 16:01:38] WARNING: [pool www] child 24552 said into stderr: "#1 /var/www/x.com/wp-content/plugins/td-cloud-library/shortcodes/single/tdb_single_categories.php(328): tdb_state_single->{closure}(Array)"
[28-May-2024 16:01:38] WARNING: [pool www] child 24552 said into stderr: "#2 /var/www/x.com/wp-content/plugins/td-cloud-library/shortcodes/single/tdb_single_categories.php(328): Closure->__invoke(Array)"
[28-May-2024 16:01:38] WARNING: [pool www] child 24552 said into stderr: "#3 /var/www/x.com/wp-content/plugins/td-composer/legacy/common/wp_booster/td_global_blocks.php(27): tdb_single_categories->render(Array, '')"
[28-May-2024 16:01:38] WARNING: [pool www] child 24552 said into stderr: "#4 /var/www/x.com/wp-includes/shortcodes.php(433): td_global_blocks::proxy_function(Array, '', 'tdb_single_cate...')"


Bettina,
Does that mean you will be getting back to us with a solution on how to fix the clicking going to incorrect locations?

Thanks for the clarification. It would be nice to have that as a feature for the infinite scroll.

In the meantime we have run into another issue with the infinite scroll with articles that have internal links. Please see the video below, what is happening is when you get to an article by continuous scrolling that contains internal links, they do not always go to the correct place.

[video src="https://s3.amazonaws.com/pramadillo/pramadillo-2024-02-06-12-22-11.mp4" /]

You can test this yourself by going to https://delawaretoday.com/partner/delaware-breast-cancer-coalition-january-2024/ and then scrolling to the next article of Faces of Delaware and then clicking on The Face of Upscale Resale you will see that article does not load correctly.

Hi Bettina. So, the continuous scroll functionality appears to be a site-wide setting, not something that can be changed category by category even when using different post cloud templates.

https://ibb.co/wyfGPQQ

What I’m trying to do is have every post in my “Sponsored Content” category NOT be continuous scroll, but have every post in my “Industry News” category be continuous scroll.

I’m not talking about continuous scroll on the CATEGORY pages, but continuous scroll at the POST level.

It does not appear that we can turn post continuous scroll off at the post level category-by-category, only sitewide. Is that correct?

Ah, wait … perhaps I didn’t make myself clear. I want continuous scroll on the POST template, but only for specific categories. In other categories, we do NOT want continuous scroll for the posts. Is that possible?

Thanks, Calin. We use cloud templates, so we’ll use your second method outlined above. I appreciate the help.

Got it. Thanks for the clarification. Cheers!

Hi Anamaria. Thanks for getting back to me so quickly.

If I understand this properly, it sounds like TagDiv does not support cloud templates for custom taxonomies on WordPress posts? What you suggest requires a complete restructure of our data which translates into thousands of dollars of development time.

Are there any plans to add support for custom post taxonomies? Or any way we can help convince your developers to add this support? 🙂

🙂 Looks like we both figured it out at the same time. Thanks for sticking with me, Bettina. I appreciate it! This is working now.

OK … through a ton of testing, I figured out the solution on my own.

The tagDiv Mobile Theme does NOT support when the AMP plugin paired URL structure is set to use a path suffix of /amp/

https://snipboard.io/hFtCXc.jpg

I used this because Hudson Valley Magazine uses that paired URL structure on its site that we’re replacing.

However, when I switched the AMP plugin paired URL structure to use a query parameter … either the standard ?amp=1 or the legacy ?amp … then the mobile theme finally worked properly.

https://staging.hvmag.com/things-to-do/this-week/?amp=1

I’m guessing that your mobile them plugin doesn’t recognize the /amp/ suffix paired URL structure and instead looks for the ?amp parameter in order to properly display the mobile theme on AMP pages.

This is something you need to update in your AMP / mobile theme documentation. And I am very surprised that no one there caught this given that I actually put our AMP paired URL settings in both my original video and as a link in my 2nd post in this thread.

• This reply was modified 3 years by nearview.

Hi Bettina. I am really trying to not get frustrated, but it’s like you’re not even reading what I’m writing. Did you see my screenshots above? Did you see how I showed our AMP plugin settings and that we’re using the /amp/ setting for the AMP plugin? Are you all even looking at the information and screenshots that I took a TON of time to document? Or are you all just throwing out generic responses without even trying to understand the information I’m providing?

I know EXACTLY how AMP works. We’ve implemented AMP on dozens of WordPress websites and at least 15 tagDiv Newspaper sites. But this is the first time we’ve implemented AMP on a site that also uses cloud templates … and it’s NOT working the way we expect.

And you do NOT need to come from Google in order to see an AMP page. Other content aggregators such as SmartNews and NewsBreak also use AMP versions of pages. And you can navigate directly to an AMP page without having to go through Google. Here’s an AMP page on our current, old site (not a tagDiv Newspaper site):
https://hvmag.com/food/baked-by-melissa/amp/

You can see the AMP page just fine even if not coming from Google … and you can see that you don’t need to have ?amp at the end of the URL. We have the AMP plugin set up currently to use /amp/ which is just fine.

Here’s another AMP page, but on a tagDiv Newspaper site that does NOT use cloud templates:
https://biztimes.com/nine-block-450-million-redevelopment-planned-in-downtown-kenosha/?amp

You can see the AMP page just fine even if not coming from Google. This particular site does use ?amp as the setting in the AMP plugin. And it’s showing the tagDiv mobile them just fine … because the site does NOT use cloud templates.

Please … before you all respond again … take the time to actually watch the video in my first post. Then fully read my next post and look carefully at the screenshots that I included in that second post.

Thank you.

P.S. I would be willing to pay a good amount to have a Zoom meeting with you all to try to work this out. 🙂

• This reply was modified 3 years by nearview.
• This reply was modified 3 years by nearview.

You’re not reading what I wrote and it’s a bit frustrating.

We ARE using the AMP plugin and the TagDiv Mobile Theme plugin. And we have the mobile theme set to only show on AMP. Did you not see the screenshots I posted above?

The problem is that the mobile theme is NOT showing on AMP pages. Instead, AMP pages are showing the cloud templates for the normal site.

Please take the time to read what I have posted and look at the screenshots.

Hi Calin. Not sure if you watched my video or not. I am very familiar with the mobile theme plugin and options with AMP. I have used it on dozens of TagDiv Newspaper sites just fine. We only ever use the mobile theme for AMP … and we only ever use it for posts.

The problem is that posts that use cloud templates seem to ignore all the AMP settings (header, post template, footer). We don’t want that. We want the AMP version of posts to only show the usual mobile theme as configured for AMP.

In the AMP plugin, we have the following settings:
https://snipboard.io/I7N5Tm.jpg
https://snipboard.io/hFtCXc.jpg
https://snipboard.io/591vgk.jpg

Here is how we have the mobile theme / AMP configured in the Newspaper theme panel …
https://snipboard.io/dzHUZT.jpg

And here are the Newspaper mobile theme header settings …
https://snipboard.io/vsxzNl.jpg

Here’s what a post looks like on mobile using cloud templates (not AMP) …
https://snipboard.io/8EhYnw.jpg

And here’s that same post with AMP …
https://snipboard.io/4MjoNQ.jpg

Notice how the header is NOT the AMP header from the mobile theme? And the body isn’t from the mobile theme either … it’s from the mobile responsive post cloud template.

You can see that we’ve implemented AMP posts just fine before. Here is an example from another TagDiv Newspaper site … but it does NOT use cloud templates.

Normal mobile responsive post …
https://snipboard.io/56YDyw.jpg

And here’s the AMP version of the same post …
https://snipboard.io/ut1ATm.jpg

So again, the challenge seems to be implementing the mobile theme for AMP only and on posts only … but on a site that uses cloud templates for it’s normal pages.

What are we doing wrong? Or is this even possible? Thanks again!

• This reply was modified 3 years by nearview.
• This reply was modified 3 years by nearview.

Thx, Anamaria. We also discovered that there is some CSS that was impacting the embedded block. All is working well now. I appreciate your help!

Hi Anamaria. Sorry that I haven’t replied sooner … not sure why I’m not getting email updates on this thread, but I’ll look into that. 🙂

Here is the code … thanks again for the help!

[td_flex_block_1 modules_on_row="" limit="1" hide_audio="yes" category_id="1362" image_floated="eyJhbGwiOiJmbG9hdF9yaWdodCIsInBvcnRyYWl0IjoiaGlkZGVuIiwicGhvbmUiOiJoaWRkZW4iLCJsYW5kc2NhcGUiOiJmbG9hdF9yaWdodCJ9" custom_title="LBM Resources" block_template_id="td_block_template_2" tdc_css="eyJhbGwiOnsiYm9yZGVyLXRvcC13aWR0aCI6IjEiLCJib3JkZXItcmlnaHQtd2lkdGgiOiIxIiwiYm9yZGVyLWJvdHRvbS13aWR0aCI6IjEiLCJib3JkZXItbGVmdC13aWR0aCI6IjEiLCJwYWRkaW5nLXRvcCI6IjEwIiwicGFkZGluZy1yaWdodCI6IjIwIiwicGFkZGluZy1ib3R0b20iOiIyMCIsInBhZGRpbmctbGVmdCI6IjIwIiwiYm9yZGVyLWNvbG9yIjoiI2NjY2NjYyIsImJvcmRlci1yYWRpdXMiOiI0IiwiYmFja2dyb3VuZC1jb2xvciI6IiNmZmZmZmYiLCJkaXNwbGF5IjoiIn19" title_tag="div" mc1_title_tag="p" f_header_font_family="948" f_header_font_size="13" f_header_font_spacing="-0.2" f_header_font_transform="none" header_text_color="#777777" modules_gap="0" all_modules_space="0" video_popup="" autoplay_vid="" show_author="none" show_cat="none" show_date="none" show_com="none" show_review="none" show_audio="none" meta_padding="0" f_title_font_family="948" f_title_font_size="21" f_title_font_weight="700" f_title_font_line_height="1.3" f_title_font_spacing="-.2" f_ex_font_family="948" ex_txt="#000000" title_txt="#000000" title_txt_hover="var(--chained-news-blue)" f_meta_font_weight="" f_ex_font_weight="300" f_ex_font_size="15" f_btn_font_family="948" f_btn_font_size="13" f_btn_font_weight="600" btn_bg_hover="var(--chained-news-blue)" btn_bg="var(--chained-news-separator)" sort="random_posts" f_ex_font_spacing="-.2" m_padding="0 10px 0 0" image_width="25" btn_radius="4"]

What’s the point of having page templates then if you can’t assign them to specific pages?