Recent content by RippC

yeah, that's it. I created a user with ICO as the last 3 chars, same effect. 🤔 And yep, escaping that . with \ did the trick. Thanks for the -T pointer, wouldn't have found it unless I had to peruse that. Kept glossing over it in my editor lol. Thanks again.

scouring through that I noticed this: # First attempt to serve request as file, then # as directory, then fall back to displaying a 404. if ($request_uri ~* ".(ico|css|js|gif|jpe?g|png)$") { expires 30d; access_log off; add_header Pragma...

Just tried with the default XF style, same thing. the URL's look identical in both cases /conversations/add?to=username I can go there from one user profile and it works great, these couple of users I've found (and now I can't find the second one again :P) no dice. The juicy part of my...

noticed you're from TH, this is using UIX 2 also... if it matters.

there's the thing, its just the default nginx 404 page, not the soft 404 page from XF.

Just found this problem this morning, and I'm at a loss as to its cause. I found a couple of users, for which the "start conversation" link (/conversations/add?to=username) results in a hard 404 error. Other usernames work just fine. I can't seem to find a pattern in the usernames (granted I...

le bump. add another vote for this "unnecessary feature." I've been using XF for years and only just realized this was the behavior of the feed. 😡

Up until this happened I haven't had an issue with it. shrug I dunno what changed.

OK, Ezoic's caching is OFF and so far so good. Why the #$^&@#$ that didn't manifest itself the myriad of other times I configured it this way I have no idea. So... We'll see. Turning the CF Browser cache setting back up to 1mo and see what happens. Letting Ezoic know that something isn't...

OK. all sorts of weirdness and stale cache crap that wouldn't go away, but I have it working again now with CF cache on, ezoic cache OFF, and Argo OFF. I'm going to leave it alone for 30 more minutes and see what breaks next. This is madness.

Alrighty then. So I went thru yet again, turned off ALL the caching from ezoic (purged and off), cloudflare (purged and dev mode), turned off Argo, made sure all my addons were in order and old directories removed, rebuilt the site master data.... changed CF's browser cache timeout to 30...

<insert facepalm> Turns out I was still using the old KL user improvments addon. At some point, maybe I missed the memo, but TH took this over(?) ... I upgraded the TH version to the latest, purged some caches, waited a bit and now its working again. So, yeah. :rolleyes:🤔🤪 WRONG. It...

still trying to figure this one out.... not sure if bumping is allowed but I'm about ready to put my head thru the wall. Pretty much ruled out cloudflare and argo. Still trying to figure out if one of the myriad of JS's ezoic loads up is somehow intercepting that click and sending it to...

OK so its probably not CF. I went through and switched off both ezoic and CF, with no change. But if I disable javascript on the page, it still doesn't work right (throws the "cookies required" message) but I don't get the server request from a random AWS IP. So it has to be a javascript...

!#&%!#$%^#$!& I have a suspicion Argo is the culprit. Found another post on CF's forum from a wordpress user with similar ajax/400 issues. Too bad too bc it was really improving the performance of the site... Not turning it off just yet though. Going to see if there's a way around it.