Wow, leave it to a PHP-based content management system to help me prove a point about useless bug-riddled crapware.
No later than when I wrote and tried to post the following message, that's when this PHP-based article system inexplicably corrupted the post and turned it into a black hole. If I'm lucky, the same wont happen again right now...
Original *attempted* posting:
Anti-Perfectionism Doesn't Mean "Release Crapware"
"Don't let perfection become the enemy of the good"?
That's all fine and good to an extent, but many people take it too far and wind up with products that are only minimally useful. Or useless bug-riddled crap.
Don't let rapid development become the enemy of a worthwhile product.
UPDATE 2013-03-20: I've fixed the problem. For some idiotic reason, the id (primary key) column of the database's "article parts" table (actually "tcm_mod_article_parts") was set to signed TINYINT. Seriously. That meant only 127 articles parts (I have one or two articles here that are two-parters) and then KABOOM, error upon INSERTs, which is exactly what happened. I have no idea whether the TangoCMS installation script set it up that way or if MySQL's migration tool fucked it up when I changed servers, and I'm not going to investigate either. Either way: fuck!
Oh yea, and wasn't it nice of my PHP-based CMS to not bother to give me any indication whatsoever the DB had returned an error, or that there has been any error at all? Wasn't even in the damn logfile for shit's sake. But then that's the whole philosophy of these damn dynamic languages, isn't it: Never flag an error when you can silently do the wrong thing.
I am still working on my own custom D/Vibe.d-based replacement, and it's been coming along, but slowly since I haven't had much time lately to dedicate to my various pet projects. It's not too far from a releasable state, but still needs some work on a few things.
0 comments for "The PHP CMS Screwed Up The Previous Article - And This One"
There are currently no comments.