|
|
Well, it looks like the 404 page gets cached. Deleting cache has helped.
That said, maybe the it would be possible to change the 404 page in a way so that browser is not allowed to cache it?
modified 3-Dec-20 12:46pm.
|
|
|
|
|
Linking an SO article is a good way to get your account closed.
|
|
|
|
|
I would not say closed...
maybe just ignored?
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Linking what?
|
|
|
|
|
|
Well, choosing "my articles" from the dropdown menu was the very first thing I did.
If it showed the article, I would not even mention it. But clicking those links lead to the url with 404. The only thing that really helped was hard cache reset.... Which probably means 404 page is cached while article page is not, or something like that.
That is why I find the situation confusing...
But really, all is fine now. Thank you.
|
|
|
|
|
using:
Miroslav Fidler wrote: https://www.codeproject.com/script/common/404.aspx?aspxerrorpath=/Aarticles/5268022/Getting-Started-with-Uplusplus-2020-2[^] works
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Article https://www.codeproject.com/Articles/5283291/Examples-of-Layered-Application-Architecture-Based
not found.
Error message - 404 - "Do not try and find the page. That’s impossible. Instead only try to realise the truth"
|
|
|
|
|
|
|
Be patient. I suspect the site is still recovering from yesterday's outage. It may also help if you clear your browser cache as you may just be getting the 404 page in the browser.
|
|
|
|
|
|
Every titled item in all the forums is followed by this word.
The behavior that ensues:
1. click on the word PIN
2. Icon of PIN reappears, item is "pinned".
3. Click on the icon again, item is "unpinned", icon remains as obligate "pin".
I've never had much reverence for the idea of "pinning" a post mainly because pinning has never been implemented correctly anywhere that I've seen (when a post is pinned (typically "opened" and made to remain in the "opened" state)) ... if I navigate away from that page then return, the item that was remaining open is now neither open nor pinned.
modified 1-Dec-20 12:22pm.
|
|
|
|
|
1. Do you have uBlocker or other add-ins that mess around with a site's HTML?
2. Anything in particular stopping you from upgrading FireFox to v83?
cheers
Chris Maunder
|
|
|
|
|
I think I have found the problem ...
The "pin" icon (which turns out to be a low-viz rendition of the colored "pinned" icon and is perhaps transparent as well (arghh -> don't get me started with .png & tranparency)) is located on the server at:
"https://codeproject.freetls.fastly.net/script/Forums/images/pin.png"
BUT, the icon won't load when the .HTML itself is refering to this path:
"https://codeproject.freetls.fastly.net/script/Forums/Images/pin.png"
Note the capitalization of the "Images" folder.
As the page loads, that icon "img" weighs in as img (22 x 11) not 13 x 13 image pin.png and with, of course, the Developer/Inpsector tootip text of "could not load the image" because the path can't be found. Copy and paste the capital "I" image folder into the URL space and return and one gets:
Error[^]
The redirect to a CP error page called:
"https://codeproject.freetls.fastly.net/script/Common/Error.aspx"
~~~~~~~~~~~~~~~~
So, is it me? Or is it the small "i" image of the HTML that needs to be upgraded?
Anybody else seeing this hoopoe?
[EDIT]
... wow, a minute and thirty-three seconds later ... all better!
[/EDIT]
modified 1-Dec-20 19:17pm.
|
|
|
|
|
... and PIN is back (12/05/20 @ 1434 PT) ... see my idea for fix above (below?)
|
|
|
|
|
About that "... and PIN is back (12/05/20 @ 1434 PT) ... see my idea for fix above (below?)"
(that "error" ->
Ticket:
Error:
An error occurred in this page. The error has been recorded and the site administrator informed.
Abort, Retry, Fail?_
so, no actual Ticket just a prompt to DOS exit that is unactionable)
There is one thing that has changed in the past four days though. Instead of being redirected to the error page when one attempts to save the "PIN" (image/Image) one gets a direct link (same path as complained about above) and a chance to save the PIN.PNG as presumably a .png. But it's not a .png, it's an .html/.htm now.
Hope this info in some way helps and doesn't just make me out to be an arm-chair quarterback
[EDIT]
In both IE and Edge, the webpages that contain posts (I'm running TIGHT/THREADVIEW/50 on FF) with that pinning feature display no low-viz pushpin image at all when first loaded. Just a space which gets hooked by any mouse-over done just to the right of the title.
[/EDIT]
modified 6-Dec-20 13:41pm.
|
|
|
|
|
|
They're both low-viz (no color only outline of object).
When I logged in this morning, the word PIN was appearing. Then 20 minutes later the proper function was back. So perhaps you're right about the cache or ... I thought ... "maybe there are two servers and my first login occured before a second server synched in and took over the task of dishing out pages (one has image the other Image)".
But anyway, if it keeps coming back and is this silly intermittant stuff it's barely annoying so I'll just get jiggie with it. Whatevs.
Thanks Chris.
|
|
|
|
|
|
|
I can see the article, and it also notes that there is a draft to view or edit.
However, there was a major outage earlier today, please be patient. The administrators are busy trying to fix things.
|
|
|
|
|
Thanks a lot, Richard, for the clarification.
I'll be patiently waiting for the administrators to fix the things.
|
|
|
|
|
That article's been visible to be since 9:05 this morning. Can you please clear your browser cache and try again?
cheers
Chris Maunder
|
|
|
|