Kenika

I have the same problem plus a bit more: Even though I have a page with the “chronoslybase” shortcode, it breaks my theme (menu disappears e.g.) and doesn’t show anything anymore. The problem occured some time ago already, but I couldn’t take care of it yet. So I can’t tell which update or which plugin causes the problem. This is my website: https://www.dennisknickel.com
This is where the events list should show up: https://www.dennisknickel.com/termine/
And this is where a list of my past events should be: https://www.dennisknickel.com/termine/vergangene-termine/
You can also navigate there from the main menu on the left: “Termine” (events) and the subpage “Vergangene Termine” (past events).
This is the page that only contains the “chronoslybase” shortcode: https://www.dennisknickel.com/events/ (You can’t navigate to this empty page from the menu! I only use this for the style incompatibilities with my theme.)

The code I used (which worked until some weeks ago) for upcoming events:

[su_row][su_column size=”1/2″][chronosly type=”category”][/su_column][su_column size=”1/2″][chronosly type=”calendar” year=”current”][/su_column][/su_row]

And this is the code I use for the past events list (also worked until some weeks ago):

[su_row][su_column size=”1/2″][chronosly type=”event” upcoming=”past” pagination=”1″ count=”10″][/su_column][su_column size=”1/2″][chronosly type=”calendar” year=”current”][/su_column][/su_row]

The “su_” shortcodes come from the plugin “Shortcodes Ultimate”!

Thanks in advance!

• This reply was modified 7 years, 6 months ago by Kenika.

Nice, thanks for your answer.
How about the issue that a part of the plugin window is outside the visible area? I mean the window that opens after the search is done (in the backend/visual editor, not the final result in the frontend). Is it only me who’s got this problem? Is it an incompatibility with some other plugin?
Thanks in advance.

@dee-lete: Interesting. Thanks for sharing this info.

But I’d definitely prefer working in text instead of visual mode. Plus: Half of the window that opens is outside my monitor. Hence working with the plugin is still pretty lame. :/

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…

Same problem here! The search function doesn’t work.

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:1

Google 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:1

Google 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:1

Backend:

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…:210

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:1

Google 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:1

Google 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:1

• This reply was modified 8 years, 2 months ago by Kenika.
• This reply was modified 8 years, 2 months ago by Kenika.

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.

Mamma mia…

Hi,
thanks for your reply. But where do I enter this? At my theme’s custom css box? But I only want it to be applied to Chronosly Events Calendar.
Thank you.

Nice! Thanks!

Nice! Thanks, but I still have one issue:
I’d like to list the past events in the category view, not in the event view. If I change “event” with “category”, the pagination changes to “more xxxxx events”. Clicking on that link only shows future events of that category, but no past events.
Adding this to the code:
type="category" (or "event") category="1,4,7"
leads to the message: “No events were found”

Thanks!

It works! Awesome!
I’m seriously fascinated by your support. Thank you so much!

Thanks for your answer!
I’ll contact my provider to find out what’s up. I’m using PHP 7.0 by the way.

Unfortunately, also this code didn’t change anything:

html#ecwid_html body#top.chameleon button.ecwid-btn--primary { background-color: #ED9D2B; }
html#ecwid_html body#top.chameleon button.ecwid-btn--primary:hover { background-color: #747474; }

• This reply was modified 8 years, 5 months ago by Kenika.

Interesting. Thanks!

But it doesn’t work for me: Whenever I try to save a my settings, I’m getting this error page:

Request Entity Too Large

The requested resource
/wp-admin/options.php
does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit.

By the way: The ecwid_chameleon settings are these:
ecwid_chameleon_background
ecwid_chameleon_links
ecwid_chameleon_primary

There is no ““ecwid_chameleon_colors_button” option though.

• This reply was modified 8 years, 5 months ago by Kenika.
• This reply was modified 8 years, 5 months ago by Kenika.

Hi,

yay, that worked for single products (like on this page). Thanks a lot!

Is there also a chance to apply these changes to the storefront (this page)? As I mentioned, I use chameleon skin, but it’s not the ideal orange and the hover color is totally different to the hover color I use on the rest of my website.

Chameleon skin made the buttons #FF6600, whereas I prefer a #ED9D2B.
And the hover color right now is a pale looking #FF944C. I’d like to have it in a grey #747474.

Thanks!