Being a repetitive task for me, it’s probably a good idea for me to write this down.
Installing events and events subscription management to Drupal 6 is as easy as installing a few modules and doing a quick setup.
- download and install the event module
- download and install the signup module
- enable the event module and all its sub-modules (don’t check datepicker if you want to go fast, as it will require additional CSS and JS to work)
- enable the signup module (required by event-signup)
- go to permissions and enable the events and signup features (nodes and signup sections) for user roles as needed (maybe you want to allow anonymous people to signup for events…)
- go to content administration -> content type -> event -> edit
- in the Signup configuration section, select any of the 2 last options (allowed or enabled) then save
- create an event and “enable” the signup option (edit the corresponding elements to suit your needs)
That’s it. Have fun.
Note that the RSVP module should be used to “invite” people, not to enable their signup to your event.
Yesterday I was invited by AcroCampus (through recommendation by AEFOL) to talk about Chamilo in Elche (Elx), Alicante, Spain, to a public of around 40 e-learning-savvy people. I brushed along the lines of open source software and its advantages for Peruvian education, then went on (shortly) about Chamilo and what it offered.
We later discussed the Chamilo platform and a bunch of people told me they were going to try it out this week. Seems like Chamilo actually made it from unknown to popular quite quickly. Most Dokeos users/administrators I’m meeting tell me they’re switching soon (some of them are waiting for 1.8.7, to be released very shortly at the time of writing).
Presentation of open-source software and Chamilo, in Spanish, available on my Slideshare channel:
It’s easy enough to do (although you shouldn’t fix your issues that way, obviously), but I found it difficult to find information about it on the web.
To change your PHP settings in order to avoid these warnings, one quick way is to edit your php.ini file (in /etc/php5/apache2/php.ini) and find the line that says
error_reporting = E_ALL
Possibly it will include other options. A general practical way to avoid the warnings is to extend that line like this:
error_reporting = E_ALL & ~E_NOTICE & ~E_DEPRECATED
Then you’ll have to reload your Apache configuration (apachectl reload or /etc/init.d/apache2 reload)
I’ll be talking about Chamilo and the state of open-source software in Peru on Radio Panik tonight, 7pm Paris time. French only: http://www.radiopanik.org/spip/Ecoutez-radio-Panik
I will be presenting Chamilo and our intention to make a Chamilo package for Ubuntu this year at the Ubuntu Developers Summit in Brussels, on Friday 14th of May (at the beginning of the afternoon). As a side gift, I will be meeting Jono Bacon (writer of “The Art of Community” and Mark Shuttleworth, the founder of Ubuntu).
As a developer or translator for Chamilo 1.8.*, you might often be faced with the need to know what variable is used to look for a translated term to be shown on screen. While we don’t have a nice in-house feature for this just yet, you can easily hack your own. Here’s how:
- Go to main/inc/lib/internationalization.lib.php
- Find the function get_lang
- Find the first and the third “return” statements
- Put the whole value (after the equal sign) between parenthesis and prefix them with: $variable.’-’. (this should give something like return $cache[$language][$variable] = $variable.’-’.($_api_is_translated ? ($is_utf8_encoding ? $langvar : api_utf8_decode($langvar, $encoding)) : $langvar); )
From then, you should see all the variables show before the translated term. You can then go on http://translate.chamilo.org, click on “Advanced search” and change the translation to the right one.