Page 3 of 3

Re: Announcing Calendar 1.0

Posted: Thu Dec 11, 2008 3:09 pm
by Charles Butcher
Thank you so much, seitenwind. For some reason I missed the first page and saw only people complaining about how their templates didn't work any more. Evidently the changes suggested by KO worked for you too.

I have also discovered how to dump CSV data from MySQL, so that might be another workaround, though less elegant. Sorry for asking earlier for pointers on how to do this. I'm sure many experienced people find such questions irritating. Trouble is, CMSms really does work for ignoramuses like me  :)

Re: Announcing Calendar 1.0

Posted: Sun Dec 14, 2008 10:29 pm
by gertvdijk
I also installed the new 1.0 version in 1.5.1, but I have one problem: there is no template. All fields are empty, so I cannot use one as a basis to edit it to my needs...
So how can I install the default templates? edit: deinstall the old one first, before "upgrading". that did the trick.

Hmm.. now I see more problems... The dutch help of the module is outdated and shows options of versions pre-1.0...

Re: Announcing Calendar 1.0

Posted: Sun Dec 14, 2008 11:15 pm
by calguy1000
Okay.... just to verify that I was not off base.... i used somebody else's installation of CMS Made Simple, went to the module manager....browsed to 'C'.... and clicked on the 'help' link beside Calendar.... there is a help and about link on each row people... .don't you see it?

I saw near the top a message stating that Calendar 1.0 was not compatible with previous versions.  I intentionally wrote this message FOR THIS REASON.   I also put a big large red marquee on my initial announcement post.

So you people are complaining because you downloaded and installed something that you didn't know what it was, and what the consequences were, and now something is broken?   

That's like calling Microsoft and saying 'I downloaded version x.yy.zz of SOMEPROGRAM.EXE from SOMEPLACE.COM and now my machine is screwed.  Do you think they would listen to you?    The answer is a very loud 'NO'. 

You people are responsible for what you do.  Nobody else.   

This version of calendar was well announced, and its caveats continue to be well advertised.... if you didn't listen to them, or couldn't be bothered to read them, it's nobody else's problem.

I will be happy to talk about correctly formatted, and correctly submitted bugs relating to new installs of the calendar module.... but if you're talking about ugrades from 0.8.2 or earlier, go away.

Re: Announcing Calendar 1.0

Posted: Mon Dec 15, 2008 10:26 am
by KO
Please put also a note on Calendar download on Forge that "not compatible with Calendar 0.82 or previous version".
http://dev.cmsmadesimple.org/projects/calendar

If that note won't be there more unneeded confusion will happen as the module has same name with higher version number. It's impossible to know if it's just bug fix, security fix or totally incompatible version unless said in forge where many people download it from.

Othervice great work with module so thanks for that. I'm happy to see it go towards "news" and other standards modules.

Re: Announcing Calendar 1.0

Posted: Sun Dec 21, 2008 9:14 am
by Charles Butcher
Calguy, talk of that kind -- and leaving users without an upgrade path -- is not going to help the reputation of CMSms as an open-source project that truly is simple.

I have to earn a living too, so for me, a village website based on CMSms is a spare-time activity. Without open-source software there would be no website, so if CMSms is going to become progressively harder to use without paid support, I'd appreciate some notice.

You have users out there with large amounts of calendar data locked up in the old format. Calendar 0.8.2 has significant disadvantages, which is presumably why you created a new version. Just what are these users supposed to do?

What upsets me most is that there does seem to be an upgrade path, as KO explained in a previous post. If KO's logic is valid, it surely would not have been too hard to automate the necessary changes to the database? If KO's approach is dangerous for any reason, then a short explanation of why would be appreciated.

Yesterday I upgraded DEVONthink (a Mac information manager) from v1 to v2. This represents a big change to the database, but instead of telling me to throw away a couple of years' worth of work, the program helpfully offered to convert my existing files. I'm sure you could do something similar when you have time to think about Calendar.1.1.

I wish you and everyone in the CMSms community a happy Christmas and a content-filled New Year.

PS: I'm pleased to see there is now a warning on the Forge pages, which after all are the public home of the Calendar project. Having been burned before by installing updates (not yours) via Module Manager, only to find that the Forge has a later version or a patch, I tend to go straight to the Forge. Maybe that's a bad idea, but you have to agree there is some overlap.

Re: Announcing Calendar 1.0

Posted: Mon Dec 22, 2008 1:24 am
by beattie
Hi Calguy, just wanted to say thanks for your work on the calendar. I have no php knowledge and found it very easy to install. Am using the upcoming events, past events and large calendar, awesome! My client is very happy with the outcome  :)

Re: Announcing Calendar 1.0

Posted: Fri Jan 16, 2009 1:49 pm
by monghidi
I, too, wish to thank CalGuy for his hard work on the calendar. I believe that Calguy has taken this module well down a 'right' road for the future and Thank Goodness it received his attention. A good calendar is a fundamental part of any reasonable CMS, which as we all know CMSMS is waaay better than just 'reasonable'!  ;D

