Renaming extcal to calender
Hi, qoute from old Ticket:
Extcal has been upgraded to an ImpressCMS 1.3 module and has been renamed Calendar.
http://impresscmsdev.assembla.com/spaces/impresscmsaddons/tickets/304-extcal-does-not-work-with-1-3-rc1
But in the SVN the module is still called extcal. I downloaded it, renamed the folder into "calender" and uploaded it to an test-workspace. Installation works, but nothing else.
Got these message:
FEHLER: Handler existiert nicht // Error: Handler does not exist
Modul: extcal
Name: cat
It should be cleand up.
Extcal has been upgraded to an ImpressCMS 1.3 module and has been renamed Calendar.
http://impresscmsdev.assembla.com/spaces/impresscmsaddons/tickets/304-extcal-does-not-work-with-1-3-rc1
But in the SVN the module is still called extcal. I downloaded it, renamed the folder into "calender" and uploaded it to an test-workspace. Installation works, but nothing else.
Got these message:
FEHLER: Handler existiert nicht // Error: Handler does not exist
Modul: extcal
Name: cat
It should be cleand up.
Leave a comment
on 2011-12-29 15:58 *
By mcdonald3072
The name of the module in the Module Administration has been changed to Calendar only, not the installation folder. The name of the installation folder is still extcal.
on 2012-02-03 02:13 *
By
I think there are two options.
1) Close the ticket as invalid.
2) To think about to change the module name to "calendar".
Both are good ideas. If anyone use the old module, this person can update the module. To rename the module is in my eyes a nice option, but the work is very high.
1) Close the ticket as invalid.
2) To think about to change the module name to "calendar".
Both are good ideas. If anyone use the old module, this person can update the module. To rename the module is in my eyes a nice option, but the work is very high.
on 2012-02-03 06:24 *
By mcdonald3072
Think best is to leave it as is for a release.
This way users can easily continue using the module under icms 1.3.
With a later release we can start renaming (dirname, db tables, etc) and modifying the module.
This way users can easily continue using the module under icms 1.3.
With a later release we can start renaming (dirname, db tables, etc) and modifying the module.