sadams101

Each topic in my forum that has more than one page, including topics on this forum (which is 4.6 right?), throws multiple html errors due to the page having two instances of the keys used in the pagination, which are displayed at both the top and bottom of the topic. They only way I could correct those errors was to remove this code from the forums > front > topics > topic template. You can see it here: https://validator.w3.org/nu/?doc=https%3A%2F%2Finvisioncommunity.com%2Fforums%2Ftopic%2F407405-upgrade-from-ip-34x-to-ips40-updated%2F and by the way, you've got 124 other errors and warnings on your 4.6 version, which is very bad for SEO...compare to: https://validator.w3.org/nu/?doc=https%3A%2F%2Fwww.celiac.com%2Fforums%2Ftopic%2F154714-has-anyone-gotten-covid-shots-yet%2F Do you have plans to fix these and the many other errors I see in the 4.6 software? Code removed: {{if ( \count( $topic->commentMultimodActions() ) && ( $topic->posts > 1 OR $topic->mapped('unapproved_comments') > 0 OR $topic->mapped('hidden_comments') > 0 ) ) || $pagination}} <div class="ipsBox ipsResponsive_pull ipsPadding:half ipsClearfix ipsClear ipsMargin_bottom"> {{if \count( $topic->commentMultimodActions() )}} <ul class="ipsButtonRow ipsPos_right ipsClearfix sm:ipsMargin_bottom:half"> <li> <a class="ipsJS_show" href="#elCheck_menu" id="elCheck" title='{lang="select_rows_tooltip"}' data-ipsTooltip data-ipsAutoCheck data-ipsAutoCheck-context="#elPostFeed" data-ipsMenu data-ipsMenu-activeClass="ipsButtonRow_active"> <span class="cAutoCheckIcon ipsType_medium"><i class="fa fa-square-o"></i></span> <i class="fa fa-caret-down"></i> <span class='ipsNotificationCount' data-role='autoCheckCount'>0</span> </a> <ul class="ipsMenu ipsMenu_auto ipsMenu_withStem ipsHide" id="elCheck_menu"> <li class="ipsMenu_title">{lang="select_rows"}</li> <li class="ipsMenu_item" data-ipsMenuValue="all"><a href="#">{lang="all"}</a></li> <li class="ipsMenu_item" data-ipsMenuValue="none"><a href="#">{lang="none"}</a></li> <li class="ipsMenu_sep"><hr></li> <li class="ipsMenu_item" data-ipsMenuValue="hidden"><a href="#">{lang="hidden"}</a></li> <li class="ipsMenu_item" data-ipsMenuValue="unhidden"><a href="#">{lang="unhidden"}</a></li> <li class="ipsMenu_item" data-ipsMenuValue="unapproved"><a href="#">{lang="unapproved"}</a></li> </ul> </li> </ul> {{endif}} {{if $pagination}} {$pagination|raw} {{endif}} </div> {{endif}} ERRORS: Error: Duplicate ID elPagination_0d84dfb8b6392cf011e295693b7c56a0_918124633. From line 10035, column 2; to line 10035, column 224 ↩ ↩↩↩ ↩ <ul class='ipsPagination' id='elPagination_0d84dfb8b6392cf011e295693b7c56a0_918124633' data-ipsPagin…ue' data-pages='2' data-ipsPagination data-ipsPagination-pages="2" data-ipsPagination-perPage='25'>↩ ↩ Warning: The first occurrence of ID elPagination_0d84dfb8b6392cf011e295693b7c56a0_918124633 was here. From line 1599, column 2; to line 1599, column 224 ↩↩↩ ↩ <ul class='ipsPagination' id='elPagination_0d84dfb8b6392cf011e295693b7c56a0_918124633' data-ipsPagin…ue' data-pages='2' data-ipsPagination data-ipsPagination-pages="2" data-ipsPagination-perPage='25'>↩ ↩ Error: Duplicate ID elPagination_0d84dfb8b6392cf011e295693b7c56a0_918124633_jump. From line 10051, column 6; to line 10051, column 211 mp'>↩ <a href='#' data-ipsMenu data-ipsMenu-closeOnClick='false' data-ipsMenu-appendTo='#elPagination_0d84…392cf011e295693b7c56a0_918124633' id='elPagination_0d84dfb8b6392cf011e295693b7c56a0_918124633_jump'>Page 1 Warning: The first occurrence of ID elPagination_0d84dfb8b6392cf011e295693b7c56a0_918124633_jump was here. From line 1615, column 6; to line 1615, column 211 mp'>↩ <a href='#' data-ipsMenu data-ipsMenu-closeOnClick='false' data-ipsMenu-appendTo='#elPagination_0d84…392cf011e295693b7c56a0_918124633' id='elPagination_0d84dfb8b6392cf011e295693b7c56a0_918124633_jump'>Page 1 Error: Duplicate ID elPagination_0d84dfb8b6392cf011e295693b7c56a0_918124633_jump_menu. From line 10052, column 6; to line 10052, column 131 </a>↩ <div class='ipsMenu ipsMenu_narrow ipsPadding ipsHide' id='elPagination_0d84dfb8b6392cf011e295693b7c56a0_918124633_jump_menu'>↩ Warning: The first occurrence of ID elPagination_0d84dfb8b6392cf011e295693b7c56a0_918124633_jump_menu was here. From line 1616, column 6; to line 1616, column 131 </a>↩ <div class='ipsMenu ipsMenu_narrow ipsPadding ipsHide' id='elPagination_0d84dfb8b6392cf011e295693b7c56a0_918124633_jump_menu'>↩

