+ Google Calendar button – not working and a problem with Hebrew

[sagi]

Hi Guys, me again.
My events are all written in Hebrew. now there are 2 problems with that:
1. if there is a Hebrew slug to a URL of an event – the link gets broken (and this doesnt happen for example when I use a hebrew slugs on any of my posts).
2. Major problem- when I try to add an event to my google calendar – if any of the title/description/etc is in Hebrew – the “add to google calendar” button just doesnt work.
Here is an example event (try for yourself) – http://www.pixelperfect.co.il/event/curious-minds/

3. When an event is in English (like here – http://www.pixelperfect.co.il/event/mobile-apps-and-beer)
It does work but takes all the HTML with it instead of the text itself.

I would really love to get some help on this.

Thanks a lot!
Sagi

[Rob]

Hey Sagi. Thanks for the heads up here; this is a weird issue that I’m unable to recreate on my default 2011 install. Is it possible you’ve got another calendar-related plugin (or any plugin for that matter) which could be creating a conflict? Is your site in an environment where you can test deactivating other plugins as a test? Let me know if not and I can try to figure out another solution.

[Adam]

Hi Rob –

The Google Calendar button is AWESOME! …but…
I can 2nd that the Google Calendar link doesn’t always work on my site either. I’ve noticed that if I create a test event with a really short post content in WordPress, then the google calendar button works perfectly, populating the event’s post content to the google calendar description field.

But many of this site’s events may have a couple paragraphs of text typed into the event’s post content box in WordPress. On those event’s pages, the google calendar button attempts to pass the full content of the post/event in the URL, causing google to return the following error:

“414. That’s an error.
The requested URL /ServiceLogin… is too large to process. That’s all we know.”

So my guess is the OP’s problem may not be hebrew/english, but rather a LONG post (his first example) vs a short enough post (2nd example).

Can you verify this and let us know a solution? Thanks!

[Rob]

Hey Adam. Thanks for the heads up; do you have a site I can test this on, with events along these lines that I can import into my Google Calendar? Would also help to have that to share with the team internally here…

[Jonny]

I too have this exact error. Unfortunately, the current site i’m developing is localhost so cannot show a live example.

[Rob]

Thanks Jonny. Are you running into the same issue specific to Hebrew?

[Jonny]

Hi Rob,
Sorry, no the problem is just the google add to calendar and error
“414. That’s an error.
The requested URL /ServiceLogin… is too large to process. That’s all we know.”

The site is in english

[Rob]

Thanks for confirming, Jonny. As Adam noted above: “So my guess is the OP’s problem may not be hebrew/english, but rather a LONG post (his first example) vs a short enough post (2nd example).”

Any chance that’s your issue here, too? It sounds like this could be the cause and not related to the Hebrew item at all. Would also be helpful to know whether the issue persists for you if you deactivate other plugins (specifically any that alter permalinks or are calendar-related). Also, just to confirm…you’re on 2.0.2 for both The Events Calendar and PRO, right?

[Jonny]

Hey Rob,
Yes v2.0.2
Permalinks: /%postname%/

I have events that have around 1600 characters – error!
Events that have around 540 characters – works fine!

Its definately something to do with long post content.

[Rob]

This is great to know. Thanks Jonny; let me get this in front of one of our devs so they can identify what’s up and we can get this patched for our next release (probably will be 2.1 at this point, since 2.0.3 is in a code freeze as it’s practically done). Appreciate you guys bringing this to our attention.

[Jonny]

No problem Rob.
Its not a dealbreaker. I’ll keep an eye out on updates.
Its a great plugin!
🙂

[Rob]

Thanks Jonny. With feedback from folks like yourself, we’re always working to make it better. Thanks again for the heads up and do let us know if you have any other questions.

[Author]

Posts