Hello.
I’m starting with this scheduler and recently downloaded the v.4.0 build 130813 version to test it. However, when I tried to run the samples on the zip package I noticed a possible bug on the recurring events support. Always the “dhtmlxscheduler_recurring.js” file is included, when you delete an event it is shown on the screen until you perform another task (add event, change view) if the “details view” is disabled. If enabled, the details dialog simply does not close forcing you to refresh the window.
When you test the recurring events demo on dhtmlx.com/docs/products/dht … ring.shtml (one of the “live demos”) it works well as expected, so I downloaded that page and run it with my local version of the scheduler, getting the same error again. Hence, I conclude the version used in the sample is not the same is avalible to download and that the oldest (?) works better.
What version is that one and is it possible to download it? Is there a way to fix that problem?
Thanks for your help.
Hello,
I couldn’t reproduce the issue with our samples(tested on build 130813).
Check the screencast below, i’ve deleted one event and changed label of another, both has been updated instantly. Do i need to do something else to reproduce the issue?
screencast.com/t/Hr0CCRDBb6J0
Thank you for answering, Aliaksandr.
Well, I (shamelly) have to admit I’m just “opening” the *.html file of every test on the explorer instead of runnig it with some server and database connection, so the PHP code and related don’t work, but that should not be the problem since events are also stored as objects inside the scheduler, right?
The process I followed is very simple. I took the “samples\01_initialization_loading\01_basic_init.html” demo and linked the “dhtmlxscheduler_recurring.js” (using build 130813) which automatically adds recurring events functionality. I repeated the test (add/delete events) and discoverd that the error only occurs with no recurring events. That is to say, you can add any type of event but the view only updates after deleting when you erase recurring events. A little debugging showed me that execution fails on the sheduler.updateEvent function (“dhtmlxscheduler_recurring.js”) because sometimes the “rec_type” property is not defined.
To check this behavior, I directly downloaded the *.js files linked in the “live demo” dhtmlx.com/docs/products/dht … ring.shtml (“http://www.dhtmlx.com/docs/products/dhtmlxScheduler/codebase/dhtmlxscheduler.js” and “http://www.dhtmlx.com/docs/products/dhtmlxScheduler/codebase/ext/dhtmlxscheduler_recurring.js”) and used them to test. Here the deleting error disappears but the scheduler is not displayed correctly.
I guess those trials demostrate this behavior is specific to the build 130813.
Is it clear what I did? Any suggestion to solve it?
Note: I have to say my goal is not to make the demo work but getting a stable scheduler version to use the recurring events easily.
Note 2: Please excuse me for such a long message. I have no way to upload a screen record.
The ‘recurring events’ example is expected to be run on the server, since it uses php backend to handle CRUD operations.
When you delete an event, the client-side awaits confirmation from server before removing the event box. So when the example is opened in explorer, the server-side does not work, client wont receive any confirm and the whole application will work not the same way as it would on the actual server.
I’m not quite understand the issue. Scheduler have certain set of required data properties of the event objects. When you’ll be implementing recurring event in your app, the data will be loaded with all required fields (as you would specify it on server side, and as it works in recurring events example), and this situation will never come up.