TYPO3 CMS  TYPO3_7-6
Todo List
Member ADODB_Active_Record::Load ($where=null, $bindarr=false)

Improve by storing once and for all in table metadata

Also re-use info for hasManyId

Member adodb_GetActiveRecordsClass (&$db, $class, $tableObj, $whereOrderBy, $bindarr, $primkeyArr, $extra, $relations)

Improve by storing once and for all in table metadata

Also re-use info for hasManyId

Member TYPO3::checkInlineFileTypeAccessForField (array $selectorConfiguration, array $fileRecord)
: check this ...
Member TYPO3::__construct (NodeFactory $nodeFactory, array $data)

: Should NOT set the nodeFactory instance, this is done by AbstractContainer only,

: but not done for Element classes: Elements are tree leaves, they MUST

: not create new nodes again.

: Currently, AbstractFormElement still does that, but do not rely on the fact that

: Element classes have an instance of NodeFactory at hand.

Class TYPO3
: It should be possible to merge this container to ListOfFieldsContainer
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.

Member TYPO3::addData (array $result)
: This does not work for "default" fields like "hidden", those don't have a type set - fix in bootstrap?? foreach ($result['processedTca']['columns'] as $fieldName => $fieldConfig) { if (!isset($fieldConfig['type'])) { throw new ( 'Field ' . $fieldName . ' of TCA table ' . $result['tableName'] . ' has no type set', 1438594044 ); } }
Class TYPO3
: maybe not needed?
Member TYPO3::resolvePossibleExternalFileInDataStructure (array $result, $fieldName)

: Why is this not done in BackendUtility::getFlexFormDS() directly? If done there, the two methods

: GeneralUtility::resolveSheetDefInDS() and GeneralUtility::resolveAllSheetsInDS() could be killed

: since this resolving is basically the only really useful thing they actually do.

Member TYPO3::addDataStructurePointersToMetaData (array $result, $fieldName)
: This method is a stopgap measure to get required information into the AJAX controller
Member TYPO3::getFlexIdentifier (array $result, $fieldName)

: This method is only implemented half. It basically should do all the

: pointer handling that is done within BackendUtility::getFlexFormDS() to $srcPointer.

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::prepareSelectedNodes (array $itemArray, array $databaseValues)
: this is ugly - should be removed with the tree rewrite
Member TYPO3::removeFieldsFromPalettes (array $result, $removeListArray)
: unit tests!
Member TYPO3::injectAjaxConfiguration ($contextString='')
: 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
Class TYPO3
This class is incomplete, because the methods still need
Member TYPO3::getFlexFormDS ($conf, $row, $table, $fieldName='', $WSOL=true, $newRecordPidValue=0)
: All those nasty details should be covered with tests, also it is very unfortunate the final $srcPointer is not exposed
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::explain ($query, $from_table, $row_count)
Feature is not DBAL-compliant
Class TYPO3
Need to really extend this class when the tcemain 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::getFromMPmap ($pageId=0)
Implement some caching of the result between hits. (more than just the memory caching used here)
Member TYPO3::checkIfAllowed ($ext, $theDest, $filename='')
Deprecate, but still in use by DataHandler
Member TYPO3::checkIfFullAccess ($theDest)
Deprecate: but still in use by through func_unzip in ExtendedFileUtility
Member TYPO3::checkPathAgainstMounts ($thePath)
: deprecate this function, now done in the Storage object. But still in use by impexp and ExtendedFileUtility
Member TYPO3::cleanFileName ($fileName, $charset='')
Deprecate, but still in use by the core
Member TYPO3::findFirstWebFolder ()
: deprecate this function. But still in use by impexp
Member TYPO3::getUniqueName ($theFile, $theDest, $dontCheckForUnique=0)
Deprecate, but still in use by the Core (DataHandler...)
Member TYPO3::is_allowed ($iconkey, $type)
Deprecate, but still in use by checkIfAllowed()
Member TYPO3::is_directory ($theDir)
Deprecate: but still in use by getUniqueName (used by DataHandler)
Member TYPO3::is_webpath ($path)
Deprecate, but still in use by DataHandler
Member TYPO3::slashPath ($path)
Deprecate, but still in use by is_webpath, used by DataHandler
Member TYPO3::compat_version ($verNumberStr)
Still needs a function to convert versions to branches
Member TYPO3::getUserObj ($classRef)
Deprecate the whole method in several steps:
  1. Deprecated singleton pattern, (will be removed in TYPO3 CMS 8)
  2. Deprecate file prefix/ require file,
  3. Deprecate usage without valid class name.
  4. The last step should be to deprecate the method itself.
Member TYPO3::isBrokenEmailEnvironment ()
4.3 should have additional configuration variable, which is combined by || with the rest in this function.
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::addVisibilityConstraintStatement (QuerySettingsInterface $querySettings, $tableName, array &$sql)
remove after getUidOfAlreadyPersistedValueObject is adjusted, this was moved to queryParser
Member TYPO3::getBackendConstraintStatement ($tableName, $ignoreEnableFields, $includeDeleted)
remove after getUidOfAlreadyPersistedValueObject is adjusted, this was moved to queryParser
Member TYPO3::getFrontendConstraintStatement ($tableName, $ignoreEnableFields, array $enableFieldsToBeIgnored=[], $includeDeleted)
remove after getUidOfAlreadyPersistedValueObject is adjusted, this was moved to queryParser
Member TYPO3::getUidOfAlreadyPersistedValueObject (AbstractValueObject $object)
this is the last monster in this persistence series. refactor!
Member TYPO3::replacePlaceholders (&$sqlString, array $parameters, $tableName='foo')
add deprecation notice after getUidOfAlreadyPersistedValueObject is adjusted
Member TYPO3::normalizeParameterIdentifier ($identifier)
come on, clean up that method!
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::translate ($key, $extensionName, $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::getVariableContainer ()
remove
Member TYPO3::getVariableContainer ()
Rename to getPostParseVariableContainer
Member TYPO3::postProcessArgumentsForObjectAccessor (array $arguments)
This method should become superflous once the rest has been refactored, so that this code is not needed.
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::resolveTypoScriptReferences (array $typoScript)
Extract to core then...
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::isClassAvailable ($className, array $config=null)
This method was introduced in TYPO3 4.3 and can be removed if the autoload was integrated
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::includeLibraries (array $libraries)
deprecate this method
Member TYPO3::main (&$backRef, $menuItems, $table, $uid)
Skinning for icons...
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::setDownloadTargetPath ($downloadTargetPath)
move this to folder structure
Member TYPO3::genTree_traverse ($rootID, $depth, $echoLevel=0, $callBack='', $versionSwapmode='', $rootIsVersion=0, $accumulatedPath='')
$versionSwapmode needs to be cleaned up, since page and branch version (0, 1) does not exist anymore
Member TYPO3::main ()

Add parameter to exclude filepath

Add parameter to list more file names/patterns to ignore

Add parameter to include RTEmagic images

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::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::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/