Jump to content
Sign in to follow this  
Followers 4
dreamhummie

Waymarking Site down ?

Recommended Posts

All searches give me an error message. Clicking any waymark gives an error message:

 

"An Error Has Occurred

Your request has resulted in an error. You may choose to retry your previous request. Or you may tell us what you were doing when this error occurred:"

Now the same again here. All I try gives the error message. 15.07.2015 - 14:36

Share this post


Link to post

Interesting, from the smart phone I can use the site (even review Waymarks) if I use the computer all of the errors appear.

Share this post


Link to post

<!-- Server: WAYMARK-WEB02; Build: Waymarking.Web.release-20150622.1.Release_13 -->

 

This is the one giving me fits right now. Same error message as the one Lumbricus posted. Waymarking Russian Roulette.

Share this post


Link to post

After most of the day yesterday of receiving no error messages I'm now getting the same 'Error Occurred' message that lumbricus is getting.... AAAAARRRRRRRRRRRGGGGGGGGGHHHHHHHHHHH

 

My smart phone is also working with the site.

 

With most-likely less than 10% of Groundspeak's annual revenue coming from Waymarking, I guess we know where the priorities lie....

 

:(

Share this post


Link to post

Interesting, from the smart phone I can use the site (even review Waymarks) if I use the computer all of the errors appear.

 

Actually, on my smart phone I get the same error messages. I can't navigate the site on it. Thought it might have been my wifi, so I turned it off on my phone and tried again. Same error messages. I'm using an iPhone 5s with software version 7.1.2. I would have had a more recent software update, but I have 4,000 photos of waymarks on it that takes up all my gigs.

Share this post


Link to post

Holy smokes Batman, look what I just got ....

 

 

Server Error in '/' Application.

Compilation Error

Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.

 

Compiler Error Message: BC30560: 'controls_categoryfiltercontrol_ascx' is ambiguous in the namespace 'ASP'.

 

Source Error:

 

Line 24: </asp:Content>

Line 25: <asp:Content ID="Content3" ContentPlaceHolderID="ContentRightColumn" runat="server">

Line 26: <uc2:CategoryFilterControl ID="CategoryFilterControl1" runat="server" />

Line 27: <uc1:DynamicLinksControl ID="DynamicLinksControl1" runat="server"></uc1:DynamicLinksControl>

Line 28: </asp:Content>

 

Source File: E:\inetpub\www.Waymarking.com\Waymarking.Web.release-20150622.1.Release_13\wm\search.aspx Line: 26

 

Show Detailed Compiler Output:

 

Show Complete Compilation Source:

 

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.34248

Share this post


Link to post

What the hell is all this mess? Get this when I try to opn My Waymarks...

 

Server Error in '/' Application.

 

Compilation Error

 

Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.

 

Compiler Error Message: BC30560: 'controls_categoryfiltercontrol_ascx' is ambiguous in the namespace 'ASP'.

 

Source Error:

 

Line 24: </asp:Content>

Line 25: <asp:Content ID="Content3" ContentPlaceHolderID="ContentRightColumn" runat="server">

Line 26: <uc2:CategoryFilterControl ID="CategoryFilterControl1" runat="server" />

Line 27: <uc1:DynamicLinksControl ID="DynamicLinksControl1" runat="server"></uc1:DynamicLinksControl>

Line 28: </asp:Content>

 

Source File: E:\inetpub\www.Waymarking.com\Waymarking.Web.release-20150622.1.Release_13\wm\search.aspx Line: 26

Share this post


Link to post

...

 

Compilation Error

 

Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.

 

Compiler Error Message: BC30560: 'controls_categoryfiltercontrol_ascx' is ambiguous in the namespace 'ASP'.

 

Source Error:

...

 

Source File: E:\inetpub\www.Waymarking.com\Waymarking.Web.release-20150622.1.Release_13\wm\search.aspx Line: 26

 

I got an other source. And the interesting thing is that you can inspect sources an compiler output. So might start reconstructing the website ;-).

 

This kind of info should never go outside, so it looks they are working hard to fix and are getting desperate, so loosing attention to keep safety procedures in place...

Share this post


Link to post

So how is it that the site keeps publishing new WMs when one can't even access it? And why all the secrecy from GS/WM?

 

...

 

Compilation Error

 

Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.

 

Compiler Error Message: BC30560: 'controls_categoryfiltercontrol_ascx' is ambiguous in the namespace 'ASP'.

 

Source Error:

...

 

Source File: E:\inetpub\www.Waymarking.com\Waymarking.Web.release-20150622.1.Release_13\wm\search.aspx Line: 26

 

I got an other source. And the interesting thing is that you can inspect sources an compiler output. So might start reconstructing the website ;-).

 

This kind of info should never go outside, so it looks they are working hard to fix and are getting desperate, so loosing attention to keep safety procedures in place...

Share this post


Link to post

At the moment, I can now at least list my waymarks and start working again. For how long, I don't know ...

 

Same here. It seems to be working now, hopefully for a long time. I've noticed that the site is slow (about 15-20 seconds to load a page), but that's better than the stupid error messages.

Share this post


Link to post

Still encountering the "An Error has Occurred". Still apparently routing to waymark-web02. Still unable to use the site in any meaningful way except ...

 

To download all my waymarks into a KML file as a backup in case we never make it out of these woods. (Groundspeak has become rather silent).

become? :unsure:

Share this post


Link to post

It seems to be working nicely now. Hopefully it stays up.

 

Didn't last long. Attempting to upload a photo (twice) when it crashed - Out of memory.

 

Discovered a couple of days ago that when eating hot chilli that drinking alcoholic spirits such as vodka quells the pain. Cheers.

 

Share this post


Link to post

It seems to be working nicely now. Hopefully it stays up.

 

Didn't last long. Attempting to upload a photo (twice) when it crashed - Out of memory.

 

Discovered a couple of days ago that when eating hot chilli that drinking alcoholic spirits such as vodka quells the pain. Cheers.

 

That's odd. The website is still working completely fine for me now at 6:17 PST.

Share this post


Link to post

Site worked long enough to submit three waymarks and MOST of the 4th.. trying to upload last photo and got this message... gee, didn't think my pics were THAT big :)

 

 

Server Error in '/' Application.

--------------------------------------------------------------------------------

 

Out of memory.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

 

Exception Details: System.OutOfMemoryException: Out of memory.

 

Source Error:

 

 

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

 

Stack Trace:

 

 

[OutOfMemoryException: Out of memory.]

System.Drawing.Image.FromStream(Stream stream, Boolean useEmbeddedColorManagement, Boolean validateImageData) +1139062

Tucson.Common.FileApi.ImageHelpers.ExtractDateTakenFromEXIF(HttpPostedFile& postedFile) +41

WM.UI.ImageUploadPanel.ProcessFile() +724

WM.UI.ImageUploadPanel.btnUpload_Click(Object sender, EventArgs e) +7

System.Web.UI.WebControls.Button.OnClick(EventArgs e) +9628722

System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +103

System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +10

System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +13

System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +35

System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1724

Edited by jiggs11

Share this post


Link to post

Tried uploading the photo a third time based on the saying "third time lucky" but no luck - same error as above. 16 July @ 11:35 AEST

 

Share this post


Link to post

Discovered a couple of days ago that when eating hot chilli that drinking alcoholic spirits such as vodka quells the pain. Cheers.

 

But why would you want to quell the pain? That's what the pepper is for!

 

I haven't had vodka with hot food. Beer does a good job, but the best thing is actually dairy. Or bread.

Share this post


Link to post

Tried uploading the photo a third time based on the saying "third time lucky" but no luck - same error as above. 16 July @ 11:35 AEST

 

 

It would be nice if the site automatically resized the photo *before* upload. It's pretty easy to do in javascript, and could be done completely on the client side.

Share this post


Link to post
...But why would you want to quell the pain? That's what the pepper is for!...

Exactly! :grin:

Share this post


Link to post

With the chatter about site problems dying down, I thought maybe the problems had been fixed and tried submitting a Waymark. However, when I clicked "Save and Continue" on the first step, I was given the following error:

 

Server Error in '/' Application.
The waymark was not found.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: Groundspeak.Web.Exceptions.ItemNotFoundException: The waymark was not found.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[itemNotFoundException: The waymark was not found.]
  Groundspeak.Web.Waymarking.Waymark..ctor(Guid WaymarkGUID) +266
  WM.UI.WaymarkPageBase.SetWaymark() +691
  WM.UI.WaymarkPageBase.Page_Init(Object sender, EventArgs e) +34
  System.EventHandler.Invoke(Object sender, EventArgs e) +0
  System.Web.UI.Control.OnInit(EventArgs e) +92
  System.Web.UI.Page.OnInit(EventArgs e) +12
  System.Web.UI.Control.InitRecursive(Control namingContainer) +134
  System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +489


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.34248

