EXT:News Event¶

ICS feed with all events¶

Many calendar applications allow you to subscribe to calendar data. Just like an RSS feed, you can keep your calendar up-to-date with all new events automatically.

The link to the ICS feed would typically look like this: ` http://www.example.com/index.php?id=1&type=101&no_cahce=1 <http://www.example.com/index.php?id=1&type=101&no_cahce=1>`_ .

ICS for single events¶

ICS for single events works in much the same way as the feed with all events. The difference? The generated ICS file contains only one event. When you include the correct static template, a link to “Add to calendar” will automatically be displayed with every event.

Important if you don't use TypoScript constants to configure ICS¶

Unless you use TypoScript constants to set up tt_news, you should include the TypoScript below as a minimum configuration in your TypoScript template. Otherwise the ICS feature won't work at all.

icsevents.10 {
        pid_list < plugin.tt_news.pid_list
        singlePid < plugin.tt_news.singlePid
}

The page object for single events is called singleicsevent , so you will have to write singleicsevent.10 instead to configure the single event ICS feature.

templateFile¶

date_stdWrap¶

plugin.tt_news.mbl_newsevent {
    date_stdWrap.strftime = %x
}

time_stdWrap¶

plugin.tt_news.mbl_newsevent {
    time_stdWrap.strftime = %H:%M
}

where_stdWrap¶

organizer_stdWrap¶

dateLabel_stdWrap¶

datesLabel_stdWrap¶

toLabel_stdWrap¶

whereLabel_stdWrap¶

organizerLabel_stdWrap¶

showOrganizerEmail¶

dateSelMode¶

dateSelMenuNoEmpty¶

dateSelTypoLink¶

disableCategoriesInDateSelLinks¶

dateSelMenuWithCatSelector¶

dateselHeader_stdWrap¶

dateSelTitleCObject¶

LatestShowsNewEvents¶

ics.templateFile¶

ics.icsName¶

ics.from¶

ics.to¶

singleics . templateFile¶

singleICSLink_stdWrap¶

automaticAdjustTime¶

automaticAdjustDate¶

adjustTime¶

adjustDate¶

displayEventUntilEnd¶

enableRegistration¶

registrationLink_typolink¶

registrationLink_typolink {
  parameter.field >
  parameter = insertPIDorURL
  ATagParams = rel="lightbox"
  additionalParams.field = uid
  additionalParams.wrap = &powermail[tt_news]=|
}

<a href=”index.php?id=insertPIDorURL&powermail[tt_news]=123” rel=”lightbox”>Register</a>

replaceWithClosed¶

registrationClosed_stdWrap¶

registerAvailableUntilEnd¶

enablePrice¶

price_stdWrap¶

priceDecimals¶

zeroPrice_stdWrap¶

pricenote_stdWrap¶

enableRegistrationsTracking¶

registrationsTable¶

registrationsSelect¶

registrationsWhere¶

disableIfFull¶

registrationFull_stdWrap¶

displayMaxRegistrations¶

maxRegistrations_stdWrap¶

maxRegistrationsLabel_stdWrap¶

displayPlacesFree¶

placesFree_stdWrap¶

placesFreeLabel_stdWrap¶

displayCurrentRegistrations¶

currentRegistrations_stdWrap¶

currentRegistrationsLabel_stdWrap¶

closedFullPriority¶

hideEvents¶

[plugin.tt_news.mbl_newsevent ]

Setup (Powermail part):¶

Create a page and insert the Powermail plugin. Then create these three fields. (You can create more fields later, but these three are required.)

The first field you should create is used to display the name of the event on the powermail form. The field should be of the type “Add typoscript object”, and the “typoscript object” should be set to “lib.eventinfo”, like this:

The second field is a hidden field that holds the title of the event (So you can see which event the user has signed up to.) The field should be of the type “Hidden field”, like this:

Remember the value of the field “Name for Templates”, as that is needed later for the TypoScript setup.

