Chris027

Now it’s not deterministic. Some links work, that formerly didn’t work. But some remain not working. This really stinks.

Looking at the browser console, I see a 404 error for the link that doesn't work.

Maybe someone can decipher why some links work and others don't, based on seeing these. This one has 16 comments and doesn’t work https://audiophilestyle.com/ca/bits-and-bytes/hang-loose-convolver-stands-alone-at-the-top-with-214-update-r1449/?&do=getNewComment&d=2&id=1449 This one has 19 comments and doesn’t work https://audiophilestyle.com/ca/reviews/powered-by-shunyata-the-delta-x-and-more-r1453/?&do=getNewComment&d=2&id=1453 This has 5 comments ave works fine https://audiophilestyle.com/ca/immersive/inside-a-dolby-atmos-music-mixing-session-heavy-weighs-the-kings-avidyā-r1450/?&do=getNewComment&d=2&id=1450 This has 4 comments and works fine https://audiophilestyle.com/ca/reviews/nitch-x-schiit-pietus-maximus-review-r1451/?&do=getNewComment&d=2&id=1451 These two articles each have 6 comments. One works and the other doesn't. I give up. Doesn't work - https://audiophilestyle.com/ca/reviews/review-apos-community-gremlin-amp-geshelli-merlin-dac-stack-r1442/?&do=getNewComment&d=2&id=1442 Works - https://audiophilestyle.com/ca/reviews/minidsp-kd-1-roon-remote-control-review-r1441/?&do=getNewComment&d=2&id=1441

Update, some pages articles have an automatic link that ends in - ?&do=getNewComment&d=2&id=1456 or similar, and these links work. Somehow Pages articles links to comments are messed up on some, but not others. I believe the distinction is if the article has enough comments. One article with 14 comments works, while those with 16 and 19 do not work.

Is anyone else seeing all the Pages articles links broken after the update to 5.0.21? For example, a standard link to an article like this, works just fine - https://audiophilestyle.com/ca/reviews/powered-by-shunyata-the-delta-x-and-more-r1453/ However, for logged in users, the link automatically adds a suffix like this - ?&do=findComment&comment=1354837&d=2&tab=comments It's all these links that show the error message below. This means, all logged in users can no longer click on Pages articles and get to the articles, without the error. Here is one example, which will also show the error for guests, but the link is only generated for logged in users. https://audiophilestyle.com/ca/reviews/powered-by-shunyata-the-delta-x-and-more-r1453/?&do=findComment&comment=1354837&d=2&tab=comments Sorry! We could not locate the item you are trying to view. Error code: 2S1361C

Update: Support helped me very quickly. The waiting while one's site is down, is killing and axiety causing. Thankfully they resovled it.

Ticket sibmitted already. I was unsure if you guys dropped the update and went home, and hopefully anyone here could help. In the middle of the upgrade, I got the Cloudflare human detector. After that passed, the upgrade lost it's formatting and was just a page refreshing with all the languages it was updating and theme updates. Then I got rate limited.

When I try from a different browser that isn't logged in, I see this, followed by the rate limiting if I click Complete Upgrade. Ah, the joys of giving up complete control of everything, to be on IC Cloud. 😡

Getting all three messages at once.

Updated and got rate limited in the middle of it. Now my site is down. Can't even access /admin/upgrade anymore without the rate limit message.

And.... there not working again. Seems intermittent.

This is a reason to upgrade in my opinion :~)

And, now they are working again :~)

A huge benefit of Cloudflare is the company's ability to also attempt to mitigate this. "Cloudflare has deployed default web application firewall (WAF) protections for newly disclosed PHP vulnerabilities before public disclosure. The rules use request and response signals to stop exploit attempts and prevent exposed data from reaching attackers." Cloudflare BlogCloudflare deploys protections against php2shell vulnerab...Cloudflare has deployed default web application firewall (WAF) protections for newly disclosed PHP vulnerabilities before public disclosure. The rules use request and response signals to stop exploit

hi Guys, this morning mentions using @ username aren't working. I tried on Safari for macOS and Safari on iOS, and Chrome on macOS. When I type the @ symbol, then start typing a name I know should work, nothing pops up. As if it doesn't recognize I'm trying to bring up a list of users from which to select. I see it's working for this support forum, but not my site. Any idea what's going on for my install?