TLDR; This is nothing new : WordPress is a great choice for a quick blog or web-site.<\/p>\n
We were after an update to our web-site and we did not want to spent too many evenings and weekends.<\/p>\n
We used Textpattern<\/a> for a long time for our old site. It was OK, but I missed a mobile app and did not like textile markup and generally was not greatly impressed by the admin UI.<\/p>\n About 5 years ago I used Joomla<\/a> for a client, but to be honest Martina and I kind of forgot about it and did not check it out. I might have been the best, but we will never know.<\/p>\n Typo3<\/a> came into consideration because it is popular in German speaking countries. I checked it out in a demo site and downloaded it and never did more with it.<\/p>\n In the end it came down to only Drupal<\/a> and WordPress<\/a> even though these two might be the best they become the favourites for these reasons:<\/p>\n I know Drupal from work, but not intimately. For this test I set-up a complete site and allowed multiple users to create their own blogs in both WordPress and Drupal and apart from Martina’s work in the mnm blog and her effort of importing the old entries into the WordPress our test sites in WordPress and Drupal had similar functionality. Or I could have searched and used that script<\/a>. I believe I was quicker with my script.<\/p>\n I did a bit more CSS work in Drupal. I think that it takes a similar effort to set up a multi site WordPress installation as a Drupal installation that provides a similar set-up.<\/p>\n The points that moved the decision to WordPress in the end:<\/p>\n encoding issues that have been a problem in the old site. But that also meant that she was faster in doing a single user blog in WordPress with imported posts than I was with the multi-user Drupal set up and a single themed blog. (Though I was also the one who had to spent the time on the multi-site WordPress set-up)<\/p>\n","protected":false},"excerpt":{"rendered":" TLDR; This is nothing new: WordPress is a great choice for a quick blog or web-site. Continue reading Joomla<\/h3>\n
Typo3<\/h3>\n
The Finalists<\/h2>\n
\n
\nI believe that things were done in Drupal were more elegant than the equivalent in WordPress.
\nAlso Drupal is not as annoying about the domain name changes as a multi-site WordPress installation<\/a>.
\nDuring the process of testing I set up a VM and used a local IP then moved to a faked domain (hosts entry) then I wanted to reach it externally and set up a reverse proxy of our test home domain.
\nDrupal was still happy but for WordPress I had to run something along the lines of this:<\/p>\nexport grepFile=$(mktemp)\n\ncat > ${grepFile} <<ENDL\ntest.domain1:2081\ntest.domain1\ntest.domain2\nwww.mnm.at:2081\nwww.mnm.at\n10.10.10.10:2081\n10.10.10.10\nENDL\n\nexport sedFile=$(mktemp)\nsed -e 's@\\(.*\\)@s~\\1~mnm.at~g@' ${grepFile} > ${sedFile}\nfor f in $(grep -l -i -r --file ${grepFile} wordpress wp.final.dump.sql); do \n sed -i --file ${sedFile} $f \ndone\n\nrm ${grepFile} ${sedFile}\n<\/code><\/pre>\n\n