New extension: EEvent Helper

Great Extension! On one site I have several event calendars with different field groups and they are separate weblogs. Is there anyway to use this extension on different weblogs? Thanks, BJ

I second this feature request - I have two Event weblogs with pretty much identical functionality, it’d be useful to have EEvent Helper working on both. Works very well on one so far.

Cheers,

Cormac

Hey folks, I wasn’t getting notifications of replies to this thread, so sorry for the lateness here.

I’m getting an error on top of all my cp pages after installing this extension (v.1.0.2): Notice: Uninitialized string offset: 0 in /home/xxx/public_html/xxx/extensions/ext.eevent_helper.php on line 151

I assume this was only happening prior to saving any settings for the extension? Version 1.0.3 should fix this, as it first checks for the existence of EEvent Helper settings.

I installed Event Helper but when i turn on the extension I cannot return to the controlpag or login. I remove the extensie from the server but if i actived the extensions manager the problem return.

Unfortunately, manually deleting an extension must be accompanied by removing the extension for the exp_extensions table in your database as well.

Can you try version 1.0.3 and tell me if you still have this problem with the blank CP?

On one site I have several event calendars with different field groups and they are separate weblogs. Is there anyway to use this extension on different weblogs?

I’d like to add this as well. It’s in the plans when I find the time!

One added point. If you have the option to remove the time portion but have events that are already in the database with time portions saved, the current jquery commands won’t get rid of them when you go to edit the entry. I added this substr command to make sure existing ones don’t show as well.

$js = '
                [removed]
                <!-- Added by EEvent Helper -->
                $(document).ready(function()
                    {
                    ';
                if($this->settings['start_date_field'])
                {
                    $js .= '$("input[name='.$this->settings['start_date_field'].']").attr("maxlength", "10");
                    $("input[name='.$this->settings['start_date_field'].']").val($("input[name='.$this->settings['start_date_field'].']").val().substr(0,10));
                    ';
                }
                else
                {
                    $js .= '$("input[name=entry_date]").attr("maxlength", "10");
                    $("input[name=entry_date]").val($("input[name=entry_date]").val().substr(0,10));
                    ';
                }
                if($this->settings['end_date_field'])
                {
                    $js .= '$("input[name='.$this->settings['end_date_field'].']").attr("maxlength", "10");
                    $("input[name='.$this->settings['end_date_field'].']").val($("input[name='.$this->settings['end_date_field'].']").val().substr(0,10));
                    ';
                }
                $js .= '}
                );
                [removed]
                </head>
                ';

Thanks for catching that, and contributing the code - I’ll commit these updates to GitHub shortly.

Just updated EEvent Helper to version 1.1, which adds support for multiple events weblogs. NOTE! You must deactivate EEvent Helper before upgrading to 1.1, as the settings format has changed! Also, version 1.1 requires CP jQuery loading jQuery 1.3+.

Any problems, please let me know.

If I understand how this works correctly, it will automatically set the expiration time to the end of the day of the event? Is there a way to automatically set the expiration time to say the beginning of the day instead of the end of the day, e.g. 8:00 am the day of the event?

You are correct - expiration is set to the end of the day of the event, OR the end of the “End Date” of the event (if you’ve chosen a custom field for the End Date). There’s no setting in the extension to change this - but feel free to make the change yourself. (Expiration date stuff starts at line 299.) 😊

Great, Thanks!

This is awesome and I’d love to use it but our site uses MSM. There are a few sites with identically named weblogs. Any chance you could add in COLGROUPs that display the name of the site to differentiate the event weblog setting?

I’m poking around in the code but am too much of a n00b to know if colgroup support is built into $DSP.

I’d love to use it but our site uses MSM. There are a few sites with identically named weblogs.

Good catch there. I’ll push an update in the next few days that adds the site name to the weblog select menu if MSM is installed.

If you don’t mind, we’re actually making mods right now that will make the settings MSM-site-specific. This removes the need for OPTGROUP (I misspoke mentioning COLGROUP previously). When you go to the settings page it will show only the current site’s weblogs in the SELECT.

I can fork the master and recommit if you want once we’ve finished and tested.

That’d be great. I thought about making the settings MSM-specific, but since it works just fine as is, put it on the back-burner. Please do send a note if/when you make these changes. It should be just a matter of altering the one SELECT query on the settings screen to include the site_id - no need to add another level of depth to the settings array to hold the site_id.

I should probably do the same for Entry REEdirect and Tag Sync when time permits.

Ok. We’re almost done testing. I’ll email you the file if you PM me your email address. That way you can recommit to GitHub if you want to.

MSM Support has been added to a forked copy of EEvent Helper on GitHub. We also added a feature to ignore end dates entirely… so you can still use the custom field for entry date and the feature to set start date to 12:00 but without the auto-creation of an end date and time.