http://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692020-06-17T08:22:22ZTYPO3 ForgeTYPO3 Core - Task #91663: PersistedAliasMapper can only resolve with fixed field "uid"http://forge.typo3.org/issues/91663?journal_id=4268952020-06-17T08:22:22ZSven Erens
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/426895/diff?detail_id=353686">diff</a>)</li></ul> TYPO3 Core - Task #91663: PersistedAliasMapper can only resolve with fixed field "uid"http://forge.typo3.org/issues/91663?journal_id=4281192020-07-29T08:57:50ZStefan P
<ul></ul><p>I'll join this request. We have the same issue. We have a routing-enabled table that is not in TCA (its rows are fully autogenerated by custom PHP and not used in Extbase or whatever) and has neither the <code>uid</code> nor <code>pid</code> field.</p>
<p>I also extended the core aspect and overwrote all methods to fetch from the correct fields.</p>
<p>In our case the primary (id) field is also no <code>int</code>, but a <code>varchar</code>.</p> TYPO3 Core - Task #91663: PersistedAliasMapper can only resolve with fixed field "uid"http://forge.typo3.org/issues/91663?journal_id=4796082022-11-03T14:02:17ZOliver Haderoliver.hader@typo3.org
<ul><li><strong>Sprint Focus</strong> set to <i>On Location Sprint</i></li></ul> TYPO3 Core - Task #91663: PersistedAliasMapper can only resolve with fixed field "uid"http://forge.typo3.org/issues/91663?journal_id=4982522023-08-02T13:04:57ZBenni Mackbenni@typo3.org
<ul><li><strong>Sprint Focus</strong> deleted (<del><i>On Location Sprint</i></del>)</li></ul>