sadams101

@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 c

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 req

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:

For months now I've seen a growing number of contact us messages like the one below. Notice the unique codes used. I suspect that what is going on is that hackers are probing to see if they can manipulate the forum to send spam, thus the unique identifiers they are including in the content. I recently patched my forum with the latest update that included an update intended to stop spam from being sent via the share article feature. I guess I am wondering if they could be using the contact us form to be sending spam? I'd like to hear from others who have been seeing similar contact us mess

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 tho

I had @DawPi design a plugin that does exactly this, and it also handles forum posts that have been archived. So if you have archived posts, rather than all links to those old posts being gone and no longer available from the poster's profile, there is an "Archives" tab that includes links to all archived posts. Here is how that looks: https://www.celiac.com/profile/2-scott-adams/

I am currently getting this error code when I try to login using Google. It was working for years, then google login stopped working at some point. I've gone through the setup instructions in detail, have tried generating a new token, but nothing seems to work. Any ideas? Sorry, there is a problem The page you requested does not exist Error code: 1S160/2

Some speed issues I've pointed out at more than 2 years ago, both on this forum and in support tickets, are still present. This is why I've gone off on my own path and have worked with people who have overcome most of them. I was a solid 80 on mobile before this new update. This new JS requirement will be harder to deal with, but I'm working with a programmer now to see what can be done. If I find anything out I'll post it here.

I just got this notification from Google: