Lista di cose da fare

Membro mod_user_task::sendEmail ($email, $subject, $message)

this function is from the old implementation of the taskcenter, it should be updated to modern standards

Membro mod_user_task::sendEmail ($email, $subject, $message)

this function is from the old implementation of the taskcenter, it should be updated to modern standards

Membro mod_user_task::sendEmail ($email, $subject, $message)

this function is from the old implementation of the taskcenter, it should be updated to modern standards

Membro t3lib_div::validPathStr ($theFile)

Possible improvement: Should it rawurldecode the string first to check if any of these characters is encoded ?

Membro t3lib_div::validPathStr ($theFile)

Possible improvement: Should it rawurldecode the string first to check if any of these characters is encoded ?

Membro t3lib_div::validPathStr ($theFile)

Possible improvement: Should it rawurldecode the string first to check if any of these characters is encoded ?

Membro t3lib_div::validPathStr ($theFile)

Possible improvement: Should it rawurldecode the string first to check if any of these characters is encoded ?

Membro t3lib_div::validPathStr ($theFile)

Possible improvement: Should it rawurldecode the string first to check if any of these characters is encoded ?

Membro t3lib_div::validPathStr ($theFile)

Possible improvement: Should it rawurldecode the string first to check if any of these characters is encoded ?

Membro t3lib_sqlengine::readDataSource ($table)

Table locking tools?

Membro t3lib_sqlengine::readDataSource ($table)

Table locking tools?

Membro t3lib_sqlengine::readDataSource ($table)

Table locking tools?

Membro t3lib_sqlengine::readDataSource ($table)

Table locking tools?

Membro t3lib_sqlengine::readDataSource ($table)

Table locking tools?

Membro t3lib_sqlengine::readDataSource ($table)

Table locking tools?

Membro t3lib_sqlengine::saveDataSource ($table)

Table locking tools?

Membro t3lib_sqlengine::saveDataSource ($table)

Table locking tools?

Membro t3lib_sqlengine::saveDataSource ($table)

Table locking tools?

Membro t3lib_sqlengine::saveDataSource ($table)

Table locking tools?

Membro t3lib_sqlengine::saveDataSource ($table)

Table locking tools?

Membro t3lib_sqlengine::saveDataSource ($table)

Table locking tools?

Membro t3lib_TStemplate::getFromMPmap ($pageId=0)

Implement some caching of the result between hits. (more than just the memory caching used here)

Membro t3lib_TStemplate::getFromMPmap ($pageId=0)

Implement some caching of the result between hits. (more than just the memory caching used here)

Membro t3lib_TStemplate::getFromMPmap ($pageId=0)

Implement some caching of the result between hits. (more than just the memory caching used here)

Membro t3lib_TStemplate::getFromMPmap ($pageId=0)

Implement some caching of the result between hits. (more than just the memory caching used here)

Membro t3lib_TStemplate::getFromMPmap ($pageId=0)

Implement some caching of the result between hits. (more than just the memory caching used here)

Membro t3lib_TStemplate::getFromMPmap ($pageId=0)

Implement some caching of the result between hits. (more than just the memory caching used here)

Membro t3lib_TStemplate::mergeConstantsFromPageTSconfig ($constArray)

Apply caching to the parsed Page TSconfig. This is done in the other similar functions for both frontend and backend. However, since this functions works for BOTH frontend and backend we will have to either write our own local caching function or (more likely) detect if we are in FE or BE and use caching functions accordingly. Not having caching affects mostly the backend modules inside the "Template" module since the overhead in the frontend is only seen when TypoScript templates are parsed anyways (after which point they are cached anyways...)

Membro t3lib_TStemplate::mergeConstantsFromPageTSconfig ($constArray)

Apply caching to the parsed Page TSconfig. This is done in the other similar functions for both frontend and backend. However, since this functions works for BOTH frontend and backend we will have to either write our own local caching function or (more likely) detect if we are in FE or BE and use caching functions accordingly. Not having caching affects mostly the backend modules inside the "Template" module since the overhead in the frontend is only seen when TypoScript templates are parsed anyways (after which point they are cached anyways...)

Membro t3lib_TStemplate::mergeConstantsFromPageTSconfig ($constArray)

Apply caching to the parsed Page TSconfig. This is done in the other similar functions for both frontend and backend. However, since this functions works for BOTH frontend and backend we will have to either write our own local caching function or (more likely) detect if we are in FE or BE and use caching functions accordingly. Not having caching affects mostly the backend modules inside the "Template" module since the overhead in the frontend is only seen when TypoScript templates are parsed anyways (after which point they are cached anyways...)

Membro t3lib_TStemplate::mergeConstantsFromPageTSconfig ($constArray)

