I'm a die hard Drupal fanatic, but Drupal is more of a CMS and OSCommerce is more of a Online Shop application. Question is, should I stick with Drupul for my next online shop project, or dare to take on OSCommerce?
Tough to answer without knowing more. Drupal is not very strong if all you're doing is building [x], where [x] is an online store, blog, forum, rss aggregation site, etc. We recently retooled our company store in Drupal using the Ubercart plugin suite, though, and were able to exercise a lot of control over the final results -- and more importantly, intgrate it better with the rest of our site's content.
That's where the real win is -- if you have lots of existing content and/or community, and you want that integrated smoothly with your store. We can do things like auto-suggest products from the store that match the tags on the articles a user is reading, give people access to private forums on our main site based on purchases they make in the store, etc.
If you aren't already an old hand with Drupal, and you don't need that kind of connection, it's probably better to go with a dedicated solution.
(Random notes: Article about putting up the store, podcast about same)
Last autumn, i created several online-shops at a time using Ubercart. There were issues that were hard to solve (e.g. shaping the checkout-view), but in general, it was a good experience, mainly because you have all advantages Drupal has to offer, for example, products are nodes, and the way you present them can be tweaked using all the tons of existing Drupal modules.
I used OSCommerce once, and I nearly went mad adjusting the look as the customer wanted it. So my experience on OSCommerce is pretty bad, and i strongly reommend using Drupal.
If you're going to just create a plain store, without content integration, like Eaton suggests, you'd better go with a dedicated ecommerce solution.
This being said, if you decide to miss on the "extras" coming from using an integrated CMS/ecommerce solution like Drupal+eCommerce or Drupal+Übercart, you should probably not be using osCommerce anyway, but rather look at something with a different code base, like Magento or ZenCart (which derived from osCommerce originally).
If you chose the Magento route, specifically, you will find it is still possible to add Drupal in the mix afterwards if needed, thanks to an existing connector.
OSCommerce may be a practical solution but are you willing to maintain two code bases in the future? Your client will expect ongoing support and you'll need to be proficient in both Drupal and OSCommerce.
I would stick with Drupal if it does what you need. You'll spend less time fixing problems.
I'd stick with Drupal. In OS Commerce installing a module involves following 10 pages of instructions (e.g. insert this code in line 87 in file A, insert this code in line 192 in file B), in Drupal you can upload the module, activate and it works. (Sure you might then need to modify the settings, but most Drupal modules provide an intuitive online interface to do that in.
As you can imagine, once you've installed a few OS Commerce modules, line 87 might be line 104 so the instructions get harder and harder to follow.
I learnt OS Commerce first, then switched to Drupal and found Drupal heavenly to work with in comparison! It also has better SEO, is easier to edit and easier to theme.
Related
I need to make a website for my hockey club. My main purpose for this site is allowing people to sign in and post articles and training schedules in their section. Eg Mens, Womens, Juniors and Masters. I want to have some kind of upload manager that will allow them to choose where they post the info too (eg, Mens, Masters and Homepage).
This is the main functionality I'm looking for at the moment.
The clubs previous website used Joombla which I have hated. I found it to be way to restrictive. Its on a old version of it so there are probably many improvements in the new version but from what I've read it seems like it still has a lot of restrictions in how content is managed. I am open to trying it again tho.
I've used Wordpress before and liked it but that was on a small scale projects and I'm not sure it really fits what I'll be trying to do here, since it mostly deals with blog posts and I'll need to have functionality to upload and display files.
I've had a look around at some other ones like Squarespace and Silverstripe. I'm really liking the simplicity of silverstrip(one thing I hate about Joombla is the clutter on the opening page) and am leaning towards it right now if I can find a nice way to have people post news to multiple pages at once.
If anyone has any suggestions they'd be very welcome. I know html, css, javascript and a bit of php. I'm learning Ruby atm so wouldn't be against using it so I could learn more but it might be a bit much for a sports website.
First off, its nice to see someone that likes hockey too :) You can't use Squarespace, you'll need an Apache server for what you want. You will need some way to store information, so you'll need a MySQL database, probably some advanced knowledge of PHP (I'm assuming you don't know how to connect to databases and do some other functions). Wordpress is too limited, so you can't use that. I have never used Silverstripe personally, but it seems like the best of your options here. You'll probably need some more knowledge of PHP before you attempt to make a members system.
For about a year and a half I used Codeigniter to build my sites. Then a client begged me to build theirs in Wordpress. I soon found the joy of using a CMS (if Wordpress can be called that). So for about the last 8 months I have been using Wordpress as much as possible to buld my sites - I made the content fit the design.
Well, I began to grow very tired of the limitations of Wordpress - I needed more control and flexibility over my sites. So, I have recently started using Drupal 7 (not 6.x - I really like the admin panel).
After working with Drupal now for a little under two months - I have begun to feel like I'm using Stone Age Tools to build Space Age equipment.
So my question is: does Drupal get any better? Do you really have to use Views to display your content? Asking for help on the forums is just a shake better than asking a wall. I feel like to do anything requires a module. Why? Is one better off sticking to a framework?
"After working with Drupal now for a little under two months - I have begun to feel like I'm using Stone Age Tools to build Space Age equipment."
Well, my intiial reaction is that this is what you're going to feel like you're doing when you're working with Drupal 7, which isn't out of alpha yet. A good number of the folks who maintain modules haven't started upgrading to 7 yet, and that means that you're missing out on one of the great features of Drupal, which is it's wide and deep space of premade modules.
Try 6.
Do you need to use views to display all content? No, not at all. You can go in, create a new module, and write the sql and presentation that you want. Or you can find a module that will display things for you. Or, depending, you might be able to get the effect you want just by adjusting the theme you're using.
(As a side note, using an admin theme really pretties up the Drupal experience. I'm fond of rootcandy, although Rubik is nice too. Problem with Rubik is that it's not on drupal.org.)
The strength of Drupal is that by using modules, you don't have to re-write code that someone else has written - you can instead take that code and modify it (with hooks) to do what you want. This means you don't have to write an authentication/autherization system again - it's there in core. You don't need to write up openid handlers - it's in core. You don't need to write code to integrate with twitter directly - there's a module that contains an api that helps out. You don't have to write an xmlrpc server from scratch - you can use the services module.
You don't need to write a website from scratch. Instead, you can start with Drupal, add most of the functionality you need, and then spend your time making it fit what your client wants.
Firstly, you can install the Admin module to pretty up Drupal 6 admin. You don't have to use 7. 7 is still in alpha, by the way. Garland sucks, but, Garland is just a theme- its not 'the' admin itself. The Drupal admin can take the form of any Drupal theme, which is useful in its own right, depending on the use-case.
In Drupal, you can create content types clicking through the interface in Drupal 6 or 7. As far as I can see in WP3, you have to script it. A few clicks vs scripting, the choice for me is not hard there. The first way is a lot more efficient, and a task you can hand off to a non coder to get done.
You don't HAVE to use Views to display content.
You -can- use Views to make the display of content easier, by telling Drupal to gather data and provide a Page, Block, or Feed to display . This lets you create specific sections of content for areas of the site. Otherwise, you would have to create a node, and hijack its template, run a direct sql query yourself AND write the pager functions just to show something easy like the latest 10 "Press Releases" content type. Then, if someone added a new field to that content type, you have to update all that SQL code and display code. Views makes your life easier in that respect. In minutes you can flesh out site sections and arrange content in a myriad of ways. In Wordpress, this method of arranging content without functionality of Views is/was a modern nightmare and a reason I do not want to use it at all unless its a blog and nothing more.
The Drupal Support Forum is tricky. Not all modules are as active as say, Views or Pathauto (being two of the most popular modules). However, SO is also at your disposal. I answer a lot of Drupal questions here. The trick to the Forum there is you have to ask it in the right spot. True, sometimes you may have to wait a few days to get an answer, then again no one -owes- you an answer for a free product. Thats the nature of open source.
Every developer has their favorite modules to use with Drupal, and more often than not, its the same 20 or so modules. It depends on what you are doing, what you are trying to implement. It's not that 'everything needs a module' its that Drupal is such a vanilla install because Drupal does not want to assume your purpose nor overwhelm with options. The UX is something they are trying to improve anyway, and popular modules are making their way into core.
Well, I began to grow very tired of
the limitations of Wordpress - I
needed more control and flexibility
over my sites. So... I have recently
started using Drupal 7
Why not go back to CI? Drupal certainly has it's strengths, but I don't think Drupal will give you any more "control and flexibility" than Wordpress.
If the standard modules/plugins, themes/templates, from WP, Drupal, or Joomla, fill your needs, then using a CMS can be a lot faster than building a site from scratch. But, if those CMSs do not fill your needs, you could find yourself "fighting the framework" and never really getting what you want.
You're just coming out from WordPress, which has great support and is relatively easy to extend to overcome what you call its limitations, if you know basic PHP, HTML, CSS & JavaScript. Every framework has its own potential/limitations.
As a user of WordPress my humble opinion is that you should have stayed with it.
As of you last question, It depends, to stick with one and only one framework has its advantages and disadvantages, the best of all is that you get to know it very well and eventually learn how to extended it. The bad part is that very often frameworks lose popularity and you are left to you own without an active user community and support.
Regards.
All of the popular CMS products (I'd maybe add Expression Engine to the mix) are great for 80% of what you want to accomplish and a huge pain to handle the other 20%.
That's just the nature of the beast.
On the plus side, it's OS so there's lots of people hacking away at it just like you which opens up the potential for someone else already having invented the wheel.
And with bulky enterprise CM solutions like SharePoint I find that you have to reverse the equation to 20/80 (ugh!).
If you're discouraged with Drupal and prefer to stick with WP, WordPress has many thousands of plugins, including ones that can overcome the limitations you're running into and make WP behave more like a normal CMS.
Just do a Google search for "top Wordpress CMS plugins." There's a lot of articles out there that can recommend ways to get WP to do exactly what you want.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 12 years ago.
Improve this question
I am planning to build a training site which will accommodate multiple users. It will also have lots of custom pages with videos in them. Which CMS/CMF is better suited for this project? Please advise..
Wordpress is designed from the ground up to be a blog, but also to be modular. Drupal is designed to be a complete CMS out of the box, but there are also extensions for Drupal too. Both are CMS systems, but again, Wordpress is really designed to be a blogging platform. Also, Drupal is a little more complicated at first and has a higher learning curve.
However, you can do what you are trying to do with either one. In addition to out of the box functionality, you can customize both Drupal or Wordpress. People tend to specialize in one or the other, and the choice comes down to personal preference (people make a living off of being Drupal or Wordpress developers, that's what's great about open source!). Once you become proficient in PHP and the CMS platform of choice, you can build your own extensions/modules and have a very custom website, but I would minimize customization to only what you absolutely need. If you are creative in using the framework and freely available modules, you may not need to write any code.
Lastly, Drupal is getting a complete re-write with version 7, which people have been waiting a long time for! If you want to get into Drupal, you may want to look into the newest version.
Edit: Personally, I prefer Wordpress, I think the admin section looks great, gives you a lot of control, but without being overwhelming (however, my opinion doesn't really matter). I really think Wordpress has a lower learning curve. I'm also pretty sure, although you haven't given many details, but if you are planning on having simple pages with videos on them, and want access to those pages to be restricted only to authenticated users, I'm pretty sure you can do that without any custom PHP coding, just some HTML.
Here's a couple helpful links for Wordpress:
Restrict Page View to Authenticated Users
Setting your Posts or Entire Blog to Private
It can be confusing trying to decide which CMS to dive into; I hope that helps a little!
The answer is Drupal.
I've been running various websites, and few years ago I decided to use Drupal as my main CMS engine and I never looked back.
I used Joomla, phpNuke, Mambo and WordPress before and nothing is as flexible, as maintainable as Drupal.
My biggest website – www.mugen.pl has 14853 registered users so I can confirm Drupal is just perfect for big, heavily used web portals.
Drupal has few wonderful 'social-networking' modules I make an excellent use of to make sure my users are keen to stay on the website, sneak preview: (sorry, I've got only screenshots in Polish):
(source: mugen.pl)
Unfortunately for Drupal, sometimes it takes a while to understand this system. Some theming stuff is not that obvious at first, but the online community is huge and always helpful.
Additionally, Drupal has excellent support for SEO. It’s built-in “path” module allows to set custom URLs for every item on the page, and other available modules (i.e. Nodewords) allow to set custom meta data for every subpage.
When you decided to go with Drupal, you should have a look at the following modules:
Content Construction Kit - http://drupal.org/project/cck
Views - http://drupal.org/project/views
Custom breadcrumbs - http://drupal.org/project/custom_breadcrumbs
Last Node - http://drupal.org/project/last_node
Nodewords - http://drupal.org/project/nodewords
Fivestar - http://drupal.org/project/fivestar
Go with Drupal ;-)
With the new release of WordPress 3.0, I would have to say WP. Many useful updates just came around the bend (menu system et al) that make it even easier to create a "site" out of a WP installation instead of just a "blog".
Drupal is extremely powerful and accommodating to the time-allowed developer, but falls short on the ease-of-use-side of things (at least from my experiences.
In short, if you're looking to make a site that's easy to install, update, and maintain - especially for posting media, go with WordPress.
Hope that helps.
Read both JohnB's and Lance May's answers. The choice is quite tricky so the only way you can make a good decision is to do your own feature comparison/score matrix.
List all the features that you need and assign importance score to them - then objectively go through both systems (or ask again on so) to get their scores.
This will also help you if you have to justify your decision later.
In the end both are good, both have quirks and both will get the job done.
WordPress is just easy to understand, for both the developer and the content editors.
WordPress is best suited for sites with:
1) Typical CMS needs - Pages, Posts, Menus - I would also include embedded videos in this list
2) Low to Moderate Traffic Loads - I know there are sites like Smashing Magazine that user WordPress under high-load, but I am sure there is some custom code added to introduce a better caching architecture and multiple servers
3) Hand off to Client for Content Editing - In my opinion, the best feature of WP is the admin user interface. The sleek visual design, smart use of ajax controls, and the simple layout makes it possible to hand off content editing to "non-technical" people
When I start a WP site, I create a new theme with two files, index.php and styles.css. Then I build my own, custom theme, that is uniquely designed for my project. Examples of my work are http://perqworks.com, http://janemonheitonline.com and http://generalordersno9.com. As you can see, these are not blogs, but CMS sites. I agree, WP was a blog platform, but it has proven itself as a CMS-lite application.
I prefer WordPress because of its extensibility and easy install and modifications.
Version 2.0 has introduced a bunch of features (like custom post types) that makes using it as a CMS easy.
Wordpress is mostly use for blogging and Drupal is used for creating websites. YOu should consider using drupal for that ;)
You may be lured to WP immediately from how quick it is to get started. But in the long term, do yourself a favor and use Drupal. It's a proven CMS framework and less prone to security issues from contributed modules. I can count on two hands how many times a WP plugin has bit me in the ass, even highly rated ones. It has very granular security also, so you know exactly what your users can and cannot do.
I've used both and Drupal is just easier to extend and configure. I don't get why people think it has a huge learning curve.
I also think a big deal breaker is the end user experience - WordPress makes it just so damn easy to manage your website, all whilst looking (in my opinion) rather beautiful at the same time.
Every client I've handed a WP site to has been impressed with it's simplicity - as the iPad put it;
You already know how to use it!
I prefer Drupal over Wordpress . Drupal is made for flexibility . But you must know how to do it , ie all . You may need some time to read how to do with that module x and how to with module Y . But once you have learned you will be comfortable to do any site.
The main advantage of Drupal is CCK and Views . Wordpress 3 have come with CCK , but Drupal has it from version 5. Now we are moving to 7, and it still misses Views :) . Yes ofcourse wordpress is a wonderful tool for blogging with ease. But when talking other than blog, you may want to opt for Drupal . Once you have learned how to do with drupal , you will never say wordpress .
If some one is against Drupal then he may have not used or learned it to the extent :) . So my suggestion for you to checkout Drupal 6 for now , as Drupal 7 is still in alpha for the present time.
I am setting up a web site for a football club and I am wondering which CMS to use.
I am a developer but I am doing this as a favour to a friend and would rather grab something with modules in it (registration, events, calendar, etc.) already. I need to be able to customise it but I had a look around and Wordpress looks like a blogging tool. I am wondering if anyone has experience with the above or any others and if you could shed some light. Thanks
The Major benefit of DotNetNuke is that you will be programming in .Net with all the tools that go with that. And the db is of course, SQL Server.
So if you are a MS guy, then DNN is a good option.
Day Of DotNetNuke is on in Europe this Friday and we will some slides which demonstrate how to use Telerik and sqlDataSource to build modules in minutes. These use Telerik grids to give you CRUD functionality in two simple files. Drop in to Paris if you are free, otherwise, visit the site next week and you can get the slides and some sample code, or else contact me and I will send them to you,
PS. Not sure why, but you will enjoy working on DNN.
good luck and enjoy.
Mark
I can't speak to the current relative merits of the different tools, as it's been a couple of years since I did a comparative evaluation of Drupal, Joomla, WordPress (and 40+ others).
But, I can testify that Drupal would be a good solution for almost any club website.
Out of the box - or with the installation of a commonly used module or three - you could set up:
Recent News
Upcoming events (Calendar)
Blogs (for the club President, Treasurer, other officers, team captains, etc etc)
Media such as podcasts, videos, etc
Of course, all this is optional. There's heaps of documentation online at http://www.drupal.org covering all this kind of thing.
The key point to take away is this: With Drupal, the challenge your friend will face with the website is "what to say" not "How to make it work".
It depends how well-versed you are in a particular CMS for example Joomal or Drupal or some other. If you can customize the things easily and be able to modify the CMS as per your needs, you should go with that one as both Joomla and Drupal have big list of extensions to their name. You should have advanced programming concepts especially OOP when it comes to customizing the CMS. The other option is to create everything from scratch on your own. In the end, I would prefer Joomla over Drupal.
If you have no experience at all with any CMS, I suggest you Joomla to start with. It is easier to learn and probably enough to manage a football club sites. It is also easier setting a Calendar, Event System and Photo Gallery. Drupal is more flexible, it has great user permission control, but it is a bit more complex.
Liferay Portal also has the features you need.
Quick and easy to set up with registration, Calendar ootb. it will be easy for your friend to admin in the future
I'm going to be moving my website to a CMS in the coming months I'd I need some help on choosing an appropriate CMS. Many of the websites I've seen tend to say "use Drupal, hands down". However, my website truly doesn't have a need for commenting or community features. Its pages will need to be modified occasionally, but not extensively. My website will also consist of many programs, each with their own sub-pages and menus.
There are probably 25 people that will need access to the content on my website and will need the ability to update it.
I do like the idea of being able to tag and categorize the content, and the modular aspect of Drupal but is it really right for my website? If not, which CMS may fit my needs better?
It sounds like Drupal would be an excellent solution to your company's needs. I used to recommend WordPress for smaller, single-blog type sites, but now, even for those, I recommend Drupal because you can start small and scale up as your needs grow. It has a very dedicated community and there is a module for just about any need you may have.
I would agree with Drupal. The thing about Drupal is that you start out very small and add on as you need things. There is a ton of documentation, it is well coded, always being expanded on, good forum support, and free. It's the easiest to install, most problem free, and most maintainable CMS system I've seen so far.
You can turn Drupal commenting off with the press of a button, and if/when you decide to add onto your website, perhaps you want an ad rotator, more extensive user permissions, etc, etc, it is all already developed for you and ready to go.
I am not sure if Wordpress supports multiple users on a site.
The smallest you can go for a CMS is something like 10kCMS or the more popular TinyMCE
If it is something small I will go with WordPress as it is easily themed and extensible. There are a lot of community plugins and support. Their documentation is also fairly simple as they don't have a thousand of functions and stuff you need to remember and understand. With some creativity the basic functionality of WordPress is sufficient to solve almost all problems that might arise in small to mid-size website.
I also like Drupal, but you may consider Umbraco as well. http://umbraco.org/ I'd use Umbraco over Drupal if your team is stronger in .Net than PHP. (Really, I think that's a larger concern - what are your organization's strengths? Play to suit them. You are making a decision that will pave the way for many developers besides yourself, and business decisions of your company.) Both are extendable and open source so you can write your own modules/components to customize. It may be cleaner to import into Drupal tables than Umbraco, since it goes down to xslt files. (EDIT: This looks to be no longer the case in the new version - http://umbracohosting.com/umbraco-4---get-excited/one-cms-any-database) From a front end dev perspective, both offer great control of the final output.
From working on legacy stuff a lot, you may end up hiring interns to do the gruntwork. There's bound to be tons of inline tables and all sorts of un-reusable code in there, it may be easier to scrape the content manually and start w/clean markup for the content portions.