Ty­po3 is just like WordPress a pop­u­lar PHP/MySQL rig. And there we have it again:

1: Copying file '/private/var/tmp/php3sbLRt' failed!:
The destination path (/Users/roland/www/dummy-4.2.1/uploads/pics)
may be write protected. Please make it write enabled!. 
(tt_content:NEW48cfde529d076:image)

While I ad­mire the ef­fort put in all the te­dious func­tion­al­i­ty pro­vid­ed by Ty­po3 to look a lot like an en­ter­prise lev­el tool, there is too much fo­cus on cater­ing for the $1/month host­ing users who hard­ly have SSH ac­cess, run every­thing as the same/only user who has write ac­cess to every­thing and don't have a choice con­cern­ing what data­base to use. And sad­ly, the crowd that has a $1/month host­ing men­tal­i­ty de­fines what is pop­u­lar and con­sid­ered a good choice for the rest.

MySQL's pay-off is: The world's most pop­u­lar open source data­base

Post­greSQL's pay-off is: The world's most ad­vanced open source data­base

So if an ap­pli­ca­tion doesn't as­pire to of­fer the op­tion to use the most ad­vanced op­tion, why should it as­pire to be the most ad­vanced op­tion it­self?