At the moment I have a local test copy of an existing site (running all the latest) and I have installed the new 1.0 version of the calendar. It works great in every way, EXCEPT I don't have the old data in, just new data for this month.

My goal is to have everything working on this local copy and LEARN how to move all the old calendar data in, before I try it on my client's live site. I've tried CSV exports in various formats, SQL exports and imports, etc. etc. but I confess -- I just can't seem to get it right. My depth of knowledge on these things is only average, I'm afraid.

SO, after at least two days of trying (and failing) to do this, I am here to ask: What careful steps might one take to get old calendar data integrated into the new calendar? I imagine it must run something like:
-- BACKUP all data.
-- Uninstall old pre-1.0 calendar module
-- Install new calendar module
-- Add some new entries (for testing)
-- Adjust settings, templates, etc. until satisfied with how new calendar works.
-- ?? import old calendar data ?? <-- exactly how to do this?
-- ?? run SQL or (?) to clean up the old calendar data ?? <-- exactly how to do this?

I would sincerely appreciate any concise instructions on how to accomplish this! I humbly suggest that one good explanation of the 'upgrade path' would solve this for everyone.

Thank you!
-Monghidi
PS: I have a 1.5.1 install but would be happy to provide my full installation specs if needed to help answer this.

Re: Announcing Calendar 1.0

Posted: Thu Jan 22, 2009 8:27 am
by Rolf
Hey all,

Here is few changes we noticed on database. With these changes you might get yours running.

Look cms_module_calendar_events -> event_recur_period

and change that from int(11) to varchar(10)

Also you need to change 'none' to '0' on those fields and you can do that with SQL command:


Code:
UPDATE `cms_module_calendar_events` SET event_recur_period = 'none' WHERE event_recur_period = '0'

Also add following fields as those are not done with upgrade:

event_recur_nevents      int(11)
event_recur_interval   int(11)
event_recur_weekdays  varchar(255)
Worked for me!!

Thanks KO,

:D Rolf

Re: Announcing Calendar 1.0

Posted: Thu Jan 22, 2009 8:49 am
by KO
Rolf: You're welcome!

Keijo

Re: Announcing Calendar 1.0

Posted: Fri Apr 10, 2009 12:48 pm
by Etherman2000
FATAL ERROR:
QUERY = INSERT INTO cms_module_cgcalendar_events (event_id,event_title,event_summary,event_details ,event_date_start,event_date_end,event_parent_id ,event_recur_period, event_date_recur_end, event_created_by ,event_recur_nevents, event_recur_interval, event_recur_weekdays ,event_recur_monthdays ,event_create_date, event_modified_date) VALUES (6,'fdry','szerg','aezrg','2009-04-10 11:45:00','NULL',-1,'none','NULL','1',-1,1,'','',NOW(),NOW())
ERROR = Incorrect datetime value: 'NULL' for column 'event_date_end' at row 1

I looked around on this ERROR and found the following... I'm working on a fresh install of CMSMS 1.5.3 installed last week... Current versions of all software and modules...

"Incorrect datetime value:'' error in mysql.
Article Id: #124     Viewed: 772 times     Last updated on: 23 Aug 2008     Article Category: MySQL errors    

If you get the "insert into" error with "Incorrect datetime value: '' for some column, this error occurs due to the restricted mode of the database which doesn't allow the null value insertion, to rectify the issue please follow the below mentioned steps.

1) Find out the value of the variable 'sql_mode' from your database configuration details.

2) To know the value of the variable 'sql_mode', please execute the following query in your mysql query browser:

SELECT @@SESSION.sql_mode;
or
SELECT @@global.sql_mode;

3) If this variable contains value like : STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER etc.... then this is the reason for the occurrence of the error.

4) Modify the value of the variable sql_mode to null to resolve the issue.

5) To do that execute the following query:
set global sql_mode='';

This will change the variable value to null.

Now, open the my.ini file located at c:program files/MySQL/MySQL Server X.x/my.ini.

Add a # at the begining of the line: sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"

Type sql_mode='' on the next line and save the file.

Hope this helps...

Pete

Re: Announcing Calendar 1.0

Posted: Fri Apr 10, 2009 5:07 pm
by tyman00
Just a few quick notes.

1.) Please use the when posting code, it makes it easier for us to read and it doesn't make your post mind numbingly difficult to read :)

2.) I am not sure what you were asking for

3.) Please uninstall Calendar 1.0. It is no longer supported. You need to either install an older version of Calendar (currently 0.8.2) or install CGCalendar which was formerly known as Calendar 1.0. A new project was created for this version of calendar because of the issues with upgrades.

Because Calendar 1.0 is no longer supported, I am going to go ahead and close this thread.