I give up. I'm not even going to bother trying to submit again until I hear from Groundspeak that the problem(s) has/have been identified and fixed. I'm sick of entering the same information again and again only to be blocked by a variety of error messages or broken form elements.

Share this post


Link to post

With the chatter about site problems dying down, I thought maybe the problems had been fixed and tried submitting a Waymark. However, when I clicked "Save and Continue" on the first step, I was given the following error:

 

Server Error in '/' Application.
The waymark was not found.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: Groundspeak.Web.Exceptions.ItemNotFoundException: The waymark was not found.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[itemNotFoundException: The waymark was not found.]
  Groundspeak.Web.Waymarking.Waymark..ctor(Guid WaymarkGUID) +266
  WM.UI.WaymarkPageBase.SetWaymark() +691
  WM.UI.WaymarkPageBase.Page_Init(Object sender, EventArgs e) +34
  System.EventHandler.Invoke(Object sender, EventArgs e) +0
  System.Web.UI.Control.OnInit(EventArgs e) +92
  System.Web.UI.Page.OnInit(EventArgs e) +12
  System.Web.UI.Control.InitRecursive(Control namingContainer) +134
  System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +489


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.34248

I give up. I'm not even going to bother trying to submit again until I hear from Groundspeak that the problem(s) has/have been identified and fixed. I'm sick of entering the same information again and again only to be blocked by a variety of error messages or broken form elements.

Groundspeak works on the problems. This means that there could be some more errors in the near future. But if I look in my queue it seems like the site is working again.

Share this post


Link to post

Depends on your definition of 'working'. Uploads of photos take forever - I can chop the wood, set the fire & still be waiting. Just a second ago clicked on an icon on my category grid, waited, waited then message that the website was unavailable. The ISP probably only gives X amount of time for a site to load. Groundspeak need to speak & let us know what they're doing, on a regular basis in this forum, not hidden in the caching chatter.

Share this post


Link to post

Yesterday (18 July) I was able to submit one waymark in mid-day with no issues, and then 4 more late in the day with no issues.

 

A while ago (19 July) I barely was able to save two "stub" waymarks (no photos, just placeholders so I can finish them later), with several errors whilst trying to do so.

 

Now I cannot even log in. Oh yes, I can log into that soggy paper game site, even though it's the same password and company. But I cannot login to Waymarking.

 

Is Groundspeak trying to kill Waymarking now? I guess 600,000+ waymarks isn't convincing enough?

Share this post


Link to post

I don't think that Waymarkers will like what Groundspeak has to say. I firmly believe this is the end of the Waymarking site.

 

I have been working on one waymark today, and now I can't even log back on to the site, and I did not sign out. One error after another.

Share this post


Link to post

Just before all of this trouble started I was thinking about going back to premium for this year. But if they kill Waymarking, forget it.

Share this post


Link to post

Just before all of this trouble started I was thinking about going back to premium for this year. But if they kill Waymarking, forget it.

 

I have always been a PM, and that was because it gave me added features to geocaching, namely the PQ's and access to PMO geocaches. I seldom ever run a PQ now, I can use my andriod phone and don't really have use for the PQ's anymore. So what I am paying my PM for now is to own and access PMO geocaches.

 

I have no use to renew my PM for added benefits to the Waymarking site. I'm not interested in creating any new categorys of being a officer in any groups. I will still maintain my PM, but I would like to thing that I am supporting the geocaching site so new and better features may be added, not to fix this broken and failed attempt of virtual geocaching.

Share this post


Link to post
...I don't think that Waymarkers will like what Groundspeak has to say. I firmly believe this is the end of the Waymarking site....

This is not the end of Waymarking, 'Manville Possum Hunters' please stop spreading these false speculations. I've been talking with two Lackeys this weekend for a long time and I'm in contact with Bryan and the Lackey who wrote the Waymarking code. The resources being dedicated to the Waymarking site right now are very limited, this is not new. But they really try to fix the problems as best as they can at the moment.

