Server error on change of custom lists in Profile Stats

Question

Changing the custom lists in Profile Stats is ending up with server error.

Internal server error (6a7c7cbb228b95.64656846)

Internal server error (6a7c7ee9ce2269.22255894)

I set up two lists in past. One from GC codes in Hides and one from a bookmark in Milestones. Even then it was problematic, but after various attempts it worked. Now I'm trying to add one cache to the GC codes list, I don't change anything else and it doesn't work. Even if I change the list to bookmark-based.

I found a similar issue from February, which has not been closed.

Answer 1

Thank you for the report. A fix will be available on the site shortly.

Comments

There is still something wrong, but in different way. I tried to add one cache into a GC codes based custom list again today. It didn't end up with server error this time, but I submitted the stats settings form and the list was completely gone. Adding a new list, no matter if GC codes based or bookmark list based, looks ok in the process, but it's never there after submit.

---

That is strange. When you say "I submitted the stats settings", you are pressing "Save" at the bottom, yes?

Can you also tell me what the name of the list you are submitting is, as well as example GC#s? I am having trouble reproducing the issue, and maybe it is with the geocaches you are trying to add.

---

Yes, I first pressed Submit, got "Custom list added", then I pressed Save button at the bottom of the whole settings form. The page reloaded, but the custom list didn't create.

Here are the data I used:
title: "Eventy, na kterých jsem se podílel jako organizátor nebo dobrovolník"
Tab: Hides
Type: GC Codes
"GCAGG33, GCAW3WW, GCAW13C, GCAGCZE"

Using the same title but my own public bookmarklist "Spolupořádání" (Froggiewalker) has the same result.
https://www.geocaching.com/plan/lists/BMF9037

---

Lovely, thank you, I can reproduce the issue using that. I will look into this shortly.

---

A fix has been made and will be released soon. It had to do with how the server interpreted the character encoding of non-English characters (in the title). We're surprised this got past review since the majority of Project-GC staff are not English-speaking, but it did.

---

Ja, det är intressant. Thank you for a quick investigation :)