in Web Development

Goodbye PyroCMS, Hello WordPress

As some may have noticed I haven’t posted much about PyroCMS in awhile.  Perhaps some have asked why that is.  Well here is the post explaining that.  I’ve gone back and forth on if I should write this, but I feel like I should for anyone who may have came here for thoughts on PyroCMS.

I had made pretty good progress on my modules for PyroCMS (for those catching up I was working on moving our newspaper site over to Pyro).  I had articles imported into the system.  They were categorized.  I was able to pull in photos and I had even got the front end working (not complete but pretty good).  It was going well.  And then I tried to figure out how to get slugs working (slugs being what creates your URL so it’s SEO friendly).  And I proceeded to bang my head against the wall.  This went on for a few days.  I checked the forum, I checked the ‘secret’ Facebook page and I hung out on the mostly silent IRC group.  While some answered my questions many were just as confused as I was.  I eventually emailed Phil and asked him what the community could do to help.  I had found the documentation was severely lacking and I thought it would help move the project along.  In typical fashion he promptly replied to me about it (which is awesome).  Phil’s response was documentation sucks (it does) and to submit requests for more information.  Not due to Phil’s response but just due to the over all banging of my head against a wall I took a pause on my PyroCMS project.  Well the pause became a goodbye when I started working with WordPress.

In a lot less time I was able to get my content into WordPress, with slugs (it’s automatic if you use the API) and I’ve pretty much got a template up and running.

Is that to say that it’s better than PyroCMS?  Nope.  I have some worries about using WordPress, security being a pretty big one (and the speed), but for the time I have to dedicate to this project WordPress currently appears to be the best choice for me.  The documentation far surpasses what PyroCMS has.  At lot of that has to do with (1) the amount of people working on WordPress and (2) the amount of time it’s been around (it has been frustrating at times as well but eventually I’ll find what I’m looking for). Both of those are things that PyroCMS can overcome in due time.

So what I’m saying.  If you have the time and the will to learn PyroCMS, I think it’s a great thing to learn.  It’s growing and the community is mostly developers which I think is a strength but also a weakness (see documentation).  Support and documentation can be pretty spotty in places.  Wordpress can get you up and running fairly quickly, but it also has it’s issues that you’ll need to address (security being a big one and using older versions of PHP)

If you have any comments feel free to post them up.

 

  1. Hi,

    Are there any links to your exact question? I’ve always found routing in PyroCMS/CodeIgniter pretty pain free to be fair. Any issues have always been due to conflicting routes in the main routes file, with my module routes file. The one people seem to have the most pain with, for some reason, is module routing to a second admin controller. This is literally just a case of $route[‘modulename/admin/awards(/:any)?’] = ‘admin_awards$1’; etc.

    Would be intersted to see what your issue was exactly that caused to use something as awful as WordPress? 🙂

    Rob

    • Rob – I’d have to go and look to see if I posted something. I think that I did. But I know for sure I asked in the IRC channel when Jerel and many other people were there, but playing the silent game! The two issues that kind of set me off to another CMS is (1) the way files and photos are handled with the built in library/module Jerel wrote, which for the most part I worked around (still didn’t like it) and (2) slugging a post/item. I was using Pyro for a newspaper CMS and I wanted to have decent slugging. Slugging ‘appears’ to be possible with Adams streams product, but I couldn’t find any definitive documentation on how exactly it needed to be implemented. Additionally I had written my project with streams so there was the whole learning curve as well (coming from CI it was just easier to build with CI as at the time I thought time was going to be an issue). I got the admin controller down just fine…once I figured it out. As for something as ‘horrible’ as wordpress on some aspects I will agree with you and some of them I will disagree with you. Pyro is a good CMS. But I feel at this point, you have to be pretty damn familiar with programming to get the functionality the WordPress has built in. Having said that the project I was working on has kind of been stalled out.

      Thanks for stopping by.

  2. Fair enough I giess, each to their own 🙂

    PyroCMS does have a “Slug” fieldtype, see http://docs.pyrocms.com/2.2/manual/field-types/slug – it will generate a slug automatically for you. However, you can also include include a simple JavaScript function with the two field names E.g. pyro.generate_slug(‘#blog-content-tab input[name=”title”]’, ‘#blog-content-tab input[name=”slug”]’);

    The blog plugin uses that and you can see in the blog admin controller it simply uses the “append_metadata” function from their templating library.

    I kind of agree with you on the files side of things. Sometimes I’ll use my own image resizer as that seems to resize some images better than the built in files section. When I need to use this I use rewrite the absolute image path to my resiszing acript using htaccess, so I still get vanity URLs like /images/people/rob.png wtc.

    • Rob – Yes each to their own. In regards to the documentation on the slug it doesn’t give you much. What you mentioned about the javascript does help. But trying to implement off of what is in documentation AND what was implemented on the blog wasn’t getting me anywhere (If I remember correctly there is also some Javascript that you have to include for the Slug stuff to work and without hard coding it, it wasn’t going to work, which I didn’t want to do). I will probably re-visit Pyro at some later point, perhaps when it’s all over to Laravel, but right now I feel like there’s some ‘polish’ that needs to be done to Pyro before it’s a product that can be used with a much wider audience. Right now there are very few designers using it, Phil’s even said this, and it’s mainly people who are familiar with CI/Laravel using it.

      Have a good week.

Comments are closed.