Share this post


Link to post

Are any of you in the Information Technology fields? I am and have been since 1980. I know whereof I speak. I have worked for AT&T, IBM, and Toshiba. Not as a contractor, but as a regular employer in those companies.

 

This is the longest server outage that I have seen in 35 years of software architecture, design, and use. Someone is trying to Do It Themselves instead of calling in someone who knows these servers and get the blasted things fixed. No large company like Walmart or IBM or Federal Express or whatever would stand for such excuses for so many weeks.

 

Enough of the excuses. Have the Groundspeak CIO call in the president of whoever sold them these Commodore-64 servers and get the blasted things fixed!!

 

Think I'm joking. Nope. It's called escalation. And it does not seem to be working right at Groundspeak.

Share this post


Link to post

Other type of problem...

click on my 'Profile' button returned

 

Server Error in '/' Application.
Compilation Error
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.

Compiler Error Message: BC30560: 'controls_profileoptionscontrol_ascx' is ambiguous in the namespace 'ASP'.

Source Error:

Line 60:         </table>
Line 61:     </asp:Panel>
Line 62:     <uc1:profileoptionscontrol id="ProfileOptionsControl1" runat="server"></uc1:profileoptionscontrol>
Line 63:     <asp:Panel ID="pnlProfile" runat="server">
Line 64:         <uc1:profilepanel id="ProfilePanel1" runat="server"></uc1:profilepanel>

[/font]

Edited by ToRo61

Share this post


Link to post

Similar error for Quick Searches -> My Waymarks

Default request works fine, but when I try apply some filter (country and Pending Review)

I received only:

 

Server Error in '/' Application.
Exception of type 'System.OutOfMemoryException' was thrown.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.]
  System.Web.Util.HttpEncoder.UrlDecode(Byte[] bytes, Int32 offset, Int32 count, Encoding encoding) +43
  System.Web.HttpValueCollection.FillFromEncodedBytes(Byte[] bytes, Encoding encoding) +122
  System.Web.HttpRequest.FillInFormCollection() +77

[HttpException (0x80004005): The URL-encoded form data is not valid.]
  System.Web.HttpRequest.FillInFormCollection() +135
  System.Web.HttpRequest.EnsureForm() +75
  System.Web.HttpRequest.get_Form() +12
  System.Web.HttpRequest.get_HasForm() +9687455
  System.Web.UI.Page.GetCollectionBasedOnMethod(Boolean dontReturnNull) +95
  System.Web.UI.Page.DeterminePostBackMode() +69
  System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +130

Edited by ToRo61

Share this post


Link to post

Thanks ToRo61 for posting these error messages so it's easier to locate the problems.

Share this post


Link to post

Source File: E:\inetpub\www.Waymarking.com\Waymarking.Web.release-20150622.1.Release_13\wm\search.aspx Line: 26

 

I have received a proof the lackeys at Groundspeak are really working on the Waymarking site.

My last error message included

E:\inetpub\www.Waymarking.com\Waymarking.Web.release-20150715.1.Release_16\users\profile.aspx Line: 62

So we have a new Waymarking release since 7/15/2015. Still not working well. But something has changed in the last days.

Good news I would say! They're working on the problems.

Share this post


Link to post

I think the majority of the frustration stems from a lack of communication from these so-called lackeys....come on folks, why all the secrecy? This sounds like the GP who wants to try "just one more cure" before finally sending a patient off to the specialist.

Share this post


Link to post

Are any of you in the Information Technology fields? I am and have been since 1980. I know whereof I speak. I have worked for AT&T, IBM, and Toshiba. Not as a contractor, but as a regular employer in those companies.

 

This is the longest server outage that I have seen in 35 years of software architecture, design, and use. Someone is trying to Do It Themselves instead of calling in someone who knows these servers and get the blasted things fixed. No large company like Walmart or IBM or Federal Express or whatever would stand for such excuses for so many weeks.

 

Enough of the excuses. Have the Groundspeak CIO call in the president of whoever sold them these Commodore-64 servers and get the blasted things fixed!!

 

Think I'm joking. Nope. It's called escalation. And it does not seem to be working right at Groundspeak.

 

