Weird Behavior in Wordpress

I love the product and the BEAUTIFUL interface.
I am having some difficulties when showing “Oncoming Events”. For instance, if I have a repeating event, say every 3rd Monday of the month from 17:00 - 18:00, my Oncoming Events shows me the next three (as I have it configured) upcoming dates. However, if one of those times or dates change, I go to edit that particular instance, no applying the change the the entire repeat, and my changes to appear in the Oncoming list, it still shows the original time. However, the calendar view does see the change. Any thoughts?

Secondly, I have an issue where if my admin section uses SSL (https), when I click on the Scheduler section of the plugins menu, I get the yellow ribbon of death. However, if I tell Wordpress to not require https for admin, I can access the Scheduler configuration section.

Again, love the product.

First issue may be caused by some caching plugin, are you using any?
In any case we will investigate both problems.

Also, which version of scheduler plugin you are using?

To my knowledge I am not using any caching plugin.
Also, my version I tested on was 2.0.x and then it also occurs in 2.3.
It could very well be an issue on my end.

Both problems confirmed

a) first one caused by timezone settings of IE, fix added to local codebase and will be released as part of next version. If you need the updated file - contact us directly at support@dhtmlx.com

b) caused by the paths in admin part of scheduler, if necessary I can provide steps which need to be done to switch scheduler’s admin to https ( it will work in https, but may have problem in normal http mode after them )

Thanks a lot! By the way, it may help if you know that the only browsers we use are Safari and Firefox. I know you had mentioned IE, but we experienced it with the aforementioned browsers.
Secondly, yes, please direct me as to how to use https in the admin. I tried to also set my “Link to the scheduler” to use https but, it fails. I’m thinking there may also be a DNS or Certificate issue. Perhaps it is failing because it doesn’t like my signed certificate?

event-calendar-scheduler/admin.php

line46

locate

url: '<?php echo WP_PLUGIN_URL; ?>/event-calendar-scheduler/codebase/',
url_load: '<?php echo WP_PLUGIN_URL; ?>/event-calendar-scheduler/codebase/dhtmlxSchedulerConfiguratorLoad.php?task=loadxml',

replace with

url: 'https://wordpress_dir/wp-content/plugins/event-calendar-scheduler/codebase/', url_load: 'https://wordpress_dir/wp-content/plugins/event-calendar-scheduler/codebase/dhtmlxSchedulerConfiguratorLoad.php?task=loadxml',

Sweet. It works. I did send an email to the above address requesting the file to fix the first problem. I can’t thank you enough for helping me on these issues. I am a big fan and will refer your product to everyone.

The first problem, altering a recurring task, still exists. I looked in the database and things seem to be fine. However, when I set the event_pid to 0, it works. I am trying to figure out the SQL that pulls the events from the table to see how it is trying to use event_pid.

Try to recreate the same recurring event, with new version of plugin.

I am able to get things to work, but, I have to be in the same timezone that I have configured my Wordpress for. So, one of my administrators is in the Central timezone with Windows and cannot get things to work, but I can. This is with the new plugin by the way. However, if I change the timezone to be Central for my other admin, things do not work. Perhaps it is something to do with Windows as the client O.S. Stupid Microsoft. I also know that I had to “Reload” my pages completely to get any new JavaScript from the new plugin. Basically had to dump my cache, etc.
However, this did not work for the other admin. If you would like access to our test environment, I can see what I can do. I just want to help make this product even better because I really like what it does and what you all have done.

We confirm the issue with recurring events and different timezones.
Existing logic of recurring exception relies on timestamps which is not consistent between different time zones.

Unfortunately there is no simple solution so far.
We will investigate it and will try to provide more consistent solution.