Subscribe to Collegiate Chronicles        RSS Feed

Joomla: It's a love-hate relationship

Icon 7 Comments
I'm coming down to the wire on this new site launch - 6000+ pages of content painstakingly moved, piece by piece, from a custom coded site into a Joomla powered site. Due to the huge amount of modifications to be made to the content, writing a script to port it all from Site A to Site B didn't seem reasonable - the options were (1) move every page by hand to double check and verify all the information is up-to-date and the new site starts out with only the most current information, or (2) port all the old information over with a script and go through the new site page by page to verify all the information is up-to-date and hope you didn't miss anything along the way, so it's been a labor of love. Or a labor of hate, depending upon your point of view.

I almost feel bipolar. One day, I'm singing Joomla's praises because I've located a plugin that will make one small headache much easier to manage. The next day, I'm disgruntled and seething because I hate data entry with the white hot intensity of a thousand suns.

Ultimately, I think I'm just sick and tired of this project and more than ready to see it launched and off my list of things to worry about.

And I think what bothers me more than anything is that I was hired for my skill and experience in creating custom, hand-coded content management systems, but forced to use a generic, canned system because of the IT administration that was in place at the time. Now that we're too far in to go back, the administration has changed and I've been green lighted to build all the custom systems my heart desires.

And that's almost enough to make me look forward to rebuilding this beast all over again.

7 Comments On This Entry

Page 1 of 1

Curtis Rutland 

04 December 2012 - 08:59 AM


launched and off my list of things to worry about.

I wish that was how it worked for me. When we release, that just means a new round of headaches of production support. Do you guys have a different team that handles that?


04 December 2012 - 09:08 AM
haha... "team".... hahaha

I am the team.... the development team... the support team... the maintenance team... I am a sub-department of one.

And yes, there will be the headache of production support, but it is much easier to modify and update one live site than double all my efforts all day everyday trying to keep a live site AND a development site up-to-date and current with requested content and functionality.

Launching this thing will cut my workload for this particular site by 50%... which leaves that much time for me to start development on the next (and considerably smaller) auxiliary site.

Curtis Rutland 

04 December 2012 - 09:26 AM
Ah. Well, I work for a credit union, so our QA is ridiculously strenuous. Still, when bugs make it into production, the shit hits the fan, and it's all hands on deck to code a fix, test it, notify change control, and have the admins push it. We have such a process overhead (that's necessary because we're dealing with people's money) that production support is way harder than development or pre-deployment.


04 December 2012 - 09:37 AM


Ultimately, I think I'm just sick and tired of this project and more than ready to see it launched and off my list of things to worry about.

Man do I feel that sentiment. Well... maybe not for *your* project, but for mine. A project that was batted around in contract negotiations for about a year, went under phase one development and that went out, people rejoiced, and I moved to a new project.

Then one-point-five development for "custom content to be added" showed up.. That was worked with less fan fare, but it went out and I trudged back to what I was working on before.

Then I was drug back down into the pits because 1.5 needed to be reworked (and morphed) into in 1.75. It was released and no one cared... but it *had* to be done.

Now I am smelling the familiar stench of the beast once more looking for me and 2.0 phase may be happening sooner than I thought with 2.3 already being outlined.


04 December 2012 - 09:43 AM
I would not want to be responsible for a banking site. Ever. I don't think I would be able to sleep at night for fear that I had done something wrong and put thousands of people at risk - or worse.

I get stressed out enough and I'm not dealing with anyone's sensitive or confidential information.

Props to all of you that do what you do - I know I rely on my bank's site like mad - but I don't envy the position you're in or the headaches you deal with.


04 December 2012 - 09:49 AM
modi - We're in version 3.1 on the dev site... I'm terrified of being scheduled for another round of focus groups and 5 more pages of layout and functionality mods before the launch. TERRIFIED.

Curtis Rutland 

04 December 2012 - 11:51 AM
Yeah, we're actually going to deploy our own home-grown online banking solution next quarter. Previously we've used vendor packages, and the homegrown stuff was for the front page stuff, like locations and rates and signup. This is actually a really big deal for us, but it's been a ridiculous amount of work. Luckily we're not implementing the security portion, that's up to a vendor.
Page 1 of 1

January 2021

24 25 2627282930

Recent Entries

Recent Comments

Search My Blog

0 user(s) viewing

0 Guests
0 member(s)
0 anonymous member(s)