I am. I have also worked for AT&T in the past. I think you misunderstand the problem. This is very unlikely a problem with the hardware. As changes are made for the rest of the business which is profitable that shares infrastructure between geocaching.com and Waymarking.com, the mostly neglected Waymarking site is probably not tested or verified much.

 

When Waymarking breaks, it gets patched/fixed as needed at a lower priority than the main business. If somebody had a business case where Waymarking.com could become a profit center, I'm sure the priority would change.

Share this post


Link to post

So we have a new Waymarking release since 7/15/2015. Still not working well. But something has changed in the last days.

Good news I would say! They're working on the problems.

 

Cool, I hadn't noticed that! Hopefully it's an actual change, vs deployment of an automated nightly/weekly build from the trunk. You can't assume there are actually any changes in this release, but I hope you are right.

Share this post


Link to post

Are any of you in the Information Technology fields? I am and have been since 1980. I know whereof I speak. I have worked for AT&T, IBM, and Toshiba. Not as a contractor, but as a regular employer in those companies.

 

This is the longest server outage that I have seen in 35 years of software architecture, design, and use. Someone is trying to Do It Themselves instead of calling in someone who knows these servers and get the blasted things fixed. No large company like Walmart or IBM or Federal Express or whatever would stand for such excuses for so many weeks.

 

Enough of the excuses. Have the Groundspeak CIO call in the president of whoever sold them these Commodore-64 servers and get the blasted things fixed!!

 

Think I'm joking. Nope. It's called escalation. And it does not seem to be working right at Groundspeak.

 

I'm in IT. Because of that I sent a detailed note to contact@Groundspeak.com explaining all the stuff I had tried and the results I was getting. That was on the 14th.

On the 15th, well after it had been working well for me for a while, I got the following reply:

 

Hello Mark,

 

Thank you for contacting us and for your interest in Waymarking. In order to support the rapid community growth of Geocaching.com in the past couple of years, it has been necessary to shift previously dedicated resources from Waymarking to Geocaching. Unfortunately, at this time we are only able to provide limited technical support. Please try posting your question in the Waymarking forums. These forums are monitored and can usually provide you with the best support.

 

Sorry that we can't be of more help at this time.

 

Janelle Geocaching Community Manager

Share this post


Link to post
...I'm in IT. Because of that I sent a detailed note to contact@Groundspeak.com explaining all the stuff I had tried and the results I was getting. That was on the 14th.

On the 15th, well after it had been working well for me for a while, I got the following reply:...

Hi QuesterMark, please post the content of your mail here in the forum, thanks!

Share this post


Link to post
...I don't think that Waymarkers will like what Groundspeak has to say. I firmly believe this is the end of the Waymarking site....

This is not the end of Waymarking, 'Manville Possum Hunters' please stop spreading these false speculations. I've been talking with two Lackeys this weekend for a long time and I'm in contact with Bryan and the Lackey who wrote the Waymarking code. The resources being dedicated to the Waymarking site right now are very limited, this is not new. But they really try to fix the problems as best as they can at the moment.

Whatever you say, you seem to be the only one that can communicate with TPTB here. From what I see nothing ever changes here, it's still the same small group of waymarkers and the community never grows. I just don't understand how Groundspeak can cater to just a few people as geocaching is growing and Waymarking is at an idle. Lucky for Waymarking that Bryan is still interested in it, but as a business person myself I don't see where taking funds from geocachers and their site and putting them into another site that shows no profit makes any sense.

 

I can only speak for myself lumbricus, but you and your "I am the leader" attitude here makes me feel like I don't count as a member here and it has killed the community spirit.

Share this post


Link to post
...I'm in IT. Because of that I sent a detailed note to contact@Groundspeak.com explaining all the stuff I had tried and the results I was getting. That was on the 14th.

On the 15th, well after it had been working well for me for a while, I got the following reply:...

Hi QuesterMark, please post the content of your mail here in the forum, thanks!

 

I sent the following email to contact@Groundspeak.com on Tue, Jul 14, 2015 at 12:44 PM:

Good morning!

 

I've been having issues with the Waymarking site. I'm sure I'm not the only one, but apparently not everyone is having the same problems.

 

I can't create a new waymark.

I can't visit a waymark.

I can't approve a waymark submission.

I can't even look at my approval queues.

I can't even open this waymark's page: http://www.Waymarking.com/waymarks/WMP5KC_Prospect_Area_Library_Prospect_Pennsylvania

 

I can get to my own profile, and go to the lists tab, but if I click on any category or count on that tab, I get the error box, just like with all of the above. But the box with my counts isn't showing.

 

This has been going on since this past Saturday, the 11th.

 

My username is QuesterMark.

Here's the link to my profile: http://www.Waymarking.com/users/profile.aspx?f=1&guid=2eab057c-087b-407d-a156-dacdc7038e31&mypage=1&gt=2

 

Hopefully this gives you some bit of info that will help you solve the problem!

 

If you need any other info or want me to try anything, let me know!

Share this post


Link to post

Are any of you in the Information Technology fields? I am and have been since 1980. I know whereof I speak. I have worked for AT&T, IBM, and Toshiba. Not as a contractor, but as a regular employer in those companies.

 

This is the longest server outage that I have seen in 35 years of software architecture, design, and use. Someone is trying to Do It Themselves instead of calling in someone who knows these servers and get the blasted things fixed. No large company like Walmart or IBM or Federal Express or whatever would stand for such excuses for so many weeks.

 

Enough of the excuses. Have the Groundspeak CIO call in the president of whoever sold them these Commodore-64 servers and get the blasted things fixed!!

 

Think I'm joking. Nope. It's called escalation. And it does not seem to be working right at Groundspeak.

 

I am. I have also worked for AT&T in the past. I think you misunderstand the problem. This is very unlikely a problem with the hardware. As changes are made for the rest of the business which is profitable that shares infrastructure between geocaching.com and Waymarking.com, the mostly neglected Waymarking site is probably not tested or verified much.

 

When Waymarking breaks, it gets patched/fixed as needed at a lower priority than the main business. If somebody had a business case where Waymarking.com could become a profit center, I'm sure the priority would change.

This explains a lot. I had considered the idea that it might be software instead of hardware, but I pushed the idea aside because no one in their right mind puts out software revisions without trying them on their test site; and if those changes do cause problems they can be quickly backed out. The idea that Groundspeak might be making common infrastructure changes between GC and WM, but not testing them on the Waymarking site ("Screw those folks. Let's just see what happens!") never came to my mind.

 

(For one thing, we've been told over and over that Waymarking isn't just an extension of Geocaching from a software platform viewpoint; to the point where I thought that they were totally different implementations with no common code.)

 

At any rate, I've avoided siding with MPH on the "Groundspeak is trying to kill Waymarking" point of view; but with an attitude like what you've described, they're not so much actively killing it, as hoping it will die by attrition.

 

Thanks for explaining what's going on. They still need to escalate this issue. But I understand that my premium membership, or lack thereof, is of no consequence.

Share this post


Link to post

Trying to review Waymarks creates this error message:

 

Server Error in '/' Application.

Compilation Error

Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.

 

Compiler Error Message: BC30560: 'controls_createneworphanlinkcontrol_ascx' is ambiguous in the namespace 'ASP'.

 

Source Error:

 

Line 18: </asp:Panel>

Line 19: <asp:Panel runat="server" ID="uxOrphanControl">

Line 20: <uc1:CreateNewOrphanLinkControl ID="CreateNewOrphanLinkControl1" runat="server" />

Line 21: </asp:Panel>

 

Source File: E:\inetpub\www.Waymarking.com\Waymarking.Web.release-20150715.1.Release_16\controls\CategoryFilterControl.ascx Line: 20

 

Show Detailed Compiler Output:

 

Show Complete Compilation Source:

 

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.34248

Share this post


Link to post

I don't think they're trying to kill it because it complements geocaching and does add value to it. I'm sure they're nursing it along hoping to invest the absolute minimum in it.

 

Unfortunately, as we learn in organizations and especially IT organizations, it's very tempting to put off regular maintenance and care hoping to save money, but when the system breaks, you end up spending more money to put it back together again, than if you had put more effort into regular maintenance.

 

This seems clearly to me that they "lost the handbook" on how the Waymarking site goes together and they're rediscovering it one mistake at a time.

Share this post


Link to post

I pretty much agree with all three of those paragraphs, except that in the second paragraph, based on what ChileHead told us, you should replace the words "regular maintenance" with the words "waymark site testing", and then I agree with it 100%.

 

I once lost the handbook on how to make ice and had to wait until winter ...

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  
Followers 4

×
×
  • Create New...