Event Calendar v3

[DivaVocals]

the second link, with "TRUE" as the last parameter, uses the old zen_image function which imbeds the image's native height and width in the IMG tag.

Just got back from Nashville and I'm wading through all of the latest posts.. Have a question regarding the above comment.. While I understand what dw08gm is stating how image re-sizing works for him. My concern is that BOTH of the options for the display be available for users of this module (where the last parameter = "TRUE"). It's not clear if the latest code allows for BOTH options.. I will download tonight of course to see..

I am pushing this point because the reason to include the image and height in the image tag is not in support of artificially resizing the image display in the browser, but also in support of other user agents (e.g. a speech browser) which should have that information in order to relate it to the user. I understand that dw08gm is trying to maintain a fluid design for HIS site, but I need to point out that currently NONE of the available free and paid templates (ala Template Monstrosity and their ilk) are responsive design templates.

I would suggest that resolving for a responsive design issue in this ONE module will not make the rest of most user's of this module's site fluid/responsive.. There are other means/techniques which will bring responsive design to the entire site (I personally am testing a jQuery solution which will help make images responsive), and it is my understanding that the upcoming v1.6 release of Zen Cart will include a replacement for the default classic template which is a responsive design template.

My point is can the Events Calendar include BOTH image display options for those shopowners who want to maintain compatibility with other user agents. Is there a reason to not include BOTH options??

[LaCamus]

The alpha release I put up earlier supports both.

[DivaVocals]

The alpha release I put up earlier supports both.

Cool!! Will be testing tonight.. Have I mentioned how much you rock lately!!!

[LaCamus]

Here's the whole thing: Attachment 12352

1) Has the fix/request on the link section to now show "no link selected" (not just when added and deleted).
2) Also in link section, drop downs will show "None" at the top if not selected (except for products, those are based on a manufacturer or category being selected).
3) Fixed problems at the bottom of the "review" page with the image resize info/warning boxes.
4) Includes the changes to the Image function on the front end to support dw08gm's request.
5) Has dw08gm's view long date option in there.
6) Took CSS out in vicinity of my changes and moved to separate file, still some inline...needed in some special situations. (back end)
7) Moved majority of javascript out into another file (back end)
8) Moved some larger php functions out into another file (front & back)
9) I think I caught most (maybe all) of my text, even in the drop downs, for the code I created/changed and moved it to the language file. (back end)
10) I made a number of table and formatting changes for the screen layouts (admin side only), you may want to check to see if they look ok. For one, you will notice the default table on all events pages now stretches to 100%.
11) Worked out "some" of the issues with checking the start and end dates before moving to the "review" page (javascript errors instead of php).
12) Changed "delete event" section to provide user with info on what he/she is deleting (just in case).
13) Put in the ability to delete other "matching" events that have the same title and creation date (needed for #17, see below). Warns before pulling the trigger.
14) I think I worked out all the cross-browser issues. I would have been finished yesterday if it wasn't for this. I had to compromise(give up) on a couple of issues.
15) Added some functionality for popup errors/warnings and help, incorporated into #17.
16) Added the ability to copy an event. Allows you to grab an existing event and use it's data to seed a new event. (Would you believe me if I told you I pulled this off with just 3 lines of code?)
17) The big one is the ability to add multiple events, this is not a TRUE recurring events mod, meaning that 1 event would be saved to the db and dates would be calculated from it on the front end when building the calendars/lists. What is does is calculate a # of dates into the future (configurable based on your input) and sticks them in the database, 1 event for each newly calculated date. Has the ability to see all the dates before they are added (using popup help...#15). Gives you info about your start & end dates which is completely configurable in the language file (includes the use of mergeable variables).

Things that need to be done....
1) More testing to make sure it works for everyone else.
2) There are lots of align and valign cellpadding border, etc. tags in the tables that will have to be addressed at some point.
3) More inline css can still come out.
4) The ability to delete and select (link back to) existing image files.
5) Maybe the start/end date info mod should be added to the base edit window (currently it only shows when you click on "Multiple Events").

Testing encouraged, constructive criticism welcome...

Thanks,
Rus

This version also includes the mod to "jump over" the event list (and go straight to the event) when you click on a day that has only one event (as a defined option).

[dw08gm]

Rus

Works great, spectacularly even, especially impressed by the code to copy/add multiple events.

However
1) Issue of GIF/PNG transparency areas blackening on resize not resolved.
2) Month/Year dropdown selections not preserved, but are changed back to current month/year upon reloading page.

Are these two problems likely to be resolved any time soon?

Cheers

[DivaVocals]

Two very important things I left off the to do list...
1) Move a # of the configurable defines to the admin->configuration drop down menu.

I've got this working and I included changes to the SQL file to support this. In support of this I made several changes to some of the admin extra_datafiles files to align things up a little more consistently (moved defines out of the admin extra_definitions database definition file for example)

