From 1a5c10a26d59e5fe06a81344026775b86bffa88b Mon Sep 17 00:00:00 2001
From: Daniel Siepmann <coding@daniel-siepmann.de>
Date: Wed, 22 Apr 2020 18:43:46 +0200
Subject: [PATCH] Do not resolve pid relation

TYPO3 would otherwise run into trouble.
TYPO3 expects pid to be an integer or string.
Resolving pid due to a configured pid column via select or groups,
would result in an php array.
---
 Configuration/TCA/tx_tracking_pageview.php | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Configuration/TCA/tx_tracking_pageview.php b/Configuration/TCA/tx_tracking_pageview.php
index 5273a22..cfa9ad2 100644
--- a/Configuration/TCA/tx_tracking_pageview.php
+++ b/Configuration/TCA/tx_tracking_pageview.php
@@ -22,10 +22,10 @@ return [
         'pid' => [
             'label' => 'LLL:EXT:tracking/Resources/Private/Language/locallang_tca.xlf:table.pageview.pid',
             'config' => [
-                'type' => 'select',
+                // TODO: TYPO3 v10 does no longer allow to resolve PID relations, e.g. via select or group
+                // This will break internal PID handling.
+                'type' => 'input',
                 'readOnly' => true,
-                'renderType' => 'selectSingle',
-                'foreign_table' => 'pages',
             ],
         ],
         'crdate' => [