"What's New" photos tab not working
|
I check my favorites frequently, but switching to or directly accessing the Photos tab doesn't work: "www.mountainproject.com is currently unable to handle this request. HTTP ERROR 500" |
|
Randomly, it is working again. |
|
I was having this problem only for the 'What's new' photos in Colorado. I drilled down and started changing the area to sub-areas to see where the trouble was. It appears that there is a glitch in Golden | Clear Creek Canyon | Tunnel 4 Roof Routes - because that sub area is listed for new photos but it doesn't seem to exist in the route database when I try to get there by normal navigation from Clear Creek... Error 500. |
|
Gregger Man wrote: Good work, I was having the same issue |
|
Thanks for flagging and doing some digging! We're looking into this. |
|
Mine also isn’t working for Poudre canyon area in Colorado as well |
|
A week later... the photos for Tunnel 4 Roof Routes, as noted above, are still not loading. They do load on the app, just not on the website. |
|
Poudre canyon is also still broken |
|
having same issue where photos tab gives 502 server error for wyoming. |
|
This has been tricky to track down, appreciate everyone's patience. |
|
The day I had posted about the photos in (Clear Creek Canyon | Tunnel 4 Roofs) being broken was one day after that sub-area was created and routes added. Is there some process for new areas that awaits a human approval and keeps a portion of the content in digital purgatory perhaps? |
|
We think we've found the issue. Without getting into details, we're "whack-a-mole-ing" a few of the photos that are causing issues, which is why some of the pages should be loading again, while also trying to address the root cause, which will take a bit longer. Please post examples if you come across them. |
|
I'll start :) Photos not loading at Catfish Corner area ( mountainproject.com/route/1…), which appears to be related to the What's New: photos page for San Diego County/North San Diego County/Mount Woodson from loading (this was flagged by a user via email). |
|
A fix went out this afternoon that should help resolve most of these. Please post examples where it seems to still be happening if you find any. Thanks. |