Problem sending messages in Message Center

[+funkymunkyzone]

Lately I am experiencing serious difficulties sending messages in the Message Center.  This is in Firefox.

 

This is what happens:

1. I click on message the owner on a cache page

2. Message center opens and pre-populates with the text Regarding whatever cache

3. I click into the box and type my message

4. I click on Send and the send button fades slightly, and then nothing at all happens

5. After waiting to see if anything will happen, I click back twice to get back to the cache page and then I repeat this process around 20 times (no exaggeration) until finally my message sends.

 

This is truly painful.

 

[+Stockiwocki]

I have the same problem, since yesterday evening.

Edited August 27, 2019 by Stockiwocki

[+Max and 99]

1 hour ago, funkymunkyzone said:

Lately I am experiencing serious difficulties sending messages in the Message Center.  This is in Firefox.

 

This is what happens:

1. I click on message the owner on a cache page

2. Message center opens and pre-populates with the text Regarding whatever cache

3. I click into the box and type my message

4. I click on Send and the send button fades slightly, and then nothing at all happens

5. After waiting to see if anything will happen, I click back twice to get back to the cache page and then I repeat this process around 20 times (no exaggeration) until finally my message sends.

 

This is truly painful.

 

I bolded #4. I honestly thought it was just my Kindle having this issue until I saw others complaining on the forums. I guess I'm lucky, because my message always sends after the second click.

[+IceColdUK]

Same as the issue being discussed here?

 

 

[+wabicek]

Message center is completely broken, unable to send any message. There are some JavaScript errors in browser's console.

[+wabicek]

It seems that this bug has been resolved. 

[+Camroo]

1 hour ago, wabicek said:

It seems that this bug has been resolved.

phew.... thank goodness. i had to try to sort out all my earthcache answers and people logging them without any messages... 

[+TheLimeCat]

Just checked and I am still experiencing this issue. It only occurs when messages are sent from the link on a cache page. When I send them through a user's profile, they appear normally. In addition, when attempting to send a message through the cache page, the box that normally contains the "drop files here" text is completely gone and I cannot attach any images.

[+funkymunkyzone]

On 8/30/2019 at 1:56 AM, wabicek said:

It seems that this bug has been resolved. 

 

Nope, it's still happening just as bad as before.

[Moun10Bike]

The dev team is aware of this and have made a fix, but it has not been released yet. That should happen next week. 

[+Bunkshyde]

I also have this problem from my iPhone X (ie Safari). Very frustrating trying to respond to questions to log Virtual and Earth Caches. 

[+terratin]

Nope, not solved yet. I'm currently logging ECs again and just ran into this problem again. Sigh.

[+lodgebarn]

Bug still exists. I am using Chrome. Start with cache page, click on owner to message. New tab brought up, can click send button but nothing happens. Using F12 in the browser I get this console error. Please can you resolve this long standing problem, it is very very annoying.

 

Uncaught TypeError: Cannot read property 'getUploads' of undefined
    at r.onChildSendMessage (edit-panel.js:85)
    at r._childViewEventHandler (vendor?v=kjos4HvY2tTzLSi8NP-gCqQetz7UryGqZtFiHV5iUdc1:1)
    at l (vendor?v=kjos4HvY2tTzLSi8NP-gCqQetz7UryGqZtFiHV5iUdc1:1)
    at g (vendor?v=kjos4HvY2tTzLSi8NP-gCqQetz7UryGqZtFiHV5iUdc1:1)
    at e (vendor?v=kjos4HvY2tTzLSi8NP-gCqQetz7UryGqZtFiHV5iUdc1:1)
    at r.u.trigger (vendor?v=kjos4HvY2tTzLSi8NP-gCqQetz7UryGqZtFiHV5iUdc1:1)
    at r.y (vendor?v=kjos4HvY2tTzLSi8NP-gCqQetz7UryGqZtFiHV5iUdc1:1)
    at r.triggerMethod (vendor?v=kjos4HvY2tTzLSi8NP-gCqQetz7UryGqZtFiHV5iUdc1:1)
    at r.<anonymous> (vendor?v=kjos4HvY2tTzLSi8NP-gCqQetz7UryGqZtFiHV5iUdc1:1)
    at HTMLDivElement.dispatch (vendor?v=kjos4HvY2tTzLSi8NP-gCqQetz7UryGqZtFiHV5iUdc1:1)
