Bug #23038
closed
sysext taskcenter is missing class.mod_user_task.php (required from other extensions)
Added by Andrea Hildebrand over 14 years ago.
Updated over 10 years ago.
Description
The system extension "taskcenter" is missing class.mod_user_task.php which causes "Fatal error" for other extensions like sys_messages, sys_notepad, taskcenter_recent,...
Fatal error: Class 'mod_user_task' not found in /srv/www/htdocs/typo3_testsystem44/typo3conf/ext/sys_notepad/class.tx_sysnotepad.php on line 31
(issue imported from #M14917)
the extensions are not comaptibel with the new taskcenter anymore. I did a renewal of taskcenter_recent and sys_notepad but as I am not the author I can't upload those to TER but will upload a copy of it to this entry. sys_messages is not yet finished. sorry for that
Hey Georg,
At the moment the complete Taskcenter isn't useable. So it would be great, if you upload your version at this entry.
Yeah, where are your versions? I am looking for it.
What do you mean with:
"
"but will upload a copy of it to this entry
"
? where did you upload it?
Hey Georg,
it's possible that you take over the Extensionkeys or that you Upload the new versions for the sys_messages, sys_notepad, taskcenter_recent,...
i am in contact with authors of all 3, taskcenter_recent is already working and running with TER versions. sorry i missed to upload the other exts here...
Hi Georg,
can you please give us a short status update?
thx.
i sent a new version of sys_notepad to ter right now. sys_messages is not really simple, sorry needs a bit time or helping hands.
hi Georg,
thanks for your work.
How can we help you with sys_messages ?
- Status changed from Accepted to Needs Feedback
- Target version deleted (
0)
- Is Regression set to No
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?
- Status changed from Needs Feedback to Closed
- Assignee deleted (
Georg Ringer)
No feedback within the last 90 days => closing this ticket.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
Also available in: Atom
PDF