TYPO3 CMS  TYPO3_8-7
Todo List
Class TYPO3
: It should be possible to merge this container to ListOfFieldsContainer
Member TYPO3::getRegisteredFlexForms ($table)

: This approach is limited and doesn't find everything. It works for casual tt_content plugins, though:

: The data structure identifier determination depends on data row, but we don't have all rows at hand here.

: The code thus "guesses" some standard data structure identifier scenarios and tries to resolve those.

: This guessing can not be solved in a good way. A general registry of "all" possible data structures is

: probably not wanted, since that wouldn't work for truly dynamic DS calculations. Probably the only

: thing we could do here is a hook to allow extensions declaring specific data structures to

: allow backend admins to set exclude flags for certain fields in those cases.

Member TYPO3::getStaticValues ($itemArray, $dynamicItemArray)
: Check method usage, it's probably bogus in select context and was removed from select tree already.
Member TYPO3::setDefaultsFromDevVals (array $result)

: Fetch this stuff from request object as soon as modules were moved to PSR-7,

: or hand values over via $result array, so the _GP access is transferred to

: controllers concern.

Class TYPO3
: maybe not needed?
Member TYPO3::addInlineFirstPid (array $result)
: Find out when and if this is different from 'effectivePid'
Member TYPO3::getLiveDefaultId ($tableName, $uid)
: the workspace mess still must be resolved somehow
Member TYPO3::removeFieldsFromPalettes (array $result, $removeListArray)
: unit tests!
Member TYPO3::injectAjaxConfiguration (array $config)
: Review this construct - Why can't the ajax call fetch these data on its own and transfers it to client instead?
Member TYPO3::makeShortcutIcon ($gvList, $setList, $modName, $motherModName='', $displayName='', $classes='btn btn-default btn-sm')
Make this thing return a button object
Member TYPO3::__wakeup ()
the constraints model needs another way of storing persisted search data than serialisation
Class TYPO3
: This should be stuffed to some more central place
Class TYPO3
: This should be extended and put at some more central place
Class TYPO3
This should be moved to EXT:workspaces if EXT:belog works no matter if workspaces are installed or not
Member TYPO3::getEnumerationTableColumnDefinition (array $tableColumn, AbstractPlatform $platform)
: The $tableColumn source currently only support MySQL definition style.
Class TYPO3
Need to really extend this class when the DataHandler library has been updated and the whole API is better defined. There are some known bugs in this library. Further it would be nice with a facility to not only analyze but also clean up!
Member TYPO3::getAlternative ()
Possibly move this to the image domain object instead
Member TYPO3::getDescription ()
Possibly move this to the image domain object instead
Member TYPO3::getLink ()
Move this to the image domain object instead
Member TYPO3::getTitle ()
Possibly move this to the image domain object instead
Member TYPO3::fileNeedsProcessing ()
isOutdated()/needsReprocessing()?
Member TYPO3::fileNeedsProcessing ()
isOutdated()/needsReprocessing()?
Member TYPO3::dbTypeDateEvalDatetimeDataProvider ()
fix these unstable tests public function dbTypeDateEvalDate(BackendTester $I, Example $testData) { $this->runInputFieldTest($I, $testData); }
Member TYPO3::dbTypeDateEvalTimeDataProvider ()
fix these unstable tests public function dbTypeDateEvalDatetime(BackendTester $I, Example $testData) { $this->runInputFieldTest($I, $testData); }
Member TYPO3::simpleEvalInputFieldsDataProvider ()
this one probably broke with the html type="number" patch 'label' => 'input_9 eval=int', 'inputValue' => 'TYPO3', 'expectedValue' => '0', 'expectedInternalValue' => '0', 'expectedValueAfterSave' => '0', 'comment' => '', ],
Member TYPO3::simpleRangeAndMd5FieldsDataProvider ()
this one probably broke with the type="number" patch 'label' => 'input_25 eval=int, default=0, range lower=-2, range upper=2', 'inputValue' => 'Kasper TYPO3', 'expectedValue' => '0', 'expectedInternalValue' => '0', 'expectedValueAfterSave' => '0', 'comment' => '', ],
Member TYPO3::deleteQuotesIdentifierAndDelegatesToConcreteQueryBuilder ()
: Test with alias
Member TYPO3::fromQuotesIdentifierAndDelegatesToConcreteQueryBuilder ()
: Test with alias
Member TYPO3::updateQuotesIdentifierAndDelegatesToConcreteQueryBuilder ()
: Test with alias
Member TYPO3::withPortAcceptsBooleanTrueAsPortOne ()

: Currently, boolean true is interpreted as 1 by canBeInterpretedAsInteger().

: This test shows that, but there is an inconsistency and maybe it would be better

: if the code would not accept 'true' as valid port but throw an exception instead.

: If that is changed, 'true' should be added to the 'invalid type' data provider above.

