Newer
Older
## Upgrade from ```9.5.x``` to ```9.6.x```
- Filters are now visible when using the option ```settings.enableFilter``` in the **Overview** plugin.
Stefan Galinski
committed
# Upgrade from ```8.x.x``` to ```9.x.x```
- Dropped TYPO3 8 support
# Upgrade from ```7.x.x``` to ```8.x.x```
## Migrate the Authors
A new author table was introduced, so you need to execute the following migration wizard.
```Migrate all news authors to the new author table for each site root.```
## Add the routing for the new author news plugin
Add this routeEnhancer configuration to your config.yaml.
```
routeEnhancers:
NewsByAuthor:
type: Extbase
extension: SgNews
plugin: NewsByAuthor
routes:
- routePath: '/{authorTitle}'
_controller: 'NewsByAuthor::list'
_arguments: { 'authorTitle': authorId }
defaultController: 'NewsByAuthor::list'
aspects:
authorTitle:
type: PersistedAliasMapper
tableName: tx_sgnews_domain_model_author
routeFieldName: path_segment
```
# Upgrade from ```6.x.x``` to ```7.x.x```
In Version 7, we rewrote all included JavaScript to ES6 modules. This means that they won't be included in your site automatically when you install the extension.
## Importing the sgnews bundle in your main project
sg_news offers a front-package that imports all sub modules and initilaizes them correctly. You can import this in your bundle like that:
```js
import SgNews from 'sgnews';
new SgNews();
```
### Mapping ```sgnews``` to the extension JavaScript
In order for your module bundler to find the ```sgnews``` package, you need to add the path to your configuration. If you are using the SGC, you can add the following to your ```.sgc-config.json```
```js
{
"js": {
"libraryPaths": [
...
"./web/typo3conf/ext/sg_news/Resources/Public/JavaScript/"
]
}
}
```
Stefan Galinski
committed
## Migration to TYPO3 9
Stefan Galinski
committed
Unfortunately TYPO3 fucked it completely up. There are several issues with translations afterwards that can only be
solved by doing manual work.
### Migrate Tags
All tags must be synchronized with the translated pages as pages_language_overlay was dropped and TYPO3 didn't handled this
properly. If you don't use tags, you are a lucky guy. If you used tags, you can now be lucky. Just execute the
following SQL.
```
# Hole alle Tags von Seiten, welche Übersetzungen haben mit zugehörigem Page-Record der Übersetzung
# UND synchronisiere die neuen Tags für die Übersetzungen
INSERT INTO sys_category_record_mm (uid_local, uid_foreign, tablenames, fieldname, sorting, sorting_foreign)
SELECT sys_category_record_mm.uid_local, pages.uid, 'pages', 'tx_sgnews_tags', sys_category_record_mm.sorting, sys_category_record_mm.sorting_foreign FROM pages, sys_category_record_mm WHERE pages.l10n_parent IN (
SELECT uid_foreign FROM sys_category_record_mm WHERE fieldname = 'tx_sgnews_tags'
) AND sys_category_record_mm.uid_foreign = pages.l10n_parent;
```
### Migrate Images
All images must be resynchronized in all translations as images must always be carefully translated now in ALL records
and not only pages. Unfortunately there is no automatic approach. You must do it on your own. To simplify the process,
you should use mass badge processing offered by TYPO3.
1) Open the list view
2) Open the news category
3) Click on the table and the search icon in the top bar and choose 3 levels
4) All news should be listed for the category (you can also do that for the overview page if all news are grouped below)
5) At the very bottom, choose the higlight and teaser image fields now.
6) Click on the edit icon at the table header for hightlight images
7) Synchronize all images with the provided button and save
8) Do that now also for the teaser images and ALL pagination pages as TYPO3 loads only one page after the other.