The third field is similar to the second, but is used to store the UID of the event the user is signing up for. (Useful for reference etc.) The field should look like this:

Again, remember the value of the field “Name for Templates”, as that is needed later for the TypoScript setup.

Setup (TypoScript Constants part):¶

In your Constants field, insert and modify this to match the Powermail fields you just created:

# Change 62 to the pid of the page/sysfolder where your tt_news records are stored.
plugin.tt_news.pid_list = 62

# Change 45 to the pid of the page where you have inserted the powermail plugin.
powermail.plugin.pid = 45

# Name of hidden powermail field created to hold the eventtitle.
powermail.eventtitle.uid = uid8

# Name of hidden powermail field created to hold the eventuid.
powermail.eventuid.uid = uid5

Setup (TypoScript Setup part):¶

In your Setup field insert this:

plugin.tt_news {

        # Here's how you order by registration start:
        listOrderBy = IF(tx_mblnewsevent_regfrom=0, datetime,(tx_mblnewsevent_regfrom + tx_mblnewsevent_regfromtime))
        #And registration end date and time:
        #listOrderBy = IF(tx_mblnewsevent_regto=0, (tx_mblnewsevent_from + tx_mblnewsevent_fromtime),(tx_mblnewsevent_regto + tx_mblnewsevent_regtotime))

        _LOCAL_LANG.default {
                noNewsToListMsg = There's no events at the moment.
                backToList = « Back to list of events
                textRelated = Related events:
        }

        mbl_newsevent {

                enableRegistration = 1
                registrationLink_typolink {
                        title.data = LLL:EXT:mbl_newsevent/locallang.xml:registerLinkLabel
                        parameter = {$powermail.plugin.pid}
                        parameter.override.field = tx_mblnewsevent_regurl
                        additionalParams.field = uid
                        additionalParams.intval = 1
                        additionalParams.wrap = &tx_powermail_pi1[eventUid]=|
                }
                replaceWithClosed = 1
                registerAvailableUntilEnd = 0
                registrationClosed_stdWrap {
                        wrap = |
                        data = LLL:EXT:mbl_newsevent/locallang.xml:registerClosed
                }

        }
}

# Text for the powermail form, describing the event the user is signing up for.
lib.eventinfo = COA_INT
lib.eventinfo {
        10 = CONTENT
        10.table = tt_news
        10.select {
                pidInList = {$plugin.tt_news.pid_list}
                andWhere.data = GPvar:tx_powermail_pi1|eventUid
                andWhere.intval = 1
                andWhere.wrap = uid=|
        }
        10.renderObj = TEXT
        10.renderObj.field = title
        10.renderObj.wrap = <p>You are now signing up for the event: <strong>|</strong></p>
        10.if.isTrue.data = GPvar:tx_powermail_pi1|eventUid
}

# Powermail prefill fields
plugin.tx_powermail_pi1 {
        prefill {
                // Prefil field with event title
                {$powermail.eventtitle.uid} = COA
                {$powermail.eventtitle.uid} {
                        10 = CONTENT
                        10.table = tt_news
                        10.select {
                                pidInList = {$plugin.tt_news.pid_list}
                                andWhere.data = GPvar:tx_powermail_pi1|eventUid
                                andWhere.intval = 1
                                andWhere.wrap = uid=|
                        }
                        10.renderObj = TEXT
                        10.renderObj.value = Error! No eventUid specified.
                        10.renderObj.override.field = title
                }
                // Prefill field with event uid
                {$powermail.eventuid.uid} = COA
                {$powermail.eventuid.uid} {
                        10 = TEXT
                        10.data = GPvar:tx_powermail_pi1|eventUid
                        10.required = 1
                }
        }
}

I have changed TypoScript parameters for the extension, but I see no change. What's up?¶

If you have cleared the cache and haven't misspelled the parameter name, make sure you have inserted the changes under plugin.tt_news.mbl_newsevent . A common error is to insert the changes under plugin.tt_news .

How do I change language strings through TypoScript?¶