onChildSendMessage @ edit-panel.js:85
_childViewEventHandler @ vendor?v=kjos4HvY2tTzLSi8NP-gCqQetz7UryGqZtFiHV5iUdc1:1
l @ vendor?v=kjos4HvY2tTzLSi8NP-gCqQetz7UryGqZtFiHV5iUdc1:1
g @ vendor?v=kjos4HvY2tTzLSi8NP-gCqQetz7UryGqZtFiHV5iUdc1:1
e @ vendor?v=kjos4HvY2tTzLSi8NP-gCqQetz7UryGqZtFiHV5iUdc1:1
u.trigger @ vendor?v=kjos4HvY2tTzLSi8NP-gCqQetz7UryGqZtFiHV5iUdc1:1
y @ vendor?v=kjos4HvY2tTzLSi8NP-gCqQetz7UryGqZtFiHV5iUdc1:1
triggerMethod @ vendor?v=kjos4HvY2tTzLSi8NP-gCqQetz7UryGqZtFiHV5iUdc1:1
(anonymous) @ vendor?v=kjos4HvY2tTzLSi8NP-gCqQetz7UryGqZtFiHV5iUdc1:1
dispatch @ vendor?v=kjos4HvY2tTzLSi8NP-gCqQetz7UryGqZtFiHV5iUdc1:1
l.handle @ vendor?v=kjos4HvY2tTzLSi8NP-gCqQetz7UryGqZtFiHV5iUdc1:1

[+lodgebarn]

Detour is to go to owner page then click send message. Paste in the stuff that was not sent and all is fine.

[+twlare]

Same problem - 6-Sep-2019. Using Google Chrome under Windows 10. Tried Microsoft Edge - same result.

[+brendan714]

Same problem

[+lodgebarn]

This is clearly a reproducible problem and a code issue. It causes loads of problems especially when on my phone. Come on headquarters at least comment and then make it a very high priority fix.

Edited September 9, 2019 by lodgebarn

[+funkymunkyzone]

Moun10bike did give us an update.  We are now just waiting for the fix to come through.

 

On 8/31/2019 at 3:25 PM, Moun10Bike said:

The dev team is aware of this and have made a fix, but it has not been released yet. That should happen next week. 

 

[+terratin]

Btw, I also notice the same behaviour when going to the browse map from the search map: a click on a cache does not open up the information of it most of the time.

[+Highlands_Guy]

On 9/4/2019 at 11:15 PM, lodgebarn said:

Detour is to go to owner page then click send message. Paste in the stuff that was not sent and all is fine.

 

Thanks. This worked for me. I was trying to send some Earthcache and Virtual answers and it was most annoying trying to use the "Message this owner" from the cache page.

 

As you suggested, I used the  "Message this owner" from the cache page. I typed out my info, then copied the text. I went back to the cache page, clicked on the owners name that took me to the owners profile page. From there I clicked on SEND MESSAGE, pasted my message and then SEND. It went right away.

 

This is a good work around for now. Thanks.

[+Alphadog]

Still having this issue. I'm using Google Chrome. I get a lot of messages on my virtual and can't respond to them in the Message Center from my desktop. Have been able to use the function in the geocaching app, but that is not my preference.

[+lodgebarn]

On 8/31/2019 at 4:25 AM, Moun10Bike said:

The dev team is aware of this and have made a fix, but it has not been released yet. That should happen next week. 

Can we have another update now it has been about 5 weeks. This problem is a cause of major problems for all who answer ECs/Virtuals and is more important than new features.

[Moun10Bike]

1 hour ago, lodgebarn said:

Can we have another update now it has been about 5 weeks. This problem is a cause of major problems for all who answer ECs/Virtuals and is more important than new features.

 

The fix was finally rolled out on September 23. I see only one post above from after that date and it appears to be an issue unrelated to the OP.

[+lodgebarn]

1 hour ago, Moun10Bike said:

 

The fix was finally rolled out on September 23. I see only one post above from after that date and it appears to be an issue unrelated to the OP.

Brilliant thanks for the update!

[Moun10Bike]

In the interest of full transparency, in following up on this, I discovered that while this was fixed and deployed, a subsequent roll-out removed the fix. After some conversation in the office, a "re-fix" is rolling out momentarily.

 

Sigh.

[+terratin]

Thanks Moun10Bike. I was wondering as I again could not send answers via the message centre last week. Do give some superglue to the developers to make the fix stick

[+pli]

On 10/3/2019 at 11:02 PM, Moun10Bike said:

In the interest of full transparency, in following up on this, I discovered that while this was fixed and deployed, a subsequent roll-out removed the fix. After some conversation in the office, a "re-fix" is rolling out momentarily.

 

Sigh.

Just tried it on a virtual, works, Youre the best. THX !