Releases 

Currently the source code is available at Github.

What does it do? 

This extension is mainly used to display weather data received from openweathermap.org and weather alerts received from Deutscher Wetterdienst. The extension however is designed to work with every weather API by creating your own Symfony console command (the pattern used by weather2 itself since version 6) and mapping the returned values to the existing database structure. Moreover it is possible to organize records using storage pages and a custom identifier for each record.

Screenshots current weather 

Displaying basic information 

Displaying more information 

Screenshots weather alert 

Display basic information 

Display more information 

Adding a new plugin to display weather reports 

To add a new plugin just create a new content element, choose insert plugin and select Current Weather under plugin. Now you can select the desired measure unit and record identifier to display records.

Adding a new plugin to display weather alerts 

To add a new plugin just create a new content element, choose insert plugin and select Weather Alerts as plugin. Now you can select which regions, alarm level and alarm types should be displayed. Additionally you can select the record storage page.

Render weather reports and alerts inside a fluid template 

Maybe you want to include the plugins inside a Fluid template without a plugin. Important: include the static template of weather2 inside the root page.

# weather reports
lib.weather2_currentweather = USER
lib.weather2_currentweather {
  userFunc = TYPO3\CMS\Extbase\Core\Bootstrap->run
  extensionName = Weather2
  pluginName = Currentweather
  vendorName = JWeiland

  settings =< plugin.tx_weather2.settings
  persistence =< plugin.tx_weather2.persistence
  view =< plugin.tx_weather2.view

  # override the settings in here or change them in plugin.tx_weather2
  settings {
    # possible values: Metric | Imperial | Isou
    measureUnits = Metric
    # possible values: The "name" argument you set for the "weather2:fetch:openWeatherMap" command
    selection = Reutlingen
  }
}

<f:cObject typoscriptObjectPath="lib.weather2_currentweather" />

Render weather alerts inside a fluid template 

Add the following TypoScript to your setup:

EXT:site_package/Configuration/TypoScript/setup.typoscript

# weather alerts
lib.weather2_weatheralert = USER
lib.weather2_weatheralert {
  userFunc = TYPO3\CMS\Extbase\Core\Bootstrap->run
  extensionName = Weather2
  pluginName = Weatheralert
  vendorName = JWeiland

  settings =< plugin.tx_weather2.settings
  persistence =< plugin.tx_weather2.persistence
  view =< plugin.tx_weather2.view

  # override the settings in here or change them in plugin.tx_weather2
  settings {
    warningTypes = 0,1,2,3,4,5,6,7,8,9,10,11,12
    warningLevels = 0,1,2,3,4,5,10,20
    # warnCells = <uid of your warn cell record> (multiple comma separated)
    warnCells = 215
    showPreliminaryInformation = 1
  }
}

Copied!

Use the following snippet in your Fluid template:

EXT:site_package/Resources/Private/Templates/Page/Default.html

<f:cObject typoscriptObjectPath="lib.weather2_weatheralert" />

Copied!

Next step 

Configure extension.

View 

Persistence 

Settings 

Storage page 

1. Create a storage page
2. Refer to it in the recordStoragePage argument when you set up the Scheduler task for the relevant console command (see Console commands overview)
3. Also refer to it in the plugin

Console commands overview 

Since version 7.0.0, weather2 no longer ships its own Scheduler task types. All data fetching is implemented as Symfony console commands instead. To run one regularly (or once), go to the scheduler module, add a new task, choose the task type Execute console commands (TYPO3CMSSchedulerTaskExecuteSchedulableCommandTask), select the desired weather2 command from the list, and fill in its arguments in the form fields that appear below.

The following three commands are available. They are listed in the order in which they should be set up.

Current weather (weather report) 

How do I get set up? 

1. Create a new openweathermap.org account and copy your API key
2. Download the extension from the TYPO3 Extension Repository
3. Enable the scheduler extension in your TYPO3 installation if not already done
4. Go to the scheduler module and add a new task of type Execute console commands, then select the command weather2:fetch:openWeatherMap (see Console commands overview)
5. Fill in the command's arguments. Please note that the name argument is later used to only display this specific record
6. Create a new content element with the weather extension plugin selected
7. Select the measure units and city to display
8. Add the extension template file to your template
9. Enjoy! ;)

Weather alerts 

Update from 6.x to 7.0 

The three console commands were renamed to be shorter and to make it clear which one fetches warnings and which one only fetches the region reference data:

• weather2:fetch:deutscherWetterdienstAPI is now weather2:fetch:dwdAlerts
• weather2:fetch:warnCellsFromDeutscherWetterdienstAPI is now weather2:fetch:dwdWarnCells
• weather2:fetch:fromOpenWeatherAPI is now weather2:fetch:openWeatherMap

If you already have Scheduler tasks of type Execute console commands referencing one of the old command identifiers, edit each task and re-select the command under its new name - the old identifier no longer exists and the task will fail otherwise. See Console commands overview for the arguments of each command and whether it should be single or recurring.

Update from 5.x to 6.0 

Added TYPO3 13 compatibility. Removed all weather2 Scheduler task types and replaced them with Symfony console commands. Your existing weather2 Scheduler tasks will no longer run and should be deleted. For each one, create a new task of type Execute console commands instead, and select the matching weather2 command (weather2:fetch:fromOpenWeatherAPI, weather2:fetch:warnCellsFromDeutscherWetterdienstAPI or weather2:fetch:deutscherWetterdienstAPI - renamed again in version 7.0, see above). There is an upgrade wizard available with this extension to convert the older list type plugins to custom CType.

Update from 4.x to 5.0 

Added TYPO3 12 compatibility. Removed older version compatibility. Removed dependency with static_info_tables. Removed ObjectManager usage from scheduler tasks, so after upgrading the extension it is better to remove the old tasks and recreate the tasks, because the old serialized version is saved in the database.

Update from 3.x to 4.0.0 

Added TYPO3 11 compatibility. Removed TYPO3 9 compatibility.

We have removed all TYPO3 columns from ext_tables.sql. Please execute the database compare to update the database columns.

Execute Flush Cache in the maintenance section of TYPO3 to update the dependency injection cache.

We require recordStoragePid as int in the weather2 scheduler task. It may happen that a call to setPid() will fail, because it is not an int. That happens because all scheduler tasks, including their earlier variable types, are stored serialized in the scheduler. While unserializing, the old type (string) will not match the current type (int) anymore. So please delete that task and create that task again. Sorry, no upgrade wizard is available for that operation.

Update from 2.x to 3.0.0 

Added TYPO3 10 compatibility. Removed TYPO3 8 compatibility.

Nothing to do.

Update from 2.x to 2.0.4 

Because of a security patch of TYPO3, all of our weather2 scheduler tasks can no longer be unserialized. For you it is not possible anymore to delete, modify or start any task, as you can not open the scheduler module. Furthermore no task will be executed anymore by cronjob. Please visit the Upgrade module of TYPO3 and execute our upgrade wizard to update our tasks in the database.

Update from 1.x to 2.x 

There are breaking changes if you're updating weather2 from 1.x to 2.x. This chapter is about how to fix those breaking changes.

1. Update weather2 using Composer or the Extension Manager.
2. If you're using Composer you may need to disable and enable the extension using the Extension Manager or using the database analyzer to get the new database structure.
3. Clear all caches.
4. Open the scheduler module.
5. Edit all tasks of type Call openweathermap.org api. Directly save them after clicking edit. You don't need to change any fields inside here.
6. Remove all tasks of type Get regions from Deutscher Wetterdienst. They should have a red background because they no longer exist.
7. Either create a warn cell record manually OR create a task of type Get warn cell records from Deutscher Wetterdienst, set it as single and execute it one time.
8. Edit all tasks of type Get weather alerts from Deutscher Wetterdienst and select the cities/locations you want to fetch. Then save those tasks.
9. Edit all plugins with list type weather2_weatheralert (Weather Alerts) and select the cities/locations you want to display. Also check out the new setting Show preliminary information.
10. Clear frontend caches.

Add custom providers 

Feel free to add custom API providers for weather reports or weather alerts. You can add them using your own extension. Write your own Symfony console command, following the pattern of weather2's own commands (see Console commands overview), and use the models JWeilandWeather2DomainModelCurrentWeather for weather reports and JWeilandWeather2DomainModelWeatherAlert for weather alerts. Add new records using the Extbase PersistenceManager or the TYPO3 DataHandler. Register your command as a console.command service so it can be scheduled through TYPO3's Execute console commands Scheduler task, the same way as weather2's own commands.

Version 7.0.1 

• [BUGFIX] Add missing "target-language" attribute to German translation files
• [TASK] Update XLIFF files to version 1.2 for improved compatibility

Version 7.0.0 

• [TASK] Fetch a localized weather description from OpenWeatherMap
• [TASK] Add TYPO3 14 compatibility
• [TASK] Remove TYPO3 13 compatibility

Version 6.1.4 

• [BUGFIX] Replace hardcoded tab labels with localized labels in tt_content

Version 6.1.3 

• [BUGFIX] Assign wind direction to correct array key

Version 6.1.2 

• [TASK] Updated wizard title with [extension] name format

Version 6.1.1 

• [BUGFIX] Update testing directory

Version 6.1.0 

• [TASK] Fixed TCA configuration issues
• [BUGFIX] Fixed DB Analyser issue

Version 6.0.0 

• Full TYPO3 13 compatibility
• Dropped older version support
• Removed all scheduler tasks, replaced with Symfony console commands
• Updated test suite and removed old test suite configuration files

Version 5.0.0 

• [BUGFIX] Backported fixed DB Analyser issues

Version 5.0.0 

• Full TYPO3 12 compatibility
• Dropped support for TYPO3 10 and below
• Removed dependency on static_info_tables
• Refactored all scheduler tasks to remove ObjectManager usage
• Important: old scheduler tasks must be deleted and recreated manually

Version 4.0.0 

• TYPO3 11 LTS support
• Dropped support for TYPO3 9
• Removed TYPO3-specific SQL columns from ext_tables.sql
• Important: clear the DI cache using the maintenance module in the backend
• Fix: only numeric PIDs are now allowed in scheduler tasks - delete old ones

Version 3.0.0 

• TYPO3 10 support introduced
• TYPO3 8 support removed
• Smooth upgrade - no manual changes needed

Version 2.0.4 

• TYPO3 core change fix: unserializing scheduler tasks failed
• Required manual fix via upgrade wizard in the TYPO3 backend

Version 2.0.0 

• Major extension refactoring
• Scheduler task and TypoScript plugin handling improved
• Upgrade steps are in the documentation

Version 1.0.0 

• Initial stable release with basic support for the openweathermap.org API
• Support for weather alerts via Deutscher Wetterdienst (DWD)
• Includes TypoScript configuration for widgets and plugin rendering