With tt_news you can change language strings at plugin.tt_news._LOCAL_LANG. With mbl_newsevent you have to do it by editing plugin.tt_news.mbl_newsevent._LOCAL_LANG.

How do I make tt_news' RSS feature list only events?¶

You can make tt_news output RSS (XML) at the same time as mbl_newsevent handles makes sure only events are output. Here's an example TypoScript, thanks to Vincent Kessels:

plugin.tt_news  {
        code = XML
        mbl_newsevent {
                currentCode = EVENT_FUTURE
        }
}

It is important to note that tt_news' RSS static template has to be included AFTER tt_news and mbl_newsevent's static templates. Otherwise, the settings for events won't be carried over to the RSS feed.

Changes in version 0.2.0¶

• Added new field called “EVENT_SELECTOR”. It lists events for different periods, like the archive menu (“AMENU”).
• Added possibility to define the limit and latestLimit TS properties specificly for the event lists.
• Some changes to the manual (corrections and additions).
• Changed the icon slightly (added a plus-sign) to indicate that the extension extends tt_news.
• Localizeable template markers for strings like “Event date(s):” and “Location”.

Changes in version 0.3.0¶

• ICS calendar download possibility.
• Organizer information (can be gathered from fe_users, be_users or tt_address). Introduces the fields ###EVENT_ORGANIZER### and ###EVENT_ORGANIZER_TEXT### (the last for the label) in the template.
• Added the field ###EVENT_TO_TEXT### in the templates for translated versions of the english word “to” in the template.
• An amount of seconds can now be added to or subtracted from the times displayed in listings.
• Misc. bugs corrected.

Changes in version 0.3.2¶

• It is now possible to make the event selector show either all, future or past events through the TypoScript variable plugin.tt_news.mbl_newsevent.timeperiodSelMode . Thanks to Stig Færch for this.
• New translations included (Norwegian and Finnish).

Changes in version 0.4.0¶

• ICS feed available as a static ext template.
• TypoScript Constants and Setup files preconfigured.
• Divider to tabs implemented. News Event now has it's own tab when you create or edit a news article. (Requires tt_news 2.0.2 or higher, and Typo3 version 3.7.0 or higher.)
• Tested with multilingual news. Work without problems.

Changes in version 0.4.1¶

• Static template must be included for News Events to work.
• Some bugs corrected.

Changes in versions 0.4.2-0.4.4¶

• Bugs corrected
• Added dateSelOrder TypoScript property to choose ascending or descending sorting of the Event Period Selector.

Changes in version 0.4.5¶

• Corrected a bug that made the Event Selector not show in some cases.
• German localization (thanks to René Rossi)
• Correction to the Norwegian localization (Quarter is “kvartal”, not “kvarter”).
• The Extension repository now has the same version number as this manual. How surprising!

Changes in version 0.4.6¶

Corrected a bug in the Event Selector where items were shown that shouldn't be visible. (Thanks to Stig Nørgaard Færch for that.)

Changes in version 1.0.0¶

• This version is almost 100% rewritten. No new features, but a much nicer code. It will hopefully be much more compatible with tt_news updates.
• This version is only partially compatible with previous versions.
• This version is waiting for a feature in tt_news before it becomes 100% compatible with tt_news.

Changes in version 1.1.0¶

• Events can now be displayed until they end (new TS property displayEventUntilEnd).
• Fixing bug appearing when events are exactly 7 days long. (Thanks to Sven Homrighausen.)
• Fixing bug where ICS news links were wrong. (Thanks to Daniel Minder.)
• New “UPDATE” menu item appears if database needs to be updated: Date and Time is kept in separate fields as of v1.0.0.
• Updated manual.

Changes in version 2.0.0¶

Event registration linking and registration start and end. Sponsored by Redvald Hjulstad, hjulstad.no .

• Backend interface improvements.
• extraItemMarkerProcessor() now uses it's own cObj instance with the current tt_news row as data.
• Removing time adjustment from ICS. Since ICS uses UTC time, time adjustment shouldn't be needed. (Thanks to Daniel Minder)
• adjustDate in TypoScript is now deprecated. adjustTime is now the only time adjustment property.

