You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm experiencing a strange issue when the add to calendar links are sent to an email that uses Roundcube. The issue only seems to be occurring when I try to add the event from an email opened in Roundcube. I have tested the same exact event sent to gmail and yahoo and there are no issues.
What's strange is that I have extracted the Google Calendar link from both an email sent to Roundcube as well as an email sent to Gmail.
As far as I can tell, the links are exactly the same. However, if you open the link that was sent to Roundcube, you get a AddToCalendar.com gets invalid event parameters that complains about location This value should not be blank.
Here are the location blurbs from each link (that are exactly the same):
Hi there,
I'm experiencing a strange issue when the add to calendar links are sent to an email that uses Roundcube. The issue only seems to be occurring when I try to add the event from an email opened in Roundcube. I have tested the same exact event sent to gmail and yahoo and there are no issues.
What's strange is that I have extracted the Google Calendar link from both an email sent to Roundcube as well as an email sent to Gmail.
Link Sent to Roundcube:
Link Sent to Gmail:
As far as I can tell, the links are exactly the same. However, if you open the link that was sent to Roundcube, you get a
AddToCalendar.com gets invalid event parameters
that complains aboutlocation This value should not be blank.
Here are the location blurbs from each link (that are exactly the same):
[location]=https%3A%2F%2Fglobal.gotomeeting.com%2Fmeeting%2Fjoin%2F120101757&e[0]
[location]=https%3A%2F%2Fglobal.gotomeeting.com%2Fmeeting%2Fjoin%2F120101757&e[0]
The link when opened from gmail works perfectly.
Any ideas what might be going on? It seems strange that the exact same link is resulting in different behaviors.
Thanks in advance!
The text was updated successfully, but these errors were encountered: