Extension talk:MW Calendar

Please use my Google Issue trackerfor new issues, its easier, really...
 * Issue Tracker


 * Use the (+) button above to add new comments, thanks!

old calendar
Dear Kenyu73, I have been using your "old" calendar extension Extension:Calendar (Kenyu73) for some while now. I was wondering why you now use direct database calls? What will be the advantage? Will we be able to "import" the old calenders? Thank you. --MartinK 10:23, 9 March 2010 (UTC)

re:
yes, you can import the old calendar, but the code isn't documented yet and only supports the original date format. The main purpose of direct db usage is speed and control. I create and store the calendar events in my own tables and plan to have all the options stored in tables via an option form.

re:
Great. I'm looking forward to it ;-) --MartinK 14:08, 12 March 2010 (UTC)

Calendar beta testing

 * Issue with Nav buttons not working, should be fixed in v0.2.1.... Please test and let me know if it's OK now. Thanks!

sorry
but I've got no google-account yet.. First: No changes - still same problem. Then I found out, that when changing skin (I'm using modern skin) database is updated. validating database checking tables...

running database update scripts...

VALIDATION COMPLETED (please refresh) Now I see the addEvent-form. But after switching back to modern skin I still have an error.

Warning: Variable passed to each is not an array or object in C:\Programme\WebServer\xampp\htdocs\mediawiki\extensions\mwcalendar\includes\main.php on line 67

Best regads, asomy.

re
asomy - I dont understand - does it now work? That message is only a warning and shouldn't cause any issues. I changed my wiki to modern skin and I'm still running fine.


 * OK, I try to explain better (sorry for my bad english..).  First, I noticed, that I can see the form, when displaying the page printable (hm, in german this is Druckversion.. don't know what the english version is called). Adding events seems not working. You can fill out the form, but in the calendar nothing is shown.  So I decided to change the skin. My standard skin was modern, so I switched to monobook. Then I saw the form on my page. Now I switched back to modern skin and it looks kind of strange... The letters are to big now and I get this warning on top of page - but only on this page using the calendar. - asomy

Thanks for fixing Issue Nr. 1
Thanks for fixning my reported issue.

The calendar is now usable for me!

I've added some usability bug reports from my first using experiences to the Issue Tracker.

--JohannesPonader 20:27, 17 March 2010 (UTC)

Feature Request
This would be a great feature from our sight: Every time a user updates the calendar, an .ics-File (iCal) with fixed url is also updated, so by downloading this file one has always the recent dates. I know that WebDAV is much more powerful, but we need a lightweight solution fitting in our Wiki-only concept. --Waschl

This warning just came up on my system
Deprecated: Function split is deprecated in /var/lib/mediawiki/extensions/Calendar/Calendar.php on line 939

Misc Issues
A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was: CREATE TABLE `ankenyikescalendar_header` ( `id` integer NOT NULL auto_increment, `name` varchar(255) NOT NULL default , `description` varchar(255) default , PRIMARY KEY (`id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1; from within function "". MySQL returned error "1142: CREATE command denied to user 'ankenyikes'@'localhost' for table 'ankenyikescalendar_header' (localhost) A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was:   CREATE TABLE `ankenyikescalendar_version` ( `id` integer NOT NULL auto_increment, `version` varchar(255) default , `date` double default '0', PRIMARY KEY (`id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1;  from within function "". MySQL returned error "1142: CREATE command denied to user 'ankenyikes'@'localhost' for table 'ankenyikescalendar_version' (localhost)". A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was:    CREATE TABLE `ankenyikescalendar_events` ( `id` integer NOT NULL auto_increment, `calendarid` integer NOT NULL default '0', `subject` varchar(255) default , `location` varchar(255) default , `start` double NOT NULL default '0', `end` double NOT NULL default '0', `allday` boolean NOT NULL default false, `text` longtext default , `createdby` varchar(255) NOT NULL default , `createddate` double NOT NULL default '0', `invites` mediumtext default , `editedby` varchar(255) default '', `editeddate` double default '0', PRIMARY KEY (`id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1; from within function "". MySQL returned error "1142: CREATE command denied to user 'ankenyikes'@'localhost' for table 'ankenyikescalendar_events' (localhost)".
 * Version 0.3.1 (23-Mar-2010) reports error "Fatal error: Cannot redeclare class mwCalendar in /ankenyikes.org/public/extensions/mwcalendar/includes/main.php on line 12" after installation.
 * this would only occur if you had another extensions using the class mwcalendar (ie: another calendar?)
 * RESOLVED... I removed the extension 'Calendar' prior to enabling 'mwcalendar'. Thank you!
 * Received the errors...
 * RESOLVED... The above error was generated as my MySQL service account does not have access to create tables. Future I'd suggest temporarily granting such access for the first calendar build, then remove the access. In my case, I ran the three CREATE TABLE statements from 'root' to resolve the issue.
 * Receive two identical forms to fill for a new appointment (when the "+" is clicked), and receive two appointments when just one of the two forms is completed. Test calendar is at
 * re: you need to add a custom key to the eventlist tag -- 
 * RESOLVED... Had these two lines on the page when entering the event, removed the second and I started getting single entries. Thank you, I'm going to give it a try for my simple 'schedule of events', will have a text page as backup as this is still beta.
 * 
 * 

// No anonymous editing allowed - $wgGroupPermissions['*']['edit'] = false;
 * In wiki's that do not allow non-logged in users to edit, mwcalendar should not allow editing. These are the commands added to LocalSettings.php to restrict editing of the wiki...


 * I had a similar need and made a small hack. I recommend that the author incorporate something similar
 * edit includes\main.php
 * on or around line 519 look for the following:
 * $link = "".helpers::translate('mwc_new').'';
 * replace the one line with the following 4:
 * $link = "";
 * global $wgTitle, $wgUser; if( $wgUser->isAllowed('edit')) {
 * $link = "".helpers::translate('mwc_new').'';
 * };

NOTE: This removes the edit link on the calendar days [e.g. (+)], it does not protect someone from manually entering into the address bar of their browser.
 * The Batch Entry method ROCKS for entering a month's worth of events.