Is Event 

This checkbox defines if a news item is rendered as event item. Only if set, the additional event fields are displayed!

Event end 

An optional end date can be defined for an event. If set, the event will be shown for every day starting with the start time (which is set in the regular Date & time field) until the given end date.

Full day 

This checkbox can be used to style events in a different way. There is no additional functionality implemented.

Organizer 

This relation can be used to add an organization to an event.

The organizer record itself contains only the basic fields:

• Title
• Description

Location 

This relation can be used to add a location to an event.

The location record itself contains the following fields:

• Title
• Description
• Street, ZIP, City, State, Municipality, Country
• Phone, Email
• Latitude & Longitude
• Link

The country is stored as its ISO 3166-1 alpha-2 code, e.g. AT. None of the address fields are rendered by the templates shipped with the extension, they are meant to be used in your own templates.

Organizer Simple 

A text field to set an organizer without using a relation.

Location Simple 

A text field to set a location without using a relation.

New news records as event 

By using the following code block in the Page TsConfig it is possible to hide the checkbox "Is event" and have new news records created as event:

tx_news.newRecordAsEvent = 1
TCEFORM.tx_news_domain_model_news.is_event {
  disabled = 1
}

The "hidden" checkbox looks different 

Location and organizer records no longer spell out the system columns the Core creates from the table's ctrl capabilities. One of them is hidden, which now uses the Core default: an inverted toggle labelled Enable instead of the previous Hide. It is the same widget every other Core table shows, and it stores the same value.

Events spanning several months are listed in every one of them 

A plugin whose Event Restriction is set to No constraint shows events next to plain news records. Its month and year range used to come straight from EXT:news, which matches on the start date alone:

datetime >= <first day of the month> AND datetime <= <last day of the month>

An event running from January to October therefore appeared in January and nowhere else, because that is where it starts. Only Only events used the range of this extension, which pairs the start date with event_end and matches every month an event covers.

The two behave the same now, so an event is listed in every month it runs through. In a calendar that is the point of the change, the event finally shows up on the days it actually runs. In a plain list the same event now appears in several months instead of one, which can push other records onto a later page when the list is paginated or limited by settings.limit.

Nothing changes for Only events, which already worked this way, or for No events, which never looks at event_end. To keep the old result for a single plugin, set it to No events and put the events into a second plugin.

See issue #198.

Address fields on location records 

A location record now carries a full address: street, ZIP, city, state, municipality, country, phone and email, grouped in an Address and a Contact palette. The country is a real country selection - TCA type country on TYPO3 14, the same list built from the Country API on 13 - and stores the ISO 3166-1 alpha-2 code.

None of the fields are rendered by the shipped templates. They are meant for your own templates and reachable through the matching getters on GeorgRingerEventnewsDomainModelLocation, so {newsItem.location.city} works right away.

See issue #223.

Support for TYPO3 14 

One branch now serves TYPO3 13.4 LTS and 14. The month view runs on both: TypoScriptFrontendController and the frontend.controller request attribute were removed in v14, so NewsController::monthAction() reads the page id from the frontend.page.information attribute instead. The ViewHelpers and the administration module were adjusted the same way.

Broken links in locations and organizers are reported 

The Link field of a location and of an organizer is now checked by linkvalidator. Both fields always used TCA type link with a typolink soft reference, which is the prerequisite, but linkvalidator only looks at fields listed in mod.linkvalidator.searchFields - and that list was never provided, so broken links went unreported.

The extension ships the registration in Configuration/page.tsconfig, which TYPO3 picks up automatically for every active package:

mod.linkvalidator.searchFields {
    tx_eventnews_domain_model_location = link
    tx_eventnews_domain_model_organizer = link
}

Existing broken links show up on the next run of the linkvalidator report or its scheduler task. To leave a table out, unset it in your own page TSconfig.

See issue #214.

Test suite and CI 

The extension now ships a container based test runner, Build/Scripts/runTests.sh, together with unit and functional test suites and GitHub Actions workflows covering TYPO3 13 and 14. Relevant if you contribute; runTests.sh -h lists what it can do.