Can you let me know exactly what you have entered as the time ranges here please? It's expecting 3 or 4 digit numbers with no punctuation, e.g. "900", "1030" etc.
Hmm, I haven't seen that. Can I just check you are clicking "Add" to add a single range (e.g. 0000 to 0500) before you click "Save"? If so if you can also let me know what browser you are using I'll see if I can replicate it and do something about it.
I've just released an update (v0.1.4) which fixes a couple of JavaScript errors I found in testing, which I think was probably causing the issues you found. Hope that sorts it and thanks for reporting.
Nope, Update do solve one issue in authentication(there was issue if you dont select checkbox "authentication" at first, it was not taking defination as not logged in but blank), But issue in time of day still remains. I added two time spans as below
But the defination on save is still blank
And after this I am unable to edit and add any time, the page refreshes if I try that but nothing happens
I just checked on IE, and found the following, It works properly on IE, but throws error in angular for firefox and chrome.
If I save group from IE and open on other browser, it still throws error. I have not checked the functionality yet, but hope this is just backend script error and wont affect the actual functionality. The idea behind this package is nice and will be useful for many of us.
EDIT: also once saved time of day, unable to edit from IE too, need to delete and add new property
Thanks for checking and posting back, appreciate you following it up. I won't be able to get to it until a bit later but hopefully with that error message it should make it clear what's going wrong so I can sort it out.
Believe I've found the issue which looked to stem from trying to store the time values as numbers. As strings we don't get these serialisation issues and works just the same when evaluating. Could you try the latest version please (0.1.5)? You'll need to delete any time of day criteria you have already made and re-enter them so the updated internal JSON syntax is used.
Issue in Time of Day
Unable to add group defination criteria "Time of day".
defination remains blank on adding any time range.
I am using umbraco version 7.2.1
Can you let me know exactly what you have entered as the time ranges here please? It's expecting 3 or 4 digit numbers with no punctuation, e.g. "900", "1030" etc.
As suggested like 0000 to 0500 or 0600 to 1200
Hmm, I haven't seen that. Can I just check you are clicking "Add" to add a single range (e.g. 0000 to 0500) before you click "Save"? If so if you can also let me know what browser you are using I'll see if I can replicate it and do something about it.
Yes, I am clicking add before save, I have also tried adding multiple ranges, i can add or edit at that time, but once I save, defination is blank.
I've just released an update (v0.1.4) which fixes a couple of JavaScript errors I found in testing, which I think was probably causing the issues you found. Hope that sorts it and thanks for reporting.
Andy
Nope, Update do solve one issue in authentication(there was issue if you dont select checkbox "authentication" at first, it was not taking defination as not logged in but blank), But issue in time of day still remains. I added two time spans as below
But the defination on save is still blank
And after this I am unable to edit and add any time, the page refreshes if I try that but nothing happens
I just checked on IE, and found the following, It works properly on IE, but throws error in angular for firefox and chrome.
If I save group from IE and open on other browser, it still throws error. I have not checked the functionality yet, but hope this is just backend script error and wont affect the actual functionality. The idea behind this package is nice and will be useful for many of us.
EDIT: also once saved time of day, unable to edit from IE too, need to delete and add new property
Thanks for checking and posting back, appreciate you following it up. I won't be able to get to it until a bit later but hopefully with that error message it should make it clear what's going wrong so I can sort it out.
Believe I've found the issue which looked to stem from trying to store the time values as numbers. As strings we don't get these serialisation issues and works just the same when evaluating. Could you try the latest version please (0.1.5)? You'll need to delete any time of day criteria you have already made and re-enter them so the updated internal JSON syntax is used.
This solved the issue. Thanks Andy.
is working on a reply...