Changes in version 2.0.1¶

French translation by Edern Appéré.

Changes in version 2.1.0¶

• Price and price info field, sponsored by OpenGate .
• Multi-line Where field, sponsored by OpenGate . Enabled as a configuration option in the Extension Manager.
• Danish translation thanks to Peter Klein.
• Better backend form layout thanks to Peter Klein.
• Tutorial section on integration with Powermail thanks to Peter Klein.
• All template markers can be inserted directly into the template (suggested by Kasper Ligaard), but it is still recommended to keep them inside the defined subparts (like ###ONE_DAY_EVENT### ), to make use of the different event type dependent templates.
• Added parameters automaticAdjustDate and adjustDate, so dates can be changed independently of times.
• Corrected bug where the event selector would not work correctly, thanks to Olaf Jörding.
• Changing language labels through TypoScript is now possible, thanks to Rene Rossi.
• German backend translation, thanks to Sebastian Wramba.
• Now on Forge: http://forge.typo3.org/projects/show/extension- mbl_newsevent
• Moved all TypoScript configuration into static template, making it easier to correct the issue where ICS would not show if TypoScript for ICS was included before the main extension TypoScript.
• Somewhat higher Outlook compatibility.

Changes in version 2.2.0¶

• All news with events can be hidden by setting the hideEvents TypoScript parameter to TRUE.
• Additional German translation, thanks to Igor Reitmair (typo3expert.at).
• Fixed addtionalHeaders so it sends correct info for ICS.

Changes in version 2.3.0¶

• Download ICS files for individual events (using the list mode ICS_SINGLE). Link is inserted using the ###EVENT_SINGLE_ICS_LINK### marker. Sponsored by Igor Reitmair (typo3expert.at) .
• Now using tt_news' local\_cObj property correctly in extraItemMarkerProcessor() .
• If there is no organizer, organizer info is hidden in ICS files.
• Removed unused TypoScript parameter ics.fileName

Changes in version 2.4.0¶

• Displays number of registered / max registrations etc. The registration count is picked from a custom DB table, either as the result of a COUNT(*) operation or by finding the number of registered in a specific field. What's the right configuration depends on your event registration system's setup.
• stdWrap for labels. (Thanks to Christoph Bauer)
• Updated manual FAQ with info about XML/RSS handling. (Thanks to Vincent Kessels)
• Improved handling of displayEventUntilEnd (Thanks to Bernd Braemer)

Changes in version 2.4.1¶

Updated manual regarding tt_news compatibility.

Changes in version 2.5.0¶

• Added TYPO3 6.2 compatibility (sponsored by zeitraum gmbh )
• Improved all day events for ICS. (Changes in the ICS template.)
• Fixed bug where the link to the news article would not appear properly in ICS.
• Improved compatibility with other tt_news extensions (thanks to Victor Livakovsky)
• ###EVENT_ORGANIZER_INFO### inserts the content of the subpart ###EVENT_ORGANIZER_WRAP###. This improves the display of events without organizer.
• ###EVENT_LOCATION_INFO### inserts the content of the subpart ###EVENT_LOCATION_WRAP###. This improves the display of events without location.
• ###EVENT_PRICE_INFO### inserts the content of the subpart ###EVENT_PRICE_WRAP###. This improves the display event price.
• ###EVENT_WHERE### is deprecated. Use ###EVENT_LOCATION### instead.
• ###EVENT_WHERE_TEXT### is deprecated. Use ###EVENT_LOCATION_TEXT### instead.
• New tt_news_v3_template_newsevent.html template file for tt_news version 3+.

Changes in version 2.5.1¶

Fixed bug where ###EVENT_SELECTOR_LIST### did not work.

Changes in version 7.6.0¶

• Compatibility with tt_news 7.6
• Compatibility with TYPO3 7 LTS

EXT:News Event - 14