On at least 8 major template pages your plugin inserts this meta tag into the header: <meta http-equiv="Content-Type" content="text/html;charset=UTF-8"> The issue is that it creates many WC3 HTML errors, which is very poor for SEO. Can you please fix the plugin so it will not insert this meta tag? The following 5 errors are caused in each of these 8 templates: Error: A document must not include both a meta element with an http-equiv attribute whose value is content-type, and a meta element with a charset attribute. From line 3, column 73; to line 3, column 94 et=UTF-8"><meta charset="utf-8">↩<titl Error: Attribute http-equiv not allowed on element meta at this point. From line 231, column 9; to line 231, column 74 ↩↩<header><meta http-equiv="Content-Type" content="text/html;charset=UTF-8"><div c Attributes for element meta: Global attributes name — Metadata name http-equiv — Pragma directive content — Value of the element charset — Character encoding declaration Error: Element meta is missing one or more of the following attributes: itemprop, property. From line 231, column 9; to line 231, column 74 ↩↩<header><meta http-equiv="Content-Type" content="text/html;charset=UTF-8"><div c Attributes for element meta: Global attributes name — Metadata name http-equiv — Pragma directive content — Value of the element charset — Character encoding declaration Error: A document must not include both a meta element with an http-equiv attribute whose value is content-type, and a meta element with a charset attribute. From line 231, column 9; to line 231, column 74 ↩↩<header><meta http-equiv="Content-Type" content="text/html;charset=UTF-8"><div c Error: A document must not include more than one meta element with a http-equiv attribute whose value is content-type. From line 231, column 9; to line 231, column 74 ↩↩<header><meta http-equiv="Content-Type" content="text/html;charset=UTF-8"><div c

I think I figured this out...the message is showing below the topic...not sure if I moved it there, or the new version displays it there!

I am in the process of upgrading from 4.4.10 to 4.5.x and on my test site around 80% of my forum was archived before the upgrade. When I review the old threads after the upgrade, none of the archived ones are displaying the archived message. I assume that they are still archived, and that there is an issue with the message, but I am not sure. Anyone else have this issue after upgrading?

Yes, I am in the process of upgrading from 4.4.10 to 4.5.x and I display the sidebar in mobile. On my test site now I do see that all of the side bar blocks do not scale to 100% width, so they are not responsive. I waited this long to upgrade because I thought that such issues would be worked out by now.

I recently upgraded my site from 4.4.10 to the latest 4.5. I then tried to use Marketplace to upgrade your app from 1.0.14 to 1.0.15, however, I get this error and can upgrade. Any advice?:

@shiobi Do you have a link example you can post or PM to me? I have a ticket open on this and they would like more examples.

I reported it...

Yes, I guess before doing that my hope is to get confirmation from someone else that this is a bug.

I've not upgraded yet, but want to report a possible bug in Pages 4.4.10. If you have an article with two pages of comments, and you land directly on page two with a link like this: https://www.celiac.com/articles.html/study-shows-worrisome-gut-changes-in-seemingly-healthy-gluten-free-celiac-patients-r5315/?&page=2#comments or like this: https://www.celiac.com/articles.html/study-shows-worrisome-gut-changes-in-seemingly-healthy-gluten-free-celiac-patients-r5315/page/2/ using the pagination page 1 button, or the previous of first page buttons do not refresh the visible comments to the page 1 comments. This same issue does not affect pages when there are more than 2 pages of comments, for example the pagination works for this: https://www.celiac.com/articles.html/the-gluten-free-diet-101-a-beginners-guide-to-going-gluten-free-r1640/page/4/ Since I have so many custom plugins and and skin updates, I am just posting this to see if anyone else can verify this as a bug. I have tried turning off all plugins and used the default skin on my site, and this was a bug.

Is there any update for this?

Are we pushing this to the last minute for a reason? Action required: Mandatory changes to oEmbed functionality Action required: You need to add the oEmbed product to your app before October 23, 2020 @ 10AM PDT or your app functionality will break. There are important changes that will impact your app, Celiac.com Gluten-Free Forum. As part of Graph API v8.0, we are changing our Facebook and Instagram oEmbed endpoints and token requirements. These endpoints will be replaced with Graph API endpoints. To access these new endpoints, you will need to add the new oEmbed product in a new or existing app and generate a client or app token on Graph API v3.2 or newer. To avoid disruption to your app, you must make these updates before these changes take effect on October 23, 2020 @ 10AM PDT. You can also find a complete list of changes in the v8.0 changelog and blog post.

I just got this from Facebook. How will this impact the Facebook login? Will you have this updated in time? Do I need to do anything?

I solved this by having a plugin developed which allows the built in Question and Answer challenge work with, or separately from Google's Captcha. So you can make certain groups have to answer custom questions before posting. Using these questions does not slow down things at all, and also prevents Google from loading tons of junk and spying on your visitors (yes, this form loading pulls in many dubious scripts, which is why it slows things down). Anyone interested the plugin is called (DP44) Combine Antispam System by @DawPi

Unfortunately this is not an option for me, because of the huge speed issues reCaptcha causes. Notice below and it causes a 20% slowdown on any page that uses reCaptcha. Here is a speed test on an article page from my site with Captcha OFF: And here is the same page with Captcha ON: