Bug #33738
Indexing and deleting multilang records bugs
| Status: | New | Start date: | 2012-02-07 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| TYPO3 Version: | Has patch: | |||
| PHP Version: | Tags: | |||
| Votes: | 0 |
Description
There are issues while indexing and deleting multilanguage records.
1. Creating a new record in default language will create an index entry in the default language index AND all other language indexes.
I think there is no need for this.
2. Creating translations will save the item with the default uid in the language index. When the translation is deleted solr tries to find the record with the uid of the translated record. Solr can't find the indexed item because of the different uid and it will remain in the index.
3. Localized pages are indexed twice in language indexes.
This behaviour occurs in Version 2.5.0-dev
Regards
Heiko
History
Updated by Heiko Kromm over 1 year ago
In addition to
3. Localized pages are indexed twice in language indexes.
The indexed doc is except for <str name="contentHash"/> exactly the same. One entry has a contentHash and the other contentHash is empty.
The same doc for language 0 has only one doc with an empty contentHash.
Updated by Heiko Kromm over 1 year ago
Heiko Kromm wrote:
In addition to
3. Localized pages are indexed twice in language indexes.
The indexed doc is except for <str name="contentHash"/> exactly the same. One entry has a contentHash and the other contentHash is empty.
The same doc for language 0 has only one doc with an empty contentHash.
After a lot of digging I found that this is caused by the extension forcerealurls.