What does it do?

The extension were build to manage firefighter operations in a TYPO3 website. Quite originally the Freiwillige Feuerwehr der Stadt Thale, long time ago, got this extension from me in a TYPO3 website. In the meanwhile someone else takes care of it and this one thinks Wordpress is great. Well, what to say ;-). If it makes people happy, you're welcome. But the download numbers of the extension also suggest me, that there are other TYPO3 sites with need for this extension. But that's just by the way.

The data for operations are managed in TYPO3 Backend by editors. Many detailed information e.g. used vehicles, resources, assistance and more are possible.

This extension can be used for other institutions like THW, DRK, Police or e.g. a Security Agency too.

Different views in Frontend are possible.

Frontend Screenshots

Here are some screenshots of the frontend templates. Styles used from the Site Package fire department optimized for the Fluid templates in "operations".

Frontend list view with filter and pagination

Frontend single view of operation data

Frontend list view of resources

Frontend list view of vehicles

Frontend statistic view grouped by type and year

Github Issue Tracker

Create an issue here operations on github if you have problems.

Slack

The fastest way to get support is the dedicated channel on slack to get in touch with other users and/or me.

The url is: https://typo3.slack.com/messages/ext-operations/

If you have Slack already installed, just looking for the Slack Channel ext-operations in TYPO3 workspace.

Sponsoring

If you need a feature which is not yet implemented, feel free to contact me.

Change the templates paths in TypoScript constants

Here an example for TypoScript constants to change the paths to Fluid templates.

plugin.tx_operations {
        view {
                templateRootPath = EXT:your_site_package/Resources/Private/Extensions/operations/Templates/
                partialRootPath = EXT:your_site_package/Resources/Private/Extensions/operations/Partials/
                layoutRootPath = EXT:your_site_package/Resources/Private/Extensions/operations/Layouts/
        }
}

Include static TypoScript

The extension come with some TypoScript which needs to be included. You can include TypoScript in different ways. The preferred way should be include TypoScript from Extensions in your Site Package. See Include TypoScript in Site Package

The old way is also possible. Include TypoScript of the Extension in your root TypoScript Template (sys_template) in database.

1. Select the root page of your site.
2. Switch to the Template module and select Info/Modify.
3. Press the link Edit the whole template record and switch to the tab Includes.
4. Select Operations (operations) at the field Include static (from extensions):

Use Constant Editor

After including operations TypoScript there are some settings in TYPO3 Constants Editor available. The most important setting to use the extension can be set here.

plugin.tx_operations {
  # This is the uid of your sysfolder where the operation data in backend is.
  persistence.storagePid = 45
  settings {
    # This is the uid of the single view page for operations.
    operationSinglePid =
    # This is the uid of the single view page for vehicles.
    vehicleSinglePid =
    # This is the uid of the single view page for resources.
    resourceSinglePid =
  }
}

Whole list of TypoScript Settings

You can find the whole list of TypoScript settings for operations in those file:

Configuration/TypoScript/setup.typoscript

Settings starting here:

plugin.tx_operations {
   settings {
      …
   }
}

Different content types

Display operations statistics

Add a content element type "Operation Statistics view". Set category if you want and the last years to show. Of courses, storage pid should be already set in TypoScript. If not you have to set this in plugin settings too.

This will show you all operations grouped by type and year depending on the settings you did.

The setting "lastYears" define how many years descending from now should be respected for the statistics. It's the same setting as in the normal list and can be overridden directly in the "Operation Statistics" plugin. Years without any operations will be ignored.

Change JavaScript for statistics

If you need adapting the chart, please use your own JavaScript file and change the path to it in template file: Resources/Private/Templates/Operation/Statistics.html

<f:section name="FooterAssets">
    <!-- chart library -->
    <script src="{f:uri.resource(path: 'Js/Chart.bundle.js')}"></script>
    <!-- change path to your own js file if you need -->
    <script src="{f:uri.resource(path: 'Js/OperationsChart.js')}"></script>
</f:section>

I suggest to put those things in an own Site Package. Change the path in your own template files. using your own template files is described here Templates.

Using Categories

You can use categories to organize your operations. E.g. Create a structure with a main fire department and sub departments. Select categories in Operations plugin to control the result of list view or statistic view in frontend.

You don't need those main department and sub department stuff? Ok, use the categories for whatever you want or ignore it.

Usage in your Site Configuration

Url routing for TYPO3 Extensions are explained more detailed here Advanced routing configuration. That's also needed to to use nice url's for single views of operations, vehicles, resources and the pages in list with pagination.

More information about Routing: Speaking Urls

You don't know about the Site Configuration? Read here: Sitehandling

Here is an example RouteEnhancer configuration that I'm using in my develop environment.

routeEnhancers:
  OperationsPlugin:
    # set "limitToPages" for route enhancer directly in your site config
    type: Extbase
    extension: Operations
    plugin: List
    routes:
      -
        routePath: '/{localized_page}-{page}'
        _controller: 'Operation::list'
        _arguments:
          page: currentPage
      -
        routePath: '/{operation_title}'
        _controller: 'Operation::show'
        _arguments:
          operation_title: operation
      -
        routePath: '/{vehicle_title}'
        _controller: 'Vehicle::show'
        _arguments:
          vehicle_title: vehicle
      -
        routePath: '/{resource_title}'
        _controller: 'Resource::show'
        _arguments:
          resource_title: resource

    defaultController: 'Operation::list'
    defaults:
      page: '1'
    requirements:
      page: \d+
    aspects:
      page:
        type: StaticRangeMapper
        start: '1'
        end: '200'
      operation_title:
        type: PersistedAliasMapper
        tableName: tx_operations_domain_model_operation
        routeFieldName: path_segment
      vehicle_title:
        type: PersistedAliasMapper
        tableName: tx_operations_domain_model_vehicle
        routeFieldName: path_segment
      resource_title:
        type: PersistedAliasMapper
        tableName: tx_operations_domain_model_resource
        routeFieldName: path_segment
      localized_page:
        type: LocaleModifier
        default: 'page'
        localeMap:
          - locale: 'de_DE.*'
            value: 'seite'

This example is included in TYPO3 Extension fire_department in folder: Configuration/Yaml/Routes/Operations.yaml. Use an @import statement in your site config and set limitToPages:

imports:
  - { resource: "EXT:fire_department/Configuration/Yaml/Routes/Operations.yaml" }
routeEnhancers:
  OperationsPlugin:
    limitToPages: [5,7,9]

8.2.0

Some small improvements on code quality checks and support now postgres and sqlite db systems.

8.1.0

TYPO3 13 compatibility

Update to 8.0.0

This version brings TYPO3 12 compatibility and retains compatibility with TYPO3 11. So operations currently runs with both LTS versions of TYPO3.

The hard dependency to Georg Ringer's numbered_pagination has been removed. There was no 12 compatible version of it available. Maybe there won't be one, because the TYPO3 core has now its own solution. For TYPO3 11 installations this means that you have to take care of the installation of the numbered_pagination by yourself. Depending on the TYPO3 version, operations selects either the NumberedPagination class (if exists) or the newer SlidingWindowPagination class. If neither is available, then SimplePagination is used. In TypoScript there is the possibility to override this and using another pagination class.

plugin.tx_operations {
   settings {
      paginate {
         class = Vendor/YourOwn/PaginationClass
      }
   }
}

Update to 7.1.0

• Before this update you always had a limit for operations data. That is not useful in statistics view. Now there is no limit by default for statistics. You can deactivate this to get back the old behaviour with the TypoScript setting noLimitForStatistics = 0.
• Now the extension "numbered_pagination" by georg ringer is used for the pagination. Check the TypoScript settings and Fluid Templates/Partials for changes. The extension will be installed automatically on composer based TYPO3 installations. If you have a non composer installation you have to install the extension by yourself manually before updating operations.
• The colors in operation type are now excluded on translations. You dont have to set a color for the translation.

Update to 7.0.0

This version is only running on TYPO3 11. In that version I fixed some small bugs and switch to some new features of TYPO3 11.

settings:
 operations:
   rootCategory: 2

Update to 6.x

Bugfix and maintenance release. Attention, Breaking Changes in this version! The new Pagination API of TYPO3 10 is used. The old Fluid Pagination Widget was removed. TypoScript setting maxNumberOfLinks not longer necessary and therefore removed. If you use the original template files for List and Search Action from operations version 5.1.x, then nothing should to do for you. If not, check if you changed one of the following files and have a look at the changes in original files:

• Resources/Private/Templates/Operation/List.html
• Resources/Private/Templates/Operation/Search.html
• Resources/Private/Partials/List/Pagination.html

If you configured the current page of pagination in the url (in the site configuration) you have to change the configuration for the page argument. It's not longer that @widget stuff. Have a look at the Speaking url example page in manual.

Slug behaviour was changed to unique. With an updated TYPO3 version it is now possible to use the sysfolder with operations data outside of the page tree. You can use one folder for multiple Sites in the same TYPO3 Instance. If you need uniqueInSite for your page, then you can switch that behaviour in the BE module "Settings" -> Extension Configuration.

Update to 5.1.0

Fix exception in list view of operations. Stand out just in TYPO3 10.

Improve translation handling with excluding some fields they don't need to be translated. Catgeories, resources, vehicles, lat and long, assistance, type, onlEld are the same in all languages.

Of course data for categories, resources, vehicles, assistance and type can be translated. Then translated field values are shown. Probably this depends on your language settings for sys_language_mode and sys_language_overlay.

fallbackType: strict
fallbacks: '0,1'

Update to 5.0.0

TYPO3 10 compatibility.

Update to 4.0.0

Complete refactoring of the templates to prepare it for using with the TYPO3 Site Package for fire department. With this package all views becomes default styles. Check frontend views.

Update to 3.2.2

Fix error if concatenation for JS and CSS files is activated in TYPO3.

Update to 3.2.0

tx_operations {
    categoryRootId = 4
}

Update to 3.1.0

Some little bugfixes. Add a new plugin to display statistics in frontend.

Update to 3.0.0 from a version below

plugin.tx_operations {
    persistence {
        storagePid = 99
        recursive = 2
    }
}

settings.listImgWidth -> settings.listMediaWidth
settings.showImgInList -> settings.showMediaInList

UPDATE tx_operations_domain_model_operation LEFT JOIN sys_file_reference ON sys_file_reference.uid_foreign=tx_operations_domain_model_operation.uid AND sys_file_reference.tablenames='tx_operations_domain_model_operation' AND sys_file_reference.fieldname='image' SET tx_operations_domain_model_operation.media=tx_operations_domain_model_operation.image, tx_operations_domain_model_operation.image=0, sys_file_reference.fieldname='media' WHERE tx_operations_domain_model_operation.image > 0;

UPDATE tx_operations_domain_model_vehicle LEFT JOIN sys_file_reference ON sys_file_reference.uid_foreign=tx_operations_domain_model_vehicle.uid AND sys_file_reference.tablenames='tx_operations_domain_model_vehicle' AND sys_file_reference.fieldname='image' SET tx_operations_domain_model_vehicle.media=tx_operations_domain_model_vehicle.image, tx_operations_domain_model_vehicle.image=0, sys_file_reference.fieldname='media' WHERE tx_operations_domain_model_vehicle.image > 0;

UPDATE tx_operations_domain_model_resource LEFT JOIN sys_file_reference ON sys_file_reference.uid_foreign=tx_operations_domain_model_resource.uid AND sys_file_reference.tablenames='tx_operations_domain_model_resource' AND sys_file_reference.fieldname='image' SET tx_operations_domain_model_resource.media=tx_operations_domain_model_resource.image, tx_operations_domain_model_resource.image=0, sys_file_reference.fieldname='media' WHERE tx_operations_domain_model_resource.image > 0;

Detailed changelog with git log

Clone the github repository and use following command to get a detailed list of the commits. Replace the version number in the command (2.0.2) with the number of version you are using before updating.

git log 2.0.2..HEAD --abbrev-commit --pretty='%ad %s (Commit %h by %an)' --date=short

Replace the word HEAD with another version, if you want to see the commits between this two versions.