Apply caching to the parsed Page TSconfig. This is done in the other similar functions for both frontend and backend. However, since this functions works for BOTH frontend and backend we will have to either write our own local caching function or (more likely) detect if we are in FE or BE and use caching functions accordingly. Not having caching affects mostly the backend modules inside the "Template" module since the overhead in the frontend is only seen when TypoScript templates are parsed anyways (after which point they are cached anyways...)

Membro t3lib_TStemplate::mergeConstantsFromPageTSconfig ($constArray)

Apply caching to the parsed Page TSconfig. This is done in the other similar functions for both frontend and backend. However, since this functions works for BOTH frontend and backend we will have to either write our own local caching function or (more likely) detect if we are in FE or BE and use caching functions accordingly. Not having caching affects mostly the backend modules inside the "Template" module since the overhead in the frontend is only seen when TypoScript templates are parsed anyways (after which point they are cached anyways...)

Membro t3lib_TStemplate::mergeConstantsFromPageTSconfig ($constArray)

Apply caching to the parsed Page TSconfig. This is done in the other similar functions for both frontend and backend. However, since this functions works for BOTH frontend and backend we will have to either write our own local caching function or (more likely) detect if we are in FE or BE and use caching functions accordingly. Not having caching affects mostly the backend modules inside the "Template" module since the overhead in the frontend is only seen when TypoScript templates are parsed anyways (after which point they are cached anyways...)

Membro tslib_cObj::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. &tx_extrepmgm_pi1[extUid]=270&tx_extrepmgm_pi1[tocEl]=325&cHash=ae4272e694 Membro tslib_cObj::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. http://typo3.org/doc.0.html?&tx_extrepmgm_pi1[extUid]=270&tx_extrepmgm_pi1[tocEl]=325&cHash=ae4272e694 Membro tslib_cObj::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. http://typo3.org/doc.0.html?&tx_extrepmgm_pi1[extUid]=270&tx_extrepmgm_pi1[tocEl]=325&cHash=ae4272e694 Membro tslib_cObj::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. http://typo3.org/doc.0.html?&tx_extrepmgm_pi1[extUid]=270&tx_extrepmgm_pi1[tocEl]=325&cHash=ae4272e694 Membro tslib_cObj::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. http://typo3.org/doc.0.html?&tx_extrepmgm_pi1[extUid]=270&tx_extrepmgm_pi1[tocEl]=325&cHash=ae4272e694 Membro tslib_cObj::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. http://typo3.org/doc.0.html?&tx_extrepmgm_pi1[extUid]=270&tx_extrepmgm_pi1[tocEl]=325&cHash=ae4272e694 Membro tx_impexp_clickmenu::main (&$backRef, $menuItems, $table, $uid) Skinning for icons... Membro tx_impexp_clickmenu::main (&$backRef, $menuItems, $table, $uid) Skinning for icons... Membro tx_impexp_clickmenu::main (&$backRef, $menuItems, $table, $uid) Skinning for icons... Membro tx_install::cleanupManager () Add more functionality ... Membro tx_install::cleanupManager () Add more functionality ... Membro tx_install::cleanupManager () Add more functionality ... Membro tx_systodos::renderTaskList () instead of showing picture depending on who created the record, it's probably more interesting to display who touched it last. Membro tx_systodos::renderTaskList () instead of showing picture depending on who created the record, it's probably more interesting to display who touched it last. Membro tx_systodos::renderTaskList () instead of showing picture depending on who created the record, it's probably more interesting to display who touched it last. Membro tx_systodos::todos_beginWorkflow ($workflowRecord) dependent on the workflow record... should get info from wfDef instead Membro tx_systodos::todos_beginWorkflow ($workflowRecord) dependent on the workflow record... should get info from wfDef instead Membro tx_systodos::todos_beginWorkflow ($workflowRecord) dependent on the workflow record... should get info from wfDef instead Membro tx_systodos::todos_finalizeWorkflow ($workflowRecord, $relRecord) some of this should probably be controlled by wfDef Membro tx_systodos::todos_finalizeWorkflow ($workflowRecord, $relRecord) some of this should probably be controlled by wfDef Membro tx_systodos::todos_finalizeWorkflow ($workflowRecord, $relRecord) some of this should probably be controlled by wfDef Membro tx_sysworkflows_executor::publishNewRecord ($table, $uid, $newPid=null, $doNotUnhide=false, $workflowRecord=Array()) workflowrecord should not be passed here it somehow be encapsulated in the definition class Membro tx_sysworkflows_executor::publishNewRecord ($table, $uid, $newPid=null, $doNotUnhide=false, $workflowRecord=Array()) workflowrecord should not be passed here it somehow be encapsulated in the definition class Membro tx_sysworkflows_executor::publishNewRecord ($table, $uid, $newPid=null, $doNotUnhide=false, $workflowRecord=Array()) workflowrecord should not be passed here it somehow be encapsulated in the definition class Namespace 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! Namespace 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! Namespace 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! Namespace 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! Namespace 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! Namespace 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!

---