//  Moved to YOUR_ADMIN/includes/languages/english/extra_definitions/events_manager.php
//define('BOX_EXTRAS_EVENTS_MANAGER', 'Events Manager');
//define('FILENAME_EVENTS_MANAGER', 'events_manager.php');

and YOUR_ADMIN/includes/languages/english/extra_definitions/events_manager.php now includes:

    define('BOX_CONFIGURATION_EVENTS_CALENDAR', 'Events Calendar Settings');
    define('BOX_EXTRAS_EVENTS_MANAGER', 'Events Manager');
    define('FILENAME_EVENTS_MANAGER', 'events_manager.php');

Also I found this and commented it out:

//    define('BOX_TOOLS_EVENTS_MANAGER', 'Events Manager'); //removed because as far as I can tell this is not being used

In the configuration settings, I included defines from the store side extra_definitions file, and I also modified the SQL so that the Events Calendar page key is now called eventsCalendar and the configuration options page key is configEventsCalendar. This makes the SQL and page keys for this module consistent with how other default Zen Cart page keys are set up (particularly the ones for configuration menu options)

that said I did not include the month defines (wanna look at the best way how to make that an admin option to support a choice between the long and short array). I also did not include the filetypes from the admin or store side in the Event Calendar configuration settings. Not sure if that should be an admin option.. thoughts on this everyone??

The following settings are included in the Events Calendar configuration setting menu and commented out in the defines files:

//    define(EVENTS_FILE_MAX_WIDTH, '800');                      //** rus.02: for max image width in px, check on uploads, change on review
//    define(EVENTS_FILE_MAX_HEIGHT,'600');                      //** rus.02: for max image height in px, check on uploads, change on review
//    define(EVENTS_FILE_RESIZE, true);                          //** rus.02: for image resizing, set to false to do/show no resizing 
//    define(EVENTS_MAX_RECURS,'52');                            //** rus.03: max possible # of recurring events to add to db at one time
// First day of the week in calendar, eg 0=Sunday, 1=Monday, etc;
//define('FIRST_DAY_OF_WEEK', 0);
// No of years to be shown in sidebox year drop-down
//define('NUMBER_OF_YEARS', 5);
// Month defines in sidebox month drop-down
define('MONTHS_SHORT_ARRAY', 'JAN,FEB,MAR,APR,MAY,JUN,JUL,AUG,SEP,OCT,NOV,DEC');
// define('MONTHS_LONG_ARRAY', 'January,February,March,April,May,June,July,August,September,October,November,December');
//**rus.03: when query returns only 1 event, jump over the event list (false=always show list on single day click)
//define(EVENTS_SINGLE_JUMP, true);
//**rus.03: use long dates (includes day of week) when displaying events
//define(EVENTS_LONG_DATES, true);

but now the following works:

 <?php echo event_flink_small($event_array['image'], $event_array['title'], 'class="c1"'); ?>

My point is can the Events Calendar include BOTH image display options for those shopowners who want to maintain compatibility with other user agents. Is there a reason to not include BOTH options??

The alpha release I put up earlier supports both.

Actually it does support both, but only if one removes the "true" from the code as dw08gm did. So I added an additional admin option that allows the shopowner to chose which option they want without having to edit the code directly at all as follows:

<?php if (EVENTS_DISPLAY_IMAGE_WIDTH_HEIGHT == 'true') { ?>
    <?php echo event_flink_small($event_array['image'], $event_array['title'], 'class="event_calendar_image"', true); ?>
<?php } else { ?>
    <?php echo event_flink_small($event_array['image'], $event_array['title'], 'class="event_calendar_image"'); ?>
<?php } ?>

This way BOTH options are supported.. (should make everyone happy and keep novice shopowners out of the code)

For greater clarity or uniqueness, the tag img.c1
in \includes\templates\YourTemplate\css\stylesheet_events_calendar.css
could be changed to img.eci or img.event_calendar_image

which would then require changing class="c1" in
\includes\templates\YourTemplate\templates\tpl_events_calendar_default.php
to class="eci" or class="event_calendar_image" respectively.

I agree.. I made this change and replaced "c1" class with "event_calendar_image". The "c1" class is a bit vaguely named, and this is a LOT more explicit..

Gonna post the files I am working off of in a moment.. I need a bio break and a stretch..

[LaCamus]

Rus

Works great, spectacularly even, especially impressed by the code to copy/add multiple events.

However
1) Issue of GIF/PNG transparency areas blackening on resize not resolved.
2) Month/Year dropdown selections not preserved, but are changed back to current month/year upon reloading page.

Are these two problems likely to be resolved any time soon?

Cheers

1) I will look at soon...next few days.
2) Not "as" familiar with the front side, maybe this is going to be easy, I'm thinking its going to need some cookies...still looking at this week.

[DivaVocals]

Okay.. I got the install and uninstall SQL all dialed in now.. Admin menu works great..

Gotta post this and scoot.. I have to be up in 3 hours for work.. What's attached is the FULL fileset with all of Rus' code and the minor changes I made including the addition of an admin menu..

[LaCamus]

