New Calendar Module >> Seeking Pilot Group Members

Hi Charles.

Thanks for your awesome work!

By the way, I tried installing the latest version and got this when I ran the module:

Warning: XMLReader::open() [xmlreader.open]: Unable to open source data in \\frigga\home\users\web\b2504\ph.d30020810\new\assets\modules\mxCalendar\mxCalendar.class.php on line 1943

Warning: XMLReader::setParserProperty() [xmlreader.setparserproperty]: Invalid parser property in \\frigga\home\users\web\b2504\ph.d30020810\new\assets\modules\mxCalendar\mxCalendar.class.php on line 1944

Warning: XMLReader::read() [xmlreader.read]: Load Data before trying to read in \\frigga\home\users\web\b2504\ph.d30020810\new\assets\modules\mxCalendar\mxCalendar.class.php on line 1945

Any ideas?

It says installation successful in green, but this came up below it.

Thoughts?

This is a great add-on, it’s working well, but I was wondering about the moodalbox functionality. It appears the libraries are present, but they generate errors. The rel attribute is set, so I would think if the libraries would be linked correctly, it should work. I’d like to work on this from my end but am unaware where the head information is built for the calendar view. Any thoughts on whether this function should already work (I know this is beta, very good so far) or where I should look to work on the JS libraries?

Thanks for the great work thusfar.

//-- ADD Google AJAX Library - MooTools
$modx->regClientStartupScript('
<script type="text/javascript" src="http://www.google.com/jsapi"></script>
<script type="text/javascript">google.load("mootools", "1.1.2");</script>
');

Quote from: dageyra at Jul 01, 2010, 01:12 AM

This is a great add-on, it’s working well, but I was wondering about the moodalbox functionality. It appears the libraries are present, but they generate errors. The rel attribute is set, so I would think if the libraries would be linked correctly, it should work. I’d like to work on this from my end but am unaware where the head information is built for the calendar view. Any thoughts on whether this function should already work (I know this is beta, very good so far) or where I should look to work on the JS libraries?

Thanks for the great work thusfar.

They should work fine as long as your mootools.js file is being loaded as well. The easiest test to see if that is the problem is to add the following in the mxcalendar snippet code block after the parameters list and above the build core line:

//-- ADD Google AJAX Library - MooTools
$modx->regClientStartupScript('
<script type="text/javascript" src="http://www.google.com/jsapi"></script>
<script type="text/javascript">google.load("mootools", "1.1.2");</script>
');

let me know if you still have any issues after that

cheers

There was something else that came up today. The times for an individual event are not maintained across edits (they reset to midnight when editing an entry, but until edited, the values are stored correctly). We will just take extra care to not have to edit the entries until a resolution is available, the module is more than worth it, but I want to be sure there’s not a configuration mishap versus a confirmed bug. I believe I saw something similar to this in the issues section of the website.

Quote from: dageyra at Jul 02, 2010, 01:14 AM

There was something else that came up today. The times for an individual event are not maintained across edits (they reset to midnight when editing an entry, but until edited, the values are stored correctly). We will just take extra care to not have to edit the entries until a resolution is available, the module is more than worth it, but I want to be sure there’s not a configuration mishap versus a confirmed bug. I believe I saw something similar to this in the issues section of the website.

thanks for the bug report. it looks like it’s caused when the option for "24 hour display (mgr)" in the configuration tab is set to "False". Can you try changing that to "True" and confirm that it works when set to true and I’ll work on getting the bug fixed.

cheers

The time switches to edit default 0100 when set to display 24-hour time in the manager, but otherwise behaves the same as 12:00 AM does for 12-hour time in the manager. Anytime an event is edited, the time becomes 0100.

Is the purchasing and full registration completed on this yet?

We are very interested in this module.