Member TYPO3::getFromMPmap ($pageId=0)
Implement some caching of the result between hits. (more than just the memory caching used here)
Member TYPO3::checkIfAllowed ($ext, $_, $filename='')
Deprecate, but still in use by DataHandler
Member TYPO3::cleanFileName ($fileName)
Deprecate, but still in use by the core
Member TYPO3::getUniqueName ($theFile, $theDest, $dontCheckForUnique=false)
Deprecate, but still in use by the Core (DataHandler...)
Member TYPO3::compat_version ($verNumberStr)
Still needs a function to convert versions to branches
Member TYPO3::convertTransientObjectToArray ( $object)
Refactore this into convertDomainObjectsToIdentityArrays()
Member TYPO3::getSelectorName ()
This has to be checked at another place
Member TYPO3::getUidOfAlreadyPersistedValueObject ( $object)
this is the last monster in this persistence series. refactor!
Member TYPO3::getQuerySettings ()
decide whether this can be deprecated eventually This method is not part of TYPO3Flow API
Member TYPO3::setQuerySettings (Generic $querySettings)
decide whether this can be deprecated somewhen This method is not part of TYPO3Flow API
Class TYPO3
Implement functionality for converting collection properties.
Member TYPO3::getGettableProperties ($object)
What to do with ArrayAccess
Member TYPO3::getValue ($object=null)
Maybe support private properties as well, as of PHP 5.3.0 we can do
Member TYPO3::appendHmac ($string)
Mark as API once it is more stable
Member TYPO3::validateAndStripHmac ($string)
Mark as API once it is more stable
Member TYPO3::getTargetPidByPluginSignatureDeterminesTheTargetPidIfDefaultPidIsAuto ()
This should rather be a functional test since it needs a connection / querybuilder
Member TYPO3::getTargetPidByPluginSignatureReturnsNullIfTargetPidCouldNotBeDetermined ()
This should rather be a functional test since it needs a connection / querybuilder
Member TYPO3::getTargetPidByPluginSignatureThrowsExceptionIfMoreThanOneTargetPidsWereFound ()
This should rather be a functional test since it needs a connection / querybuilder
Member TYPO3::translate ($key, $extensionName=null, $arguments=null)
: If vsprintf gets a malformed string, it returns FALSE! Should we throw an exception there?
Member TYPO3::createValidator ($validatorType, array $validatorOptions=[])
remove throwing Exceptions in resolveValidatorObjectName
Member TYPO3::checkExtensionDependency (Dependency $dependency)
handle exceptions / markForUpload
Member TYPO3::getExtensionFromTer ($extensionKey, Dependency $dependency)
unit tests
Member TYPO3::initializeWidgetIdentifier ()
clean up, and make it somehow more routing compatible.
Member TYPO3::configureObjectManager ()
this is duplicated code (see ::configureObjectManager())
Member TYPO3::renderHiddenReferrerFields ()
filter out referrer information that is equal to the target (e.g. same packageKey)
Member TYPO3::transformFormDefinitionForFormEditor (array $formDefinition)
move this to FormDefinitionConversionService
Member TYPO3::filterEmptyArrays (array $array)
ArrayUtility?
Member TYPO3::addParams ($content, $conf)
Make it XHTML compatible. Will not present "/>" endings of tags right now. Further getting the tagname might fail if it is not separated by a normal space from the attributes.
Member TYPO3::resolveMixedLinkParameter ($linkText, $mixedLinkParameter, &$configuration=[])
the functionality of the "file:" syntax + the hook should be marked as deprecated, an upgrade wizard should handle existing links
Member TYPO3::TCAlookup ($inputValue, $conf)
It would be nice it this function basically looked up any type of value, db-relations etc.
Member TYPO3::$contentType
Ticket: #63642 Should be refactored to a request/response model later
Member TYPO3::addMountPointParameterToPage (array $page)
Find a better name. The current doesn't hit the point.
Member TYPO3::setUpFileStorage ()
Provide functionality of creating and indexing fileadmin/ in Testing Framework
Class TYPO3
: Some of these tests would be better suited as functional tests
Member TYPO3::linkPage ($pageUid, $linkText, $row=[], $markUpSwParams=[])
make use of the UriBuilder
Member TYPO3::makeDescription ($row, $noMarkup=false, $length=180)
overwork this
Member TYPO3::makeRating ($row)
can this be a ViewHelper?
Member TYPO3::getDefaultDatabaseCharset (string $dbName)
this function is MySQL specific. If the core has migrated to Doctrine it should be reexamined whether this function and the check in $this->checkExistingDatabase could be deleted and utf8 otherwise enforced (guaranteeing compatibility with other database servers).
Member TYPO3::setDownloadTargetPath ($downloadTargetPath)
move this to folder structure
Member TYPO3::stopTask ()
find a way to really kill the running task
Member TYPO3::cleanExecutionArrays ()
find a way to actually kill the job
Member TYPO3::removeTask (Task $task)
find a way to actually kill the existing jobs
Member TYPO3::deleteSingleRecord ($table, $uid)
What about reporting errors back to the ExtJS interface? /olly/
Member TYPO3::swapSingleRecord ($table, $t3ver_oid, $orig_uid)
What about reporting errors back to the ExtJS interface? /olly/
Member TYPO3::compilePreviewKeyword ($getVarsStr, $backendUserUid, $ttl=172800, $fullWorkspace=null)
for sys_preview:
  • Add a comment which can be shown to previewer in frontend in some way (plus maybe ability to write back, take other action?)
  • Add possibility for the preview keyword to work in the backend as well: So it becomes a quick way to a certain action of sorts?
Member TYPO3::changeContentSortingAndCopyDraftPage ()
Analyse PostgreSQL issues further, which is a generic issue