@fixedmachine - I see validity in both request and will taken them under strong consideration for the next release.
And my Categories don’t seem to work.
<?php> // highlighting WHERE startdate >= \''.$date.'\' or enddate >= \''.$date.'\' or `lastrepeat` >= \''.$date.'\' and E.active=1
<?php> // highlighting WHERE (startdate >= \''.$date.'\' or enddate >= \''.$date.'\' or `lastrepeat` >= \''.$date.'\') and C.active=1 and E.active=1
<?php> // highlighting WHERE (startdate >= \''.$date.'\' and enddate < ADDDATE(\''.$date.'\', INTERVAL 1 MONTH)) or `repeat` REGEXP \'[[:alnum:]]+\' '.$catID.' and E.active=1
<?php> // highlighting WHERE ((startdate >= \''.$date.'\' and enddate < ADDDATE(\''.$date.'\', INTERVAL 1 MONTH)) or `repeat` REGEXP \'[[:alnum:]]+\') '.$catID.' and C.active=1 and E.active=1
if(!empty($param['tplEvent'])){if(!empty($param['mxcTplEventListItemWrap'])){
☆ A M B ☆
Yes, the parameter mxcStartDayID is used to set which weekday is the start of the week. As to the format of the date and time. The time/date format had not crossed my mind in the sense that I was think more UI, but makes sense if a site is multi-lingual that there would be a valid need for that to be changed on an individual instance and not globally.
I think that all cultural determined settings, like:
- time/data format
- start day of week (that’s already implemented as: mxcStartDayID right?)
Not currently, but that’s a good enhancement request. This request is also noted as a road-map item that would also extended this feature out to ACL through webuser groups for section of the site where you might have authenticated users as well. I’m also trying to track any feature request at http://code.google.com/p/mxcalendar/wiki/FeatureRequest.
Is there a parameter for setting default (initial) category to display? Something like &CatId=# but to pass in the snippet call? I want to create two different calendars on my site. One for one category, and second one for the other category - managed from one place, but without relations between them. Any suggestions?
The result here is that the category will no longer be visible when entering in events, but wanted to allow legacy events in un-published categories to still visible to the end-user. In case, lets say you had a special category for an yearly event, but then you unpublished that category so that no other events were added to that category, by un-plushing this no new events could be entered yet the event would still be visible to end users to filter on as a category.
EDIT:
Seems that publishing and un-publishing a category has no visible results.
This was first put in place so that when an event was "deleted" it never left the system, to retain an historical log. Then in a later release I converted to actual removal for data storage purposes with the intent on adding in an up-publish vs. full delete of the event.
Charless, why there is an active field for events when there is no option in events add/edit tab for publishing/un-publishing them?
Yes, this I will certainly add in.
Don’t you think that the `event list` could be filtered by category just like `callendar` ?
Thanks for catching this one, in previous pilot release I went back through and renamed all parameters to avoid any collisions with other snippets and this one did not get caught. It will be updated in the next release.
There is a bug in the code (my mod included) which unable you to assign different mxcTplEventListItemWrap from chunk.
No problem. I think that my changes are so ’light’ that they shouldn’t generate any additional problems. I need your module now, so I can’t wait until the next release - that’s why I’m patching it by myself. I thought that there are people who may need category filtering which works, so that’s why I uploaded my code. If you grant me the access to SVN I could help you with that project.
@fixedmachine - thanks for the thorough review, please be patient and allow me the opportunity to roll this into the releases, granted you can do as you wish but I’d like to ensure that changes are logged and tested in multiple environments.
I was using that for previous release. But this time I thought that it’ll be faster to write that on the forum.
Please visit http://code.google.com/p/mxcalendar/issues/list to log issues if you would please, this is my consolidated issue tracking location.
I fully agree with you. But there should be much more parameters for advanced users. Without that we’ll be doomed to hacking the code.
Side note, I want to make sure that this stays lean but also provides proper flexibility through parameters. The choice to use the configuration tab inside the mxCalendar module was to provide more laymen users a better experience when using mxCalendar. In addition we didn’t want to get too crazy with all the parameters as that can become more confusing as additional features are rolled into this project.
I understand your intentions, but I think that it’s unintuitive behaviour. ’Un-publishing’ category should hide all the events from that category. They are unpublished now right? So they, implicitly, ’were never published’. I think that you are talking about ’hiding’ that category from module interface, so it will not be displayed in "add event" form and it won’t be possible to add any new event within that category. Now ’un-publishing’ category not causing hide of that category inside "add event" form. Maybe there should be another button ’in use’/’not in use’ or something like that. Of course it would be great if only some users could change those options. But managing user privileges... that’s another story...
Quote from: fixedmachine at Jun 15, 2010, 03:26 PMThe result here is that the category will no longer be visible when entering in events, but wanted to allow legacy events in un-published categories to still visible to the end-user. In case, lets say you had a special category for an yearly event, but then you unpublished that category so that no other events were added to that category, by un-plushing this no new events could be entered yet the event would still be visible to end users to filter on as a category.
EDIT:
Seems that publishing and un-publishing a category has no visible results.
I think a better solution would be to add a second layer to the un-publish state that is for the end-user visibility. Then that would allow you to remove all events from the display.
Hmm... so maybe we could use it for publishing/un-publishing single events? It would be a useful feature. It’s already implemented in some way, we just need to add a little check box in add/edit tab.
This was first put in place so that when an event was "deleted" it never left the system, to retain an historical log. Then in a later release I converted to actual removal for data storage purposes with the intent on adding in an up-publish vs. full delete of the event.
Thanks for catching this one, in previous pilot release I went back through and renamed all parameters to avoid any collisions with other snippets and this one did not get caught. It will be updated in the next release.
If I can help in some way, I surely will
☆ A M B ☆
☆ A M B ☆
So in summary the Event Title wasn’t appearing for me in the Event Details. The solution:
Change the mxCalendar.class.php line
From
$modx->setPlaceholder(’mxcEventDetailTitle’,$title);
To
$modx->setPlaceholder(’mxcEventDetailTitle’,$p_val[’title’]);
and now the Event Title should now appear.
Thanks everyone.
☆ A M B ☆
☆ A M B ☆
My Categories and Configuration tabs are empty.
MODx: 1.0.4
MySQL 5.0.90-community
PHP: 5.2.12
Same result on another server:
MODx: 1.0.4
MySQL 5.0.67-community
PHP: 5.2.9
☆ A M B ☆