[TASK] Use correct issue reference in allowLanguageSynchronization do…

…cumentation Replace the Gerrit review ID by the related Forge ticket number. Resolves: #84150 Releases: master, 8.7 Change-Id: I53fe0699e74949b4c64020a955294b3a1ef3f726 Reviewed-on: https://review.typo3.org/56025 Reviewed-by: Mathias Brodala <mbrodala@pagemachine.de> Tested-by: TYPO3com <no-reply@typo3.com> Reviewed-by: Oliver Hader <oliver.hader@typo3.org> Tested-by: Oliver Hader <oliver.hader@typo3.org>
TYPO3 · Mar 6, 2018 · 7e00cef · 7e00cef
1 parent f337204
commit 7e00cef
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 6 deletions.
diff --git a/...1-PageRepositoryShouldFieldBeOverlaid.rst → ...8-PageRepositoryShouldFieldBeOverlaid.rst b/...1-PageRepositoryShouldFieldBeOverlaid.rst → ...8-PageRepositoryShouldFieldBeOverlaid.rst
@@ -1,10 +1,10 @@
 .. include:: ../../Includes.txt
 
 ============================================================
-Deprecation: #51291 - PageRepository shouldFieldBeOverlaid()
+Deprecation: #79658 - PageRepository shouldFieldBeOverlaid()
 ============================================================
 
-See :issue:`51291`
+See :issue:`79658`
 
 Description
 ===========
@@ -31,4 +31,4 @@ Migration
 
 The deprecated method returns TRUE in all cases, the call can be omitted.
 
-.. index:: Frontend, PHP-API
+.. index:: Frontend, PHP-API
diff --git a/...hronizedFieldValuesInLocalizedRecords.rst → ...hronizedFieldValuesInLocalizedRecords.rst b/...hronizedFieldValuesInLocalizedRecords.rst → ...hronizedFieldValuesInLocalizedRecords.rst
@@ -1,10 +1,10 @@
 .. include:: ../../Includes.txt
 
 ================================================================
-Feature: #51291 - Synchronized field values in localized records
+Feature: #79658 - Synchronized field values in localized records
 ================================================================
 
-See :issue:`51291`
+See :issue:`79658`
 
 Description
 ===========
@@ -43,4 +43,4 @@ A typical configuration looks like that:
 which stores a json string with field names and the values :code:`custom`, :code:`parent` or :code:`source` to
 specify if and from which record a single field gets its value.
 
-.. index:: Backend, Database, Frontend, PHP-API, TCA
+.. index:: Backend, Database, Frontend, PHP-API, TCA