Showtime and Statistics in CMSMS 2.0

[pengels]

Both modules are not working any longer in CMSMS 2.x. The original authors are not responding to emails. I have build working solutions of these modules with CMSMS 2.1.2., but I'm not sure how to publish them. These "fixed" versions are based on the latest releases of the corresponding modules and were not changed in any functionality. They are just working fine again.

I wonder, if it is legal to create a new forge-entry, because I'm not the author (rebuplishing of existing code). Any ideas?

Regards from Germany

Peter

[Jeff]

You are free to "fork" a module and create a new entry in the Forge. You need to maintain copyright notices and state that you are forking the module.

Here is an example from JMFilePicker a fork of GBFilePicker:

<?php
#-------------------------------------------------------------------------
# JMFilePicker
# Version 1.0
# (c) 2016 by Fernando Morgado aka Jo Morg <jomorg@cmsmadesimple.org>
# The module's homepage is: http://dev.cmsmadesimple.org/projects/jmfilepicker/
#
# A fork of: GBFilePicker (c) 2010-2012 by Georg Busch
# maintained by Fernando Morgado AKA Jo Morg
# since 2016
#-------------------------------------------------------------------------
# Original Author: Georg Busch <georg.busch@gmx.net>
#-------------------------------------------------------------------------
#
# JMFilePicker is a CMS Made Simple module that enables the web developer to create
# multiple lists throughout a site. It can be duplicated and given friendly
# names for easier client maintenance.
#
#-------------------------------------------------------------------------
#
# CMS - CMS Made Simple is (c) 2010 by Ted Kulp (wishy@cmsmadesimple.org)
# This project's homepage is: http://www.cmsmadesimple.org
#
#-------------------------------------------------------------------------
# BEGIN_LICENSE
#-------------------------------------------------------------------------
# This file is part of JMFilePicker
# JMFilePicker program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# JMFilePicker program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
# Or read it online: http://www.gnu.org/licenses/licenses.html#GPL
#
#-------------------------------------------------------------------------
# END_LICENSE
#-------------------------------------------------------------------------

[calguy1000]

two other considerations:

a: give your forked module a new name
b: make sure your forked module writes to different database tables, and can otherwise live side by side in the same install.

[pengels]

Hi all,

the idea to make a completely new module is nice, but in my opinion too much work in comparison to the few changes I made to get Showtime working again.

I have requested a new forge and I hope, that I will be able to manage SVN (never used that before) to upload the files.

[Jo Morg]

the idea to make a completely new module is nice, but in my opinion too much work in comparison to the few changes I made to get Showtime working again.

I have requested a new forge and I hope, that I will be able to manage SVN (never used that before) to upload the files.

It's not a matter of doing a new module.... it's a matter of having to do a new module for technical, ethical, and legal reasons.
What Calgu1000 posted are not only guidelines or considerations: they are forge rules. And not complying to them may lead to the removal of the module from the Forge.

[pengels]

Hi Jo,

ok, I have made a completely independent version Showtime2 with new database tables and so on. Showtime and Showtime2 may live side by side without interferring. The new tables have the disadvantage, that all slideshows must be recreated. Ok, that is the price. Therefore Showtime2 could be published now, it is well testet.

But I'm completely unfamiliar with SVN. I have installed TortouiseSVN but I have no idea how to use it. My tests yesterday ends with no success. Is there a step-by-step instruction somewhere?

Regards Peter

[10010110]

The new tables have the disadvantage, that all slideshows must be recreated. Ok, that is the price.

If the module is generally the same with just different table prefixes, couldn’t you write a simple migration script so that entries of the old module can be copied to the respective tables of the new module?

[pengels]

That is exactly what I did in the meantime: If Showtime 3.4 is still installed and you are going to install Showtime2 3.4.2 the old tables were copied to Showtime2, so that all Slideshows are available in Showtime2. After that Showtime can be deinstalled and removed.

Regards Peter