I've got this working and I included changes to the SQL file to support this. In support of this I made several changes to some of the admin extra_datafiles files to align things up a little more consistently (moved defines out of the admin extra_definitions database definition file for example)

//  Moved to YOUR_ADMIN/includes/languages/english/extra_definitions/events_manager.php
//define('BOX_EXTRAS_EVENTS_MANAGER', 'Events Manager');
//define('FILENAME_EVENTS_MANAGER', 'events_manager.php');

and YOUR_ADMIN/includes/languages/english/extra_definitions/events_manager.php now includes:

    define('BOX_CONFIGURATION_EVENTS_CALENDAR', 'Events Calendar Settings');
    define('BOX_EXTRAS_EVENTS_MANAGER', 'Events Manager');
    define('FILENAME_EVENTS_MANAGER', 'events_manager.php');

Also I found this and commented it out:

//    define('BOX_TOOLS_EVENTS_MANAGER', 'Events Manager'); //removed because as far as I can tell this is not being used

In the configuration settings, I included defines from the store side extra_definitions file, and I also modified the SQL so that the Events Calendar page key is now called eventsCalendar and the configuration options page key is configEventsCalendar. This makes the SQL and page keys for this module consistent with how other default Zen Cart page keys are set up (particularly the ones for configuration menu options)

that said I did not include the month defines (wanna look at the best way how to make that an admin option to support a choice between the long and short array). I also did not include the filetypes from the admin or store side in the Event Calendar configuration settings. Not sure if that should be an admin option.. thoughts on this everyone??

I would say no to the images (those are pretty standard worlwide) and yes to the others...ex: some may only want to use pdf's.

The following settings are included in the Events Calendar configuration setting menu and commented out in the defines files:

//    define(EVENTS_FILE_MAX_WIDTH, '800');                      //** rus.02: for max image width in px, check on uploads, change on review
//    define(EVENTS_FILE_MAX_HEIGHT,'600');                      //** rus.02: for max image height in px, check on uploads, change on review
//    define(EVENTS_FILE_RESIZE, true);                          //** rus.02: for image resizing, set to false to do/show no resizing 
//    define(EVENTS_MAX_RECURS,'52');                            //** rus.03: max possible # of recurring events to add to db at one time
// First day of the week in calendar, eg 0=Sunday, 1=Monday, etc;
//define('FIRST_DAY_OF_WEEK', 0);
// No of years to be shown in sidebox year drop-down
//define('NUMBER_OF_YEARS', 5);
// Month defines in sidebox month drop-down
define('MONTHS_SHORT_ARRAY', 'JAN,FEB,MAR,APR,MAY,JUN,JUL,AUG,SEP,OCT,NOV,DEC');
// define('MONTHS_LONG_ARRAY', 'January,February,March,April,May,June,July,August,September,October,November,December');
//**rus.03: when query returns only 1 event, jump over the event list (false=always show list on single day click)
//define(EVENTS_SINGLE_JUMP, true);
//**rus.03: use long dates (includes day of week) when displaying events
//define(EVENTS_LONG_DATES, true);

Actually it does support both, but only if one removes the "true" from the code as dw08gm did. So I added an additional admin option that allows the shopowner to chose which option they want without having to edit the code directly at all as follows:

<?php if (EVENTS_DISPLAY_IMAGE_WIDTH_HEIGHT == 'true') { ?>
    <?php echo event_flink_small($event_array['image'], $event_array['title'], 'class="event_calendar_image"', true); ?>
<?php } else { ?>
    <?php echo event_flink_small($event_array['image'], $event_array['title'], 'class="event_calendar_image"'); ?>
<?php } ?>

This way BOTH options are supported.. (should make everyone happy and keep novice shopowners out of the code)


I agree.. I made this change and replaced "c1" class with "event_calendar_image". The "c1" class is a bit vaguely named, and this is a LOT more explicit..

Gonna post the files I am working off of in a moment.. I need a bio break and a stretch..

All great stuff...good job.

[DivaVocals]

I would say no to the images (those are pretty standard worlwide) and yes to the others...ex: some may only want to use pdf's.

All great stuff...good job.

Trying to follow in your shoes sir..

Okay.. I got the install and uninstall SQL all dialed in now.. Admin menu works great..

Gotta post this and scoot.. I have to be up in 3 hours for work.. What's attached is the FULL fileset with all of Rus' code and the minor changes I made including the addition of an admin menu..

Oh and for anyone stumbling into this thread:
If you decide to use ANY of the files posted by either dw08gm, LaCamus, or myself on a LIVE productions store, please know that if you read through the last 4-6 pages of this support thread you will see that these files are in QA testing at the moment and NOT meant to be used on ANYONE's live store.

(let me stress this part again)
The Event Calendar for ZC 1.5.1-v03.zip files are in QA testing at the moment and ARE NOT meant to be used on ANYONE's live store.

That said, anyone who chooses to install a beta version of ANY module on a live store, does so at their own risk and this is not recommended/supported..