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 - 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 #78925 (Closed): PageLayoutController::renderQuickEdit() will throw exception fo...http://forge.typo3.org/issues/789252016-12-08T23:05:57ZManuel Selbachmanuel_selbach@yahoo.de
<p>If there is an empty page (no content elements on it) the method PageLayoutController::renderQuickEdit() will throw an exception on certain DBMS (depends on it's configuration), as the parameter $this->eRParts<sup><a href="#fn1">1</a></sup> will hold e.g. /new/1 which will be use in the Query as integer to get a sys_history record. As it is a "new" element there couldn't be a history entry at all, so let's skip that Query if the parameter $this->eRParts<sup><a href="#fn1">1</a></sup> can not be interpreted as integer.</p> TYPO3 Core - Task #78704 (Closed): BackendUtility: Refactor use of queryBuilder to use prepared s...http://forge.typo3.org/issues/787042016-11-15T15:09:08ZManuel Selbachmanuel_selbach@yahoo.de
<p>According to task <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Refactor use of queryBuilder to use prepared statements (Closed)" href="http://forge.typo3.org/issues/78437">#78437</a> queries should follow the prepared statement principle.<br />Thus method BackendUtiltiy::getRecordsByField() has to be refactored.</p> TYPO3 Core - Task #78578 (Closed): LiveSearch: Refactor use of queryBuilder to use prepared state...http://forge.typo3.org/issues/785782016-11-05T14:37:30ZManuel Selbachmanuel_selbach@yahoo.de
<p>According to task <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Refactor use of queryBuilder to use prepared statements (Closed)" href="http://forge.typo3.org/issues/78437">#78437</a> queries should follow the prepared statement principle.<br />Thus the LiveSearch has to be refactored.</p> TYPO3 Core - Task #75463 (Closed): "old fashioned" icons in category treehttp://forge.typo3.org/issues/754632016-04-08T15:07:23ZManuel Selbachmanuel_selbach@yahoo.de
<p>"Old fashioned" icons are used within the category tree in the backend. <br />This is not consistent with the other icons in the backend.</p> TYPO3 Core - Task #69038 (Closed): Move record-related entrypoints to backend routinghttp://forge.typo3.org/issues/690382015-08-14T08:18:01ZManuel Selbachmanuel_selbach@yahoo.deTYPO3 Core - Task #68881 (Closed): Add backend routes for wizards (part 2)http://forge.typo3.org/issues/688812015-08-09T11:24:31ZManuel Selbachmanuel_selbach@yahoo.de
<p>Move all wizards to the Backend Routing.<br />Do not use the module registration for wizards in ext_tables.php<br />Use Configuration/Backend/Routes.php instead.</p>
<p>Instructions for testing the routings:</p>
<p>colorpicker wizard<br />------------------</p>
<p>To test colorpicker follow these steps:</p>
<p>- install introduction package<br />- create a bootstrap carousel element<br />- create a carousel item<br />- The wizard is located beside the "Text color" field<br />- Open the wizard. The route should now be visible in the location of the wizard window.</p>
<p>BackendLayout wizard<br />--------------------</p>
<p>- create a backend layout record per list view<br />- The wizard is located beside the field "Config" <br />- Open the wizard. The route should now be visible in the location of the wizard window.</p>
<p>Table wizard<br />------------<br />- create a content element of type "Table" <br />- save it<br />- go to tab "Table" <br />- The wizard is located beside the field "Text" <br />- Have a look at the href-attribute of the wizard link. The route should be visible there.</p>
<p>RTE wirzard<br />-----------<br />- create a text element and save it<br />- The wizard is located beside the RTE for field "Text" (Fullscreen Rich Text Editing)<br />- Have a look at the href-attribute of the wizard link. The route should be visible there.</p> TYPO3 Core - Bug #68880 (Closed): Save, save & view, save & close not working in RTE Wizardhttp://forge.typo3.org/issues/688802015-08-09T11:04:46ZManuel Selbachmanuel_selbach@yahoo.de
<p>The button Save, save & view and save & close don´t work in the RTE wizard (Fullscreen Rich Text Editing).</p>
<p>JavaScript error appears:<br /><pre>
Uncaught TypeError: document.getElementsByName(...).submit is not a function
</pre></p>
<pre>
submitForm: function() {
if (TBE_EDITOR.doSaveFieldName) {
document[TBE_EDITOR.formname][TBE_EDITOR.doSaveFieldName].value=1;
}
// Set a short timeout to allow other JS processes to complete, in particular those from
// EXT:backend/Resources/Public/JavaScript/FormEngine.js (reference: http://forge.typo3.org/issues/58755).
// TODO: This should be solved in a better way when this script is refactored.
window.setTimeout(function() {
document.getElementsByName(TBE_EDITOR.formname).submit(); <----------------- here the error appears
}, 10);
},
</pre> TYPO3 Core - Bug #68860 (Closed): SelectImage Eventlistener throws execptionhttp://forge.typo3.org/issues/688602015-08-08T16:02:21ZManuel Selbachmanuel_selbach@yahoo.deTYPO3 Core - Task #68858 (Closed): Add backend routes for wizardshttp://forge.typo3.org/issues/688582015-08-08T15:19:16ZManuel Selbachmanuel_selbach@yahoo.de
<p>Move all wizards to the backend routing form ext_tables.php to Configuration/Backend/Routes.php</p>
<p>RTE Wizards:<br />You need the full RTE (demo mode in Extension Configuration).<br />If you have bootstrap package installed you should comment out the following line in ext_localconf.php:<br />\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addPageTSConfig('<INCLUDE_TYPOSCRIPT: source="FILE:EXT:' . $_EXTKEY . '/Configuration/PageTS/RTE.txt">');</p>
<p>Otherwise the RTE configuration of the bootstrap package will overwrite everything ;)</p>
<p>OpenId:<br />Install the extension.<br />Within the backend user settings there is a new field "OpenID identifier".<br />The wizard is located beside the field.</p>
<p>compatibility6:<br />To test the form wizard you have to uninstall the form extension and to install the compatibility6 extension.<br />After that, create a form, save and go down to the config area.<br />The wizard is located beside the textarea</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 #68814 (Closed): remove of base constant TYPO3_URL_ORGhttp://forge.typo3.org/issues/688142015-08-07T09:49:42ZManuel Selbachmanuel_selbach@yahoo.de
<p>Base constant TYPO3_URL_ORG defined in SystemEnvironmentBuilder::defineBaseConstants() can be removed.<br />It´s only for internal usage only and defined at 2 places in the core.</p>
<p>Use TYPO3_URL_GENERAL instead.</p> TYPO3 Core - Task #68756 (Closed): Add config "base" to stdWraphttp://forge.typo3.org/issues/687562015-08-05T15:04:49ZManuel Selbachmanuel_selbach@yahoo.de
<p>Follow up: <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Filelist should use IEC prefixes and appropriate units for filesize. (Closed)" href="http://forge.typo3.org/issues/22175">#22175</a></p>
<p>The following function was updated and added with a new optional parameter $base:<br />TYPO3\CMS\Core\Utility\GeneralUtility::formatSize($sizeInBytes, $labels = '', $base = 0)</p>
<p>This impacts the function:<br />TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer->stdWrap_bytes</p>
<p>It is not possible now, to set the base parameter via TypoScript if you add custom labels.</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>