TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692020-06-17T17:35:27ZTYPO3 Forge
Redmine TYPO3 Core - Task #91667 (New): Optimization of workspace information dialoghttp://forge.typo3.org/issues/916672020-06-17T17:35:27ZManuel Selbachmanuel_selbach@yahoo.de
<p>The workspace information dialog shows some information, that could be optimized.</p>
<p>First of all there is the "t3_origuid" shown, which could be dropped IMO.</p>
<p>Furthermore there is the field "Columns" shown with one "translated" and readable column name and one with just a number which might be not that easy to be interpreted by an editor.</p>
<p>Please find both topics in the image:</p>
<p><img src="http://forge.typo3.org/attachments/download/35312/workspace-information-dialog.png" alt="" loading="lazy" /></p> TYPO3 Core - Task #89794 (Closed): Refactoring the database check in install toolhttp://forge.typo3.org/issues/897942019-11-28T17:41:31ZManuel Selbachmanuel_selbach@yahoo.de
<p>The current state of the check regarding database requirements is not separated properly.<br />Thus I suggest to refactor that to add platform and driver specific specification to have this maintainable.</p> TYPO3 Core - Task #89424 (Closed): Update Microsoft docker images in testshttp://forge.typo3.org/issues/894242019-10-15T15:44:32ZManuel Selbachmanuel_selbach@yahoo.de
<p>As mentioned on <a class="external" href="https://hub.docker.com/r/microsoft/mssql-server-linux">https://hub.docker.com/r/microsoft/mssql-server-linux</a> the images have moved to another location and thus should updated in the local tests and bamboo docker-compose.yml files.</p> TYPO3 Core - Feature #88805 (Closed): Add type to TYPO3\CMS\Core\Database\Query\QueryBuilder::sethttp://forge.typo3.org/issues/888052019-07-19T14:15:54ZManuel Selbachmanuel_selbach@yahoo.de
<p>It turned out, that the method <strong><code>TYPO3\CMS\Core\Database\Query\QueryBuilder::set</code></strong> does not allow to define the type if it is forced to use <strong><code>createNamedParameter</code></strong>.</p> TYPO3 Core - Task #88553 (Closed): Update doctrine/dbal to ^2.8.1http://forge.typo3.org/issues/885532019-06-13T09:40:58ZManuel Selbachmanuel_selbach@yahoo.deTYPO3 Core - Bug #87938 (Closed): Avoid superfluous cast and creation of instances DocumentTypeEx...http://forge.typo3.org/issues/879382019-03-16T22:12:38ZManuel Selbachmanuel_selbach@yahoo.de
<p>It turned out, that the implementation uses multiple cast to integer and multiple instances of DocumentTypeExclusionRestriction are created.</p> TYPO3 Core - Feature #87776 (Closed): Limit Restriction to table/s in QueryBuilderhttp://forge.typo3.org/issues/877762019-02-24T20:41:44ZManuel Selbachmanuel_selbach@yahoo.de
<p>With the concept to apply restrictions to the query it is not possible to decide for which table it should be used.<br />In some cases it is needed to apply restriction only to a certain table.</p>
<p>Example:<br /><pre>
$queryBuilder->getRestrictions()
->removeAll()
->add(GeneralUtility::makeInstance(DeletedRestriction::class))
->add(GeneralUtility::makeInstance(HiddenRestriction::class));
$queryBuilder->select('s.uid', 's.pid', 's.hidden', 's.title', 's.flag')
->from('sys_language', 's')
->from('pages_language_overlay', 'o')
->where(
$queryBuilder->expr()->eq('o.sys_language_uid', $queryBuilder->quoteIdentifier('s.uid')),
$queryBuilder->expr()->eq('o.pid', $queryBuilder->createNamedParameter($id, \PDO::PARAM_INT))
);
</pre></p>
<p>In this example the HiddenRestriction should only be applied to "sys_language", but will be applied to both tables currently.</p>
<p>So it should be possible to limit the restriction like:</p>
<pre>
$queryBuilder->getRestrictions()->add(GeneralUtility::makeInstance(HiddenRestriction::class, ['sys_language']))
</pre> TYPO3 Core - Feature #85369 (New): Proper YAML configuration APIhttp://forge.typo3.org/issues/853692018-06-24T10:04:06ZManuel Selbachmanuel_selbach@yahoo.de
<p>In the core there should be a proper API to register, validate the definition and retrieve the parsed YAML configuration.</p>
<p>Things that should be covered:<br />- register YAML configuration files at one central place<br />- define a definition for YAML files to validate that the configuration provided is correct<br />- proper override / combining / extending of a YAML configuration by registering another file (useful if an extension extends some yaml configuration)</p> TYPO3 Core - Bug #83585 (Closed): "New" page tree broken in Safari Version 11.0.2http://forge.typo3.org/issues/835852018-01-16T19:02:53ZManuel Selbachmanuel_selbach@yahoo.de
<p>The new page tree displays an arrow always, even if there is no subpage or subtree (see screenshot).</p>
<p><strong>Expected:</strong><br />The arrow should only be displayed if there is a subpage or subtree.</p>
<p>Used Safari Version 11.0.2 on macOS High Sierra 10.13.2</p>
<p><strong>Screenshots:</strong></p>
<p><img src="http://forge.typo3.org/attachments/download/33031/Bildschirmfoto2018-01-16-1.png" alt="" loading="lazy" /></p>
<p><img src="http://forge.typo3.org/attachments/download/33032/Bildschirmfoto2018-01-16-2.png" alt="" loading="lazy" /></p> TYPO3 Core - Bug #81818 (Closed): Option additionalViewModelModules does not appendhttp://forge.typo3.org/issues/818182017-07-07T11:14:27ZManuel Selbachmanuel_selbach@yahoo.de
<p>The option `additionalViewModelModules` within the YAML configuration of ext:from <br />does not append if there are already models registered. They will be overridden, which could<br />lead to a not working extended formEditor.</p> TYPO3 Core - Task #77817 (Closed): Doctrine: wrong escaping of table fields in schemaMigratorhttp://forge.typo3.org/issues/778172016-09-03T00:33:41ZManuel Selbachmanuel_selbach@yahoo.deTYPO3 Core - Task #77812 (Closed): Doctrine: ensure unique index keys for postgreSQLhttp://forge.typo3.org/issues/778122016-09-02T22:45:52ZManuel Selbachmanuel_selbach@yahoo.de
<p>PostgreSQL requires unique index name within the database not only on tables.<br />Creating indexes like parent fails on creation of second table with the same index name.</p>
<p>The issue is visible in the installTool by creating tables after database compare.</p> TYPO3 Core - Bug #77811 (Closed): Doctrine: wrong array key access in SchemaColumnDefinitionListe...http://forge.typo3.org/issues/778112016-09-02T22:42:15ZManuel Selbachmanuel_selbach@yahoo.de
<p>Generalize the access to the column type key</p> TYPO3 Core - Bug #68857 (Closed): Openid login not working on current masterhttp://forge.typo3.org/issues/688572015-08-08T11:18:55ZManuel Selbachmanuel_selbach@yahoo.de
<p>After login via openid the redirect is broken.</p>
<p>Redirect target:<br /><pre>
http://typo3-core.dev/typo3/index.php?login_status=login&tx_openid_location=http%3A%2F%2Ftypo3-core.dev%2Ftypo3%2Findex.php%3FloginProvider%3D1433416748&tx_openid_location_signature=e1549ce9cfa8e6be55bee307a952851ee2409557&tx_openid_mode=finish&tx_openid_claimed=https%3A%2F%2Fme.yahoo.com%2Fa%2FMNzxCfkDu86cuiZg_VM_7K6BzRy1RdmvwFTN&tx_openid_signature=f6eb5cd3f85caf04c8434842e48783ec8e32bf1f&janrain_nonce=2015-08-08T08%3A56%3A35ZDHnikK&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&openid.mode=id_res&openid.return_to=http%3A%2F%2Ftypo3-core.dev%2Ftypo3%2Findex.php%3Flogin_status%3Dlogin%26tx_openid_location%3Dhttp%253A%252F%252Ftypo3-core.dev%252Ftypo3%252Findex.php%253FloginProvider%253D1433416748%26tx_openid_location_signature%3De1549ce9cfa8e6be55bee307a952851ee2409557%26tx_openid_mode%3Dfinish%26tx_openid_claimed%3Dhttps%253A%252F%252Fme.yahoo.com%252Fa%252FMNzxCfkDu86cuiZg_VM_7K6BzRy1RdmvwFTN%26tx_openid_signature%3Df6eb5cd3f85caf04c8434842e48783ec8e32bf1f%26janrain_nonce%3D2015-08-08T08%253A56%253A35ZDHnikK&openid.claimed_id=https%3A%2F%2Fme.yahoo.com%2Fa%2FMNzxCfkDu86cuiZg_VM_7K6BzRy1RdmvwFTN%23715df&openid.identity=https%3A%2F%2Fme.yahoo.com%2Fa%2FMNzxCfkDu86cuiZg_VM_7K6BzRy1RdmvwFTN&openid.assoc_handle=uF_FEAFNu21dCt1wzt8Fq7oc3CQhf3zQkcRt9EPxtEXejHUWHEtUCrTMm_uja2Gdgy9UFuRZ8SuNAfW_O_fiAbe8cZJB2eOR9spKmMRi7ZAuUrGmTBe1fgjAiiVKSwMz.rxEJA--&openid.realm=http%3A%2F%2Ftypo3-core.dev%2F&openid.response_nonce=2015-08-08T08%3A56%3A30ZNx82ncvsLatHESKqZHq8YpTHe_7MkYz4aQ--&openid.signed=assoc_handle%2Cclaimed_id%2Cidentity%2Cmode%2Cns%2Cop_endpoint%2Cresponse_nonce%2Creturn_to%2Csigned%2Cpape.auth_level.nist&openid.op_endpoint=https%3A%2F%2Fopen.login.yahooapis.com%2Fopenid%2Fop%2Fauth&openid.pape.auth_level.nist=0&openid.sig=2MIUoHeWonfSxZ8FVeYpftVgtZs%3D
</pre></p>
<p>You stuck at the login screen without CSS etc. see screenshot attached.</p> TYPO3 Core - Task #68157 (Closed): Extended TypeConverter PersistentObjectConverter to overload Q...http://forge.typo3.org/issues/681572015-07-15T13:04:15ZManuel Selbachmanuel_selbach@yahoo.de
<p>Hi @ all,</p>
<p>e.g. if you would like to pass a hidden object to another action, you will run in an exception.<br /><pre>
#1297759968: Exception while property mapping at property path "":Missing storage page ids
</pre></p>
<p>By default TYPO3 sets the QuerySettings to enable ignore fields, which is absolutely fine.<br />But in some special cases you would like to overload this behavior for an action in the controller.<br />Here we can use the initialize action, which is called before every action and set the QuerySettings for a certain object.</p>
<p>Attached you will find my patch to allow this.</p>
<p>Example after supplying the patch for a controller show action:<br /><pre>
public function initializeShowAction()
{
$modelConfiguration = $this->arguments->getArgument('object')->getPropertyMappingConfiguration();
$modelConfiguration->setTypeConverterOptions(
'TYPO3\CMS\Extbase\Property\TypeConverter\PersistentObjectConverter',
array(
\TYPO3\CMS\Extbase\Property\TypeConverter\PersistentObjectConverter::IGNORE_ENABLE_FIELDS => true,
\TYPO3\CMS\Extbase\Property\TypeConverter\PersistentObjectConverter::RESPECT_STORAGE_PAGE => false,
\TYPO3\CMS\Extbase\Property\TypeConverter\PersistentObjectConverter::RESPECT_SYS_LANGUAGE => false,
)
);
}
/**
* show action
*
* @param \MyVendor\MyExtension\Domain\Model\Model $user
*/
public function showAction(\MyVendor\MyExtension\Domain\Model\Model $model)
{
$this->view->assign('model', $model);
}
</pre></p>
<p>Following options will be available with example data:</p>
<pre>
IGNORE_ENABLE_FIELDS = true|false
RESPECT_STORAGE_PAGE = true|false
RESPECT_SYS_LANGUAGE = true|false
ENABLE_FIELDS_TO_BE_IGNORED = hidden,starttime
INCLUDE_DELETED = true|false
SYS_LANGUAGE_UID = 2
STORAGE_PAGE_IDS = 1,2
</pre>