MickEMT

I just noticed that on the cache pages, I no longer see the distance from my home coords to the cache.

I have the same issue, Windows Vista with Firefox. This looks like something that was changed since the update.

I've posted some SBA logs when there was a clear violation of the guidelines, Property Owner complains, Cache is past a sign marked "Danger Explosives" ( saw the sign on my way to a dry spot with the cache so I could sign it, and nope, it didn't go back). If it's a gray area, I'll post a comment in my log.

I work in a cubicle... Chain yourself to his cubicle and bring donuts? And not offer to share? But who supplies the coffee? Jeremy!

I work in a cubicle... Chain yourself to his cubicle and bring donuts? And not offer to share?

Thanks for the repeat - I did in fact miss your original post! Assuming you are talking about http://www.geocaching.com/calendar/, I am unable to repro. For example, I'll go back to November, click on the 7th, and get a proper list of events that were held on that date beginning with "HHE2009 -- Oorlog en Vrede by IJskimo (GC1X2P2)". Do you continue to see internal server errors with these steps? If not, do you know specifically what steps you took to get the errors? Thanks! Hi Moun10Bike. I should have mentioned which calendar. I was referring to the small one located in the upper right on the Your Geocaching Details page. It seems to work when you view a day less than a month old but beyond a month, it returns the 500 error. Editing to add that the event calendar mentioned in your post works correctly. Actually I cant access even December 31, 2009 on that calendar. Might be a stupid question, but did you have any logs for that date?

OK, looks like this thread has come to this point........

I disagree. The site constantly does updates. I only remember two having such a big impact, this being one of the two. I don't even remember the issues on the other one. Most go smoothly with some minor issues and I would bet they figured this one would too. Let's boil it down. The biggest problems now seem to be white space and HTML issues. They said that they are going to address the white space issue. This whole protest topic basically revolves around the HTML issue. The HTML issue is not reversible since it fixes a security leak with HTML Tidy, so you are going to have to adjust. The adjustment isn't that difficult. Are you going to advocate leaving the site open to hackers? Isn't the better solution to just make an adjustment if your cache page has an HTML issue? This update was a major update. Small updates, no biggie. This one was a larger one that, from reading, had a lot of thought put into it. But it was still foolish to think that it would go smoothly. Your second paragraph has nothing to do with my comment. I never implied that security fixes shouldn't be implimented. To imply otherwise is stating falsehood. Ohkayyyyyy, so TPTB should take the time to notify everyone and give them time to prepare BEFORE they fix a security issue?? How long would you suggest that they give as notice, a wekk, amonth, hey better yet, 6 months, that way they can tell us the site isn't secure every week, but still make sure that everyone has the time to clean up their bad coding....... You should come to NY and run for public office..........................

I was able to reproduce the error as well using the latest version of Firefox. I thought he was talking about the event calendar as well. It does appear to be a "time out" issue. I hope it helps to have another user check, if not let me know.

Yes, few members use the forums, that said, I know of a number of cachers who don't use the forums because they percieve the forums as a place where a vocal minority "bitch and moan and don't do anything constructive" Anytime a change is made to a website there will be those who dislike the changes. It could be that they lost some favorite function, they don't like the new layout, they don't like the new color etc, etc, etc,. From a functional standpoint, I've only seen a couple "bugs", and those are being addressed. If you put bad coords on your cache page would that be GC's fault? If you placed a cache too close to an existing one and it is denied, is that the fault of TPTB?? No, and I seriously doubt that anyone on the forums would argue that. Yet when someone puts bad HTML coding on their cache page, suddenly it's GC's "fault" that their updated site "breaks" it?? It thought that was funny at first, but now, it's just pathetic. So in protest, people want us to disable our caches, that's kind of funny in some ways. Those that support the idea want to spread the word via the forums, which some of the proponents admit "very few" cachers use. So what's the backup plan to spread the word, smoke signals???? As for temporarlily archiving your caches in protest, want to bet your local approver fails to see that as funny? Of course, if, while archived, someone hides a cache in that area, well, too bad, so sad, can't unarchive it, there's a new active cache nearby. What will you do, have ANOTHER protest over TPTB being "unfair"? Not logging in to the site for a week. Gee, less traffic for a week, less expense. Might make some sense if the site was a "pay as you go" where you paid per view. Go ahead, stay off for a week, more bandwidth for the rest of us! Moving your caches to another site, OK, name one that gives you all the features that GC does. Name one where the site works as well as this one.

Not your bad at all. The people bickering in this topic need to get out of this topic. Post factual information regarding bugs or don't post at all please. Take the bickering to email or private messages. Keeping this to the facts will help the developers and the general community as they read this topic to see if their problem has been reported. Thanks, if it helps any, the "ignore before" date on my field notes page is correct.

Seems like a pretty lame protest in my opinion. Why not archive and remove all your caches and quit playing. THAT would make Groundspeak take notice! Then they wouldn't have anything to come in and complain about.

Never mind, this IS the appropriate thread. My bad......... I know Opinion Nate does watch the thread, I'm sure he or one of the other Lackeys will see this and check the issue. Silly question, but what browser are you using, and have you tried clearing your cache (on the browser) and reloading the page?

Just upload a new set of field notes, next time the date/time should be for the last log in the uploaded field notes. No it does not change! It always says Ignore logs before 1/1/0001 6:00:00 AM after I have browsed to my field notes file to upload! Ok that's a bug, and I'll post it in the appropriate thread.

Opinion Nate has stated that they will be addressing that issue.

It would be a nice site feature if we could search by the D&T ratings

I don't know. But I doubt that they will revert the site design because a tiny percentage of cache pages have dirty HTML code causing the page to display incorrectly. Nothing dirty. I have good "clean" HTML on my pages and no issues since the change. I know of a few people who have looked at YOUR code and have said it's got some problems, I looked myself and saw the same problems. You want to complain about GC's "flawed" coding that won't let your flawed coding work the way you want it to?? Sorry, I can't support that. If you had spent the same amount of time and effort cleaning up the code on your pages that you have spent on this thread, you would probably have at least a good start on having your pages render properly.

OK, now that's a flaw!

Is it Groundspeak's responsibility now to account for problems with cache owner's poorly formed HTML? I'll be the first to admit that I'm not the best at coding for HTML, but I went to the trouble of asking a friend who IS really good at it what programs would help me create some good (working) HTML. There are a lot of good, freeware programs out there. I have a couple cache pages that are HTML "heavy", and with the new system, not one has a problem, heck one actually looks better. Yes, I understand that having to redo the coding for your cache pages is a P.I.T.A., but that's why I wanted it to be right the first time on mine. GOF said your protest is about as effective as glaring at the back of Signal's head, I think he's giving the protest too much credit. The only people you "hurt" will be your fellow cachers, and anyone that knows that you are just setting them inactive for a week as a protest may just go and find and log them anyway. Yes, you can email TPTB with your concerns, and a well written, reasoned email may well be noticed, but if the issue is your coding, I don't see that they are at all likely to do do anything about it. To me this is like someone coming to the forum and crying because TPTB won't approve a new hide that's in the "world's most perfect ammo can hiding spot", only to find that the OP wants to place the cache 250 feet from an existing cache. Yes, it sucks, but it's not Groundspeaks fault.

Just upload a new set of field notes, next time the date/time should be for the last log in the uploaded field notes.

Disabling your caches for a week? That's shooting yourself in the foot. Archiving 2 caches as a protest? That's shooting yourself somewhere near waist high and and centerline of the body.............. I don't mind the new look, in many ways it's an improvement.

If you are using GC google maps, you can hide your finds.

Service unavailable. I'm on Time Warner cable on the east coast if that helps narrow the issue down.

Nope, not dead by a long shot.

If you are talking about the "vacation cache" issue, I think that adoption of that rule was pretty much a non starter from go.