[BUGFIX] Fix references (#967)

Preparation for switch to PHP-based rendering

The guides are more strict in using interlinks then sphinx

(cherry picked from commit 19fde0a)

Documentation/ColumnsConfig/Type/File/Properties/Appearance.rst

@@ -87,4 +87,4 @@ appearance
     elementBrowserEnabled (boolean)
         Hides or displays the element browser button in inline records
 
-    This property can also be overridden by :ref:`page TSconfig <tceform>`.
+    This property can also be overridden by :ref:`page TSconfig <t3tsconfig:tceform>`.

Documentation/ColumnsConfig/Type/Flex/Index.rst

@@ -5,7 +5,7 @@
 FlexForm field
 ==============
 
-Renders a :ref:`FlexForm <flexforms>` element. Essentially, this consists in a
+Renders a :ref:`FlexForm <t3coreapi:flexforms>` element. Essentially, this consists in a
 hierarchically organized set of fields which will have their values saved into a
 single field in the database, stored as XML.
 

Documentation/ColumnsConfig/Type/Flex/Properties/DsPointerFieldSearchParent.rst

@@ -10,10 +10,10 @@ ds\_pointerField\_searchParent
     Beginning with TYPO3 v12 you can migrate to PSR-14 events to manipulate the
     data structure lookup logic:
 
-    *   :ref:`AfterFlexFormDataStructureIdentifierInitializedEvent`
-    *   :ref:`AfterFlexFormDataStructureParsedEvent`
-    *   :ref:`BeforeFlexFormDataStructureIdentifierInitializedEvent`
-    *   :ref:`BeforeFlexFormDataStructureParsedEvent`
+*   :ref:`t3coreapi:AfterFlexFormDataStructureIdentifierInitializedEvent`
+*   :ref:`t3coreapi:AfterFlexFormDataStructureParsedEvent`
+*   :ref:`t3coreapi:BeforeFlexFormDataStructureIdentifierInitializedEvent`
+*   :ref:`t3coreapi:BeforeFlexFormDataStructureParsedEvent`
 
 ..  confval:: ds_pointerField_searchParent
 

Documentation/ColumnsConfig/Type/Flex/Properties/DsPointerFieldSearchParentSubField.rst

@@ -10,10 +10,10 @@ ds\_pointerField\_searchParent\_subField
     Beginning with TYPO3 v12 you can migrate to PSR-14 events to manipulate the
     data structure lookup logic:
 
-    *   :ref:`AfterFlexFormDataStructureIdentifierInitializedEvent`
-    *   :ref:`AfterFlexFormDataStructureParsedEvent`
-    *   :ref:`BeforeFlexFormDataStructureIdentifierInitializedEvent`
-    *   :ref:`BeforeFlexFormDataStructureParsedEvent`
+*   :ref:`t3coreapi:AfterFlexFormDataStructureIdentifierInitializedEvent`
+*   :ref:`t3coreapi:AfterFlexFormDataStructureParsedEvent`
+*   :ref:`t3coreapi:BeforeFlexFormDataStructureIdentifierInitializedEvent`
+*   :ref:`t3coreapi:BeforeFlexFormDataStructureParsedEvent`
 
 ..  confval:: ds_pointerField_searchParent_subField
 

Documentation/ColumnsConfig/Type/Flex/Properties/DsTableField.rst

@@ -10,10 +10,10 @@ ds\_tableField
     Beginning with TYPO3 v12 you can migrate to PSR-14 events to manipulate the
     data structure lookup logic:
 
-    *   :ref:`AfterFlexFormDataStructureIdentifierInitializedEvent`
-    *   :ref:`AfterFlexFormDataStructureParsedEvent`
-    *   :ref:`BeforeFlexFormDataStructureIdentifierInitializedEvent`
-    *   :ref:`BeforeFlexFormDataStructureParsedEvent`
+*   :ref:`t3coreapi:AfterFlexFormDataStructureIdentifierInitializedEvent`
+*   :ref:`t3coreapi:AfterFlexFormDataStructureParsedEvent`
+*   :ref:`t3coreapi:BeforeFlexFormDataStructureIdentifierInitializedEvent`
+*   :ref:`t3coreapi:BeforeFlexFormDataStructureParsedEvent`
 
 ..  confval:: ds_tableField
 

Documentation/ColumnsConfig/Type/Inline/Examples.rst

@@ -133,20 +133,20 @@ type inline** - as it is a container.
          {
              public function render()
              {
-                 $fieldName = $this->data['fieldName'];                
+                 $fieldName = $this->data['fieldName'];
                  $result = $this->initializeResultArray();
 
                   // Add fieldInformation only for this field name
-                  //   this may be changed accordingly                                  
+                  //   this may be changed accordingly
                   if ($fieldName !== 'my_new_field') {
                       return $result;
                   }
-                  
+
                   $text = $GLOBALS['LANG']->sL(
                           'LLL:EXT:my_example/Resources/Private/Language/'
                           . 'locallang_db.xlf:tt_content.fieldInformation.demo'
                   );
-                  
+
                   $result['html'] = $text;
                   return $result;
              }
@@ -198,6 +198,6 @@ type inline** - as it is a container.
 
    *  :ref:`['ctrl']['container'] <ctrl-reference-container>`
    *  How to create custom fieldInformation, fieldControl or fieldWizard in
-      :ref:`FormEngine <FormEngine-Rendering-NodeExpansion>` chapter (TYPO3
+      :ref:`FormEngine <t3coreapi:FormEngine-Rendering-NodeExpansion>` chapter (TYPO3
       Explained)
    *  :ref:`fieldInformation <tca_property_fieldInformation>` property

Documentation/ColumnsConfig/Type/Password/Properties/PasswordPolicy.rst

@@ -13,7 +13,7 @@ passwordPolicy
     :type: string
     :Scope: Display, Proc.
 
-    This option assigns a :ref:`password policy <password-policies>` to fields
+    This option assigns a :ref:`password policy <t3coreapi:password-policies>` to fields
     of the type `password`. For configured fields, the password policy validator
     will be used in :ref:`DataHandler <t3coreapi:tce-database-basics>` to ensure,
     that the new password complies with the configured password policy.

Documentation/ColumnsConfig/Type/Select/Properties/SelectTreeConfig.rst

@@ -34,7 +34,7 @@ treeConfig
       configuration by using the `###SITE:###` syntax.
 
       This property can also be set by page TSconfig, see
-      :ref:`pagetsconfigtceformconfigtreeconfig`
+      :ref:`t3tsconfig:pagetsconfigtceformconfigtreeconfig`
 
       Example: