Issue with € sign
-
Hi,
it happens quite often that when I create an event, the price in EUR is shown incorrect. Instead of the EUR sign (€) that I want to be shown, I get to see some cryptical code like this: %E2%82%AC
I have to change it, save it, hope that it works now… and when I’m unlucky, I have to repeat this: save, change, hope, repeat.Is this a bug? Or do you have a recommendation what I can do? I also already tried using codes like €, but it still fails from time to time. It’s pretty annoying.
Thanks for your support!
-
Dear Dennis,
sorry for the delay, we have made an update to solve the issue.
Please tell us if now works as expected.Thank you! The problems seems to be solved. Therefore, the editor isn’t loading that well anymore since this update.
The editor page loads, but when it’s loaded, I can’t scroll anymore: it freezes. So I have to refresh (F5) the page to be able to edit the event; sometimes several times.
It only happens in the events editor, not when editing a default wordpress page or post.Is possible to have a js console log, to see if some error is thrown?
Frontend:
https://www.dennisknickel.com/wp-content/themes/beach_apollo/js/jackbox/php/graphics.php?jackbox_path=../img/graphics/ Failed to load resource: the server responded with a status of 403 (Forbidden)
Google Maps API warning: NoApiKeys https://developers.google.com/maps/documentation/javascript/error-messages#no-api-keys
YA.j @ util.js:212
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:127
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:46
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:43
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:46
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:99
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:43
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:99
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:43
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:99
gc @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:45
fc.cb @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:99
(anonymous) @ util.js:1Google Maps API warning: InvalidKey https://developers.google.com/maps/documentation/javascript/error-messages#invalid-key
YA.j @ util.js:212
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:127
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:46
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:43
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:46
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:99
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:43
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:99
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:43
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:99
gc @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:45
fc.cb @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:99
(anonymous) @ util.js:1Google Maps API warning: SensorNotRequired https://developers.google.com/maps/documentation/javascript/error-messages#sensor-not-required
YA.j @ util.js:212
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:127
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:46
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:43
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:46
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:99
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:43
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:99
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:43
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:99
gc @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:45
fc.cb @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:99
(anonymous) @ util.js:1Backend:
jquery.js?ver=1.12.4:3 The specified value “!” does not conform to the required format. The format is “#rrggbb” where rr, gg, bb are two-digit hexadecimal numbers.
ja @ jquery.js?ver=1.12.4:3
n.parseHTML @ jquery.js?ver=1.12.4:4
a.fn.init @ jquery-migrate.min.js?ver=1.4.1:2
n @ jquery.js?ver=1.12.4:2
(anonymous) @ spectrum.js?ver=7d1b0ee…:2
(anonymous) @ spectrum.js?ver=7d1b0ee…:2
(anonymous) @ spectrum.js?ver=7d1b0ee…:210Google Maps API warning: NoApiKeys https://developers.google.com/maps/documentation/javascript/error-messages#no-api-keys
YA.j @ util.js:212
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:127
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:46
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:43
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:46
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:99
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:43
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:99
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:43
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:99
gc @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:45
fc.cb @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:99
(anonymous) @ util.js:1Google Maps API warning: InvalidKey https://developers.google.com/maps/documentation/javascript/error-messages#invalid-key
YA.j @ util.js:212
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:127
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:46
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:43
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:46
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:99
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:43
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:99
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:43
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:99
gc @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:45
fc.cb @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:99
(anonymous) @ util.js:1Google Maps API warning: SensorNotRequired https://developers.google.com/maps/documentation/javascript/error-messages#sensor-not-required
YA.j @ util.js:212
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:127
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:46
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:43
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:46
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:99
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:43
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:99
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:43
(anonymous) @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:99
gc @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:45
fc.cb @ js?key&v=3.exp&sensor=false&ver=7d1b0ee…:99
(anonymous) @ util.js:1it seems there is no critical error on the javascript code.
This problem is on all Chronosly events or just on some cases?
Try creating a new test event to find if it’s something on the description that breaks the template rendering, at the bottom of the page, and this breaks the page.The last update shouldn’t break anything, and we don’t see this problem on our testing sites.
Unfortunately we will need more feedback from other possible problematical sites to check it.
Sorry for the late reply.
It only happens with Chronosly events. Waiting seems to solve the problem. Means: If I wait about 20 seconds after opening an event (new or already published doesn’t make a difference), it works. But that’s a bit annoying…
- The topic ‘Issue with € sign’ is closed to new replies.