sadams101

I was investigating some strange log entries, and may have found a bug. Here is an example of the log entry with the domain in URL changed because I don't want bots hitting it: The log entry was triggered by a guest (Guests) Sunday at 06:03 AM The URL of page the error occurred on was https://www.myURL.com/pastleaders/?sortdirection=desc TypeError: Cannot assign string to property IPS\Dispatcher\_Front::$currentPage of type ?int (0) #0 /home/celiac/public_html/system/Dispatcher/Dispatcher.php(110): IPS\Dispatcher\_Front->init() #1 /home/celiac/public_html/index.php(13): IPS\_Dispatcher::i() #2 {main} BACKTRACE: #0 /home/myURL/public_html/init.php(1049): IPS\_Log::log('TypeError: Cann...', 'uncaught_except...') #1 [internal function]: IPS\IPS::exceptionHandler(Object(TypeError)) #2 {main} This led me to do some testing on this page, and I was unable to click on Page 2, or Page 3 and get the results to change, and I see that your site has the same issue (after going there just try clicking on the different pages of past leaders, and they results don't change): https://invisioncommunity.com/pastleaders/ Perhaps the "sortdirection" in the example link in the error is something that has been discontinued, but even the Jump To Page function does not work, and there is no way to display any older past leaders than those that appear on the initial page.

Since this is still an issue in the latest version, I am circling back to see if this is slated for a future update?

I am on the latest release 4.7.17, and only mentioned that upgrade as the point where I first noticed sitemap resource issues from my server. Please double check your sitemap code changes in that update. I suspect there is an issue.

No, it's been running for years and never had issues. I will say that my I still suspect what I mentioned in my original post in this thread--my upgrade from 4.7.13 to 4.7.14 which included new sitemap coding. I believe the extra resources needed to run the sitemap now are somehow causing the issue when the archive cron runs, and this likely only affects sites with a larger number of posts & threads.

This issue continues to happen on my board, and below are my long query logs for over 10 seconds. There seems to be two long queries that are logged, and the one I suspect to be the issue is archive cron job, which archives all of my >5 years old posts. As you can see, this archiving function seems to sometimes take 20-50 seconds. Any insights here as to what could be going on?

Any news on this? It was fixed, but the issue is now back.

I got this warning as well, do we need to do anything? I do use google maps, and I also don't see anything on my site that calls polyfill.io.

I'm not sure how that would impact a busy server like mine...as I understand it could be fairly taxing in size and might cause performance issues, but I will look into this more.

After manually running this today...as mentioned if fails about once per day now and needs to be manually run, I saw this, which I've never seen before:

After the recent update this issue seems to be back, I'm not sure why: https://pagespeed.web.dev/analysis/https-www-celiac-com-forums-topic-158184-link-between-celiac-and-globulin-or-eosinophils/ky0j56ggps?form_factor=mobile

I'm the server admin, and so far I've traced this to the update mentioned in this thread. Nothing on my server as far as hardware has changed, and the server is running a low server load with plenty of extra memory, disk storage, etc.

I just want to amend this thread by adding that recently, on a nearly daily basis, the sitemapgenerator task has been "freezing up" and not completing. I am not wanting to create a ticket for this issue, but want to see if anyone else is having this issue. Sometimes the "Run Now" will work, but other times I need to go into the Task Manager area and stop the task, then run it. I've tried rebuilding the sitemap a few times, but the issue keeps happening, at least 3-5 times a week now. I suspect (but can't prove) that the changes in the code that you made to the sitemap is causing both issues mentioned in this thread--the excessive resource usage (which I believe is triggered by this task), and now task failing, and sometimes getting stuck running for 8+ hours.

I just want to mention that since I have fixed all other SEO issues in on my site that were found in Google's PageSpeed Insights, the issue I brought up in this thread regarding the Links that are not crawlable is bringing my SEO score down by 8 points--so I score 92 instead of 100 (other similar pages on my site without these type of uncrawlable links score 100). This is a significant hit by Google, and it's clear that they don't like these uncrawlable links at all, and as will all things Google, this negative score could grow over time. My hope is that your team will look into a better solution that will not cause us all to be penalized, as I think there is likely a simple solution for this (perhaps the one that @SeNioR- posted here?).

@Jim M, Google is definitely deducting points for this issue, the question is how many. It would not be listed as an error there if there were no deductions for it. It would be great if this simple fix could be included in the next update. @SeNioR-, thanks for this. My experience with the modifying the IPB JS is that the changes won't stick, so this really needs to applied in an IPB update, is that correct?

Can you please look into a fix for this issue, which affects both Mobile and Desktop versions of any forum post that includes a quote (this happens on nearly every thread in my forum). Example URL: https://www.celiac.com/forums/topic/158184-link-between-celiac-and-globulin-or-eosinophils/ View Issue on PageSpeed Insights: https://pagespeed.web.dev/analysis/https-www-celiac-com-forums-topic-158184-link-between-celiac-and-globulin-or-eosinophils/do1q1usgq0?form_factor=mobile Error: Links are not crawlable Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable