sadams101

I've also added @DawPi's new article comment sitemap:
https://www.celiac.com/sitemap_comments.php
Unless I've missed something I believe I now have ALL content in my site mapped in agonizing detail! 😅
 

@DawPi has completed the custom sitemap application that I mentioned which handles all posts. You can see an example of it here:
https://www.celiac.com/sitemap_posts.php
but it is modeled after the existing sitemap--but this one handles just forum posts. We were not able to add a minimum word count to this application, as one person suggested, because it slowed things down and put a load on the CPU. We were, however, able to add the ability to exclude certain forums, for example my site has around 25 different forums, so I was able to exclude a general chit chat and a technical support forum that are more or less off the main topic of my site.
Whether or not this will be a benefit or liability in Google search is an open question, but I'll follow up here with any noticeable changes, positive or negative.
I believe this will have positive results, simply because we are making it easier for Google to index specific content and allow them to provide more relevant search results for any given query. Currently Google's results may send people to a topic page like this one /page/10/, and the person who searched will still have to fish on it for the specific results of their query. With all posts indexed, Google should be able to send the person directly to the content that answers their query...at least that is my hope here.
Anyone interested in this app can contact @DawPi
Here is a screenshot of the admin page:

how I solved it was to uninstall then reinstall it

There's your chance, bro...
 

I reported it...

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.

Understood, but I wonder if you could not simply create an "Experimental Settings" tab with ample warnings and detailed descriptions on each setting. I've been running your software for 15 years and still don't understand some of the stuff hidden in init.php. These settings may be helpful to more people if only they could access them.

We are looking to put out a patch fairly soon to address this concern, however as I noted in another thread the net sum of this change is that user profile photos won't import correctly until the patch is released. You shouldn't notice any other changes in behavior on the community side.

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.

We're already aware of this and working on it:) 

What setting triggers this line? It isn't in my constants.php file, and I do have the option on for "Use Redis to reduce MySQL overhead"
define( 'OUTPUT_CACHE_METHOD', 'Redis' ); // Store guest pages in Redis

Understood, but I wonder if you could not simply create an "Experimental Settings" tab with ample warnings and detailed descriptions on each setting. I've been running your software for 15 years and still don't understand some of the stuff hidden in init.php. These settings may be helpful to more people if only they could access them.

It's always fun to read through 1,400 lines of code to find hidden settings. Ever thought of making simple check boxes for these options, with the explanations, in the Admin CP? I guess I'm just old fashioned...

I understand this, but the question was why not simply make these settings available in the Admin CP? Why do I need to learn about some of these hidden (to 99% of users) settings well over 10 years after running this software?
Also, even when looking at init.php there is no clear explanation for how to implement them. For example I see no directions that tell me that I need to add this line to my constants.php to turn this feature on--I found out how to do this here. It seems like a basic setting that ought to have a check box on the same page as the other Redis settings. Does anyone disagree?
\ define( 'OUTPUT_CACHE_METHOD', 'Redis' );

I understand this, but the question was why not simply make these settings available in the Admin CP? Why do I need to learn about some of these hidden (to 99% of users) settings well over 10 years after running this software?
Also, even when looking at init.php there is no clear explanation for how to implement them. For example I see no directions that tell me that I need to add this line to my constants.php to turn this feature on--I found out how to do this here. It seems like a basic setting that ought to have a check box on the same page as the other Redis settings. Does anyone disagree?
\ define( 'OUTPUT_CACHE_METHOD', 'Redis' );

It's always fun to read through 1,400 lines of code to find hidden settings. Ever thought of making simple check boxes for these options, with the explanations, in the Admin CP? I guess I'm just old fashioned...

It's always fun to read through 1,400 lines of code to find hidden settings. Ever thought of making simple check boxes for these options, with the explanations, in the Admin CP? I guess I'm just old fashioned...

In the last few months I've noticed a sharp uptick in my spam reports from Comcast and other large email providers. When I view the spam reports, 90%+ of them contain this auto-response:
The number of these reports has been steadily increasing over time, so the risk is that my site/domain/server will be blocked from sending email to many large providers like Comcast.
What is clearly happening here is that bots are trying to post, and are inserting either random email addresses from a spam list, or simply generating fake email addresses. 
They are being reported as spam by those who receive them because they are spam...these emails were not generated by the users who are reporting them as spam, they are created by bots who are simply using their emails in an automated attempt to spam using my forum.
Due to this I've turned off the Post Before Registering feature in the admin CP, and recommend that everyone else do the same, unless they want to be blocked from sending email to large email providers.

Mine runs faster without that line...but the real question is why the line isn't being inserted when I check the box to "Use Redis to reduce MySQL overhead"?

I don't use Nginx or a cloud server, but why bother even caching it if you only cache it for 1 minute, or 30 seconds? What is the point? The cache output for guests is to reduce resources. I assume the cached pages are created, for example, when bots crawl pages, or user do. When other request a page that has been visited in the last 15 minutes, in my case, they will get a cached version. I this is set to only 1 minute, the likely hood of serving a cached page is pretty small I think.

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

In the last few months I've noticed a sharp uptick in my spam reports from Comcast and other large email providers. When I view the spam reports, 90%+ of them contain this auto-response:
The number of these reports has been steadily increasing over time, so the risk is that my site/domain/server will be blocked from sending email to many large providers like Comcast.
What is clearly happening here is that bots are trying to post, and are inserting either random email addresses from a spam list, or simply generating fake email addresses. 
They are being reported as spam by those who receive them because they are spam...these emails were not generated by the users who are reporting them as spam, they are created by bots who are simply using their emails in an automated attempt to spam using my forum.
Due to this I've turned off the Post Before Registering feature in the admin CP, and recommend that everyone else do the same, unless they want to be blocked from sending email to large email providers.

On 4.5.1, I believe you’ll be able to enable the captcha, versions before you’d have to use a plugin.
 

In the last few months I've noticed a sharp uptick in my spam reports from Comcast and other large email providers. When I view the spam reports, 90%+ of them contain this auto-response:
The number of these reports has been steadily increasing over time, so the risk is that my site/domain/server will be blocked from sending email to many large providers like Comcast.
What is clearly happening here is that bots are trying to post, and are inserting either random email addresses from a spam list, or simply generating fake email addresses. 
They are being reported as spam by those who receive them because they are spam...these emails were not generated by the users who are reporting them as spam, they are created by bots who are simply using their emails in an automated attempt to spam using my forum.
Due to this I've turned off the Post Before Registering feature in the admin CP, and recommend that everyone else do the same, unless they want to be blocked from sending email to large email providers.