What is the difference between ubercart module and commerce module in drupal?
Which is better for building a "groupon like" site?
Ubercart is your best choice at the moment. If you are talking about Drupal 7, in a little while Drupal Commerce will become the best choice but it is still somewhat a moving target. Once it matures a little the power that using Entities/Fields with Rules brings to it is enormous and if you needed to develop Groupon functionality from scratch I think it would be quicker out the gate and more extensible/flexible down the road.
It depends on your situation, but if you’re goal is to simply and easily recreate a Groupon site, you can get 90% of the way there by installing the Open Deals Distribution profile:
http://drupal.org/project/opendeals
This is a Commerce install profile (distribution) and it seems to fit your use case quite well.
You’d then use the Mailhandler suite of modules and once you get to scale you could use an external email service provider like MailChimp or CheetahMail.
The Commerce platform is highly extensible, as is Ubercart, but since it uses the Entity paradigm you have more control over how to display your content with Views/ Panels. Check here for a list of the current contrib modules: http://www.drupalcommerce.org/contrib/all
Drupal Commerce will become the future Ubercart, I believe. It is still in alpha development though and on the project page it says there are no upgrade paths supporting version to version- your best bet is still Ubercart.
There's a healthy and helpful discussion on the drupal.stackexchange.com forum about ubercart/drupal commerce:
https://drupal.stackexchange.com/questions/5/which-e-commerce-module-for-drupal-7
Related
Is there any case that creating your own CMS for a specialized website more advantageous than using a prebuilt CMS such as dotnetnuke or umbraco? Can anyone site a project when they had to create a custom CMS and not used a prebuilt CMS? Where to draw the line from using a prebuilt CMS to a customize CMS? Or is using prebuilt CMS always more advantageous than building your own CMS in any type of content driven website?
With the quality and variety of current open source offerings, I would say it's almost never a good idea to start from scratch. It really comes down to requirements and features. There's a huge variety in the features and user experience of different systems out there. You really need to figure out the priorities (performance vs. ease of use vs. flexibility vs. extensibility vs. SEO) to choose the right one.
I generally go with DotNetNuke with an assortment of custom modules to enhance aspects of its CMS and SEO capabilities. There's just not much you can't do with DNN once you really get to know it. But if performance is your highest priority, another option might be preferred.
I think it depends what the overall goal of the project is. If you are building a marketing website or your project can be easily accomplished with a pre-built CMS then you should certainly start there and build modules or customize a little if needed.
However, if you are building a web application that's core functionality is not just content, page management you have to consider going a custom route. Pintrest, Facebook, Flickr, etc. would definitely not start with a pre-fab CMS.
The Onion started with Drupal at one point but realized their needs were so custom that they ended up doing it all in Python/Django. Plus, with frameworks like Python/Django and Ruby on Rails if you are building web apps you can easily create the CMS features you need.
We do a lot of DotNetNuke, some Drupal and all of our custom web apps we are doing with Ruby on Rails. Once you have the requirements and goals of the project you have to look at your tools and see what is the best for the job. And sometimes it's making your own tools :]
if you move for a prebuilt CMS, you have to use their available functions and do improve whatever your features. but if you go fro a new custom CMS, you are free to customized to the maximum.
What are your requirements? If the majority of your requirements (65% +) are CMS related requirements, than I would strongly recommend looking into existing CMS solutions (opensource or commercial).
On other hand, if your CMS requirements are about 35% of your total requirements, then I would consider implementing in-house, fairly light-weight CMS.
Be aware, CMS sounds like an interesting and easy to tackle task, but when it comes to it, it is likely to be the most complicated project that you have ever worked on, mainly due to its extensibility, security and efficiency related requirements.
It all depends on what the requirements are for the project.
I would like to know if it is possible to integrate zen cart to Drupal 7+ ?
I know that there was a Drupal zen cart integration project http://drupal.org/project/zencart
but it seems only support in Drupal 5.x
thx!
I'm afraid it's very unlikely, efforts for e-commerce in Drupal 7 have been very firmly moved into the Commerce module which is still a wee bit unstable and without a full complement of add-ons as yet.
There's also the Ubercart module which as it happens I'm grappling with myself at the moment. It's fairly complete but be prepared to get stuck in and do some coding if you want it to do anything that's not 'out-of-the-box'.
Drupal is great as long as it is not fully ecommerce. If the site has content plus little bit of selling, then drupal is OK. If you are serious about online shopping for your site, then magneto or a paid software might be a solution.
Magneto is not totally free, the free one is not easy and it is slow.
I have experienced zencart and it is OK if you are going to use it as the main cart integrated with forum or content management systems, the integration is not always easy. zencart is badly designed for a framework point of view, examples, inserting inline css in the template doesn't allow flexibility in overriding especially if the markup output is the result of a module.
I would generally prefer to use drupal for CMS/social network, zencart for online shop, phpbb for forums.
I chose zencart because I am an experienced web developer and I can work around badly designed table-based module output. The main templates are easy to edit. check http://domainpiranha.com/customizezencart.
It is the case in all CMS framework that you have to deal with them the way they are. If you are willing to extensively customize, then programming your own software might be easier.
I need to create a blog for my student organization at my university, and we have access to a folder on the school's AFS system. We would like to install a CMS such as WordPress or Drupal and then interface with that via a blogging client to streamline updating the website. We can My only experience with any CMS is developing an Android app that connects to a Drupal powered blog, so I'm familiar with some of its features.
Any thoughts on the best way to go about creating this blog?
Drupal has 2 core modules that can help you with this, Blog and Blog API. Using both of these modules, you will be able to update blogs on your Drupal site through a blogging client.
Another Drupal user has created a video about blogging with Drupal's Blog and Blog API which you can see HERE.
"Best" is always super subjective.
If what you want is a standard, robust blog functionality quickly with minimal learning curve, you want Word Press. If what you want is a flexible, robust blog functionality with room to scale out and add more functionality over time you might want to make the larger and slower investment of going with Drupal.
Speaking as a Drupal Developer myself, I would reach for Drupal because I favor building with future flexibility in mind, but then I've already defeated the learning curve.
I have never used DotNetNuke before. I'm thinking about giving it a try to help me build websites, and I'd like to hear from other developers who are in a position to compare DotNetNuke with other CMS's/Web Application Frameworks.
I have used both DNN and Drupal to build fairly large, content-based sites. My focus is more on the production side... UI/themeing, module configuration, etc. I'm sold on Drupal, but there may be other choices that meet your needs just as well. I just happened to work with both systems in recent months.
Drupal's core taxonomy module gives you the benefit of creating a relationship between different kinds of content. If you have "article" and "video" content types, you can easily display data from both types based on the shared taxonomy terms. This is huge and something DNN lacks.
Drupal's hook system is also a big benefit when building your own modules or creating "sub-modules" to alter or add to the default functionality of an existing module. This allows you to customize functionality or take advantage of another module's functionality as your application runs. If you purchase a module for DNN, you will have to alter the module if it doesn't meet your needs. Once you do this, you will need to update it each time there's a new release that you would like to take advantage of. DNN modules seem to be more stand-alone solutions. For example, if a DNN module has a rating system, it's only a part of that solution. With Drupal, I can use the "5 Star" rating module in my forums, my blogs, my articles, my videos, etc. There's central configuration for it and I only theme it once.
The themeing layer in Drupal also gives you a large amount of flexibility in that process. My frustration with themeing DNN sites was that I was stuck working with the markup the developer used, with no option for altering the output without hacking the module. With theme hooks and function overrides, I can change the output from those modules to meet my needs (not completely sometimes, but enough), without touching the module code itself.
The biggest problem I had with DNN modules, including some of the most popular, was just a lack of documentation or discussions available for how to achieve your goal. While Drupal's forums can be hard to navigate and you might not always find the answer you are looking for, there are many outlets for gathering information. Honestly, using DNN made me appreciate the community approach of Drupal more.
I was left feeling that DNN would be fine for building sites with more basic needs. But for that, I would still choose something like WordPress or Joomla, considering they have much larger user bases and, in my opinion, are more sophisticated.
Hope this helps you some.
DNN is a pretty good .NET solution for CMS. If you want more flexibility, I would look at SiteFinity for .NET CMS systems. This is a very flexible and elegant CMS for .NET
If you venture out of .NET and want to look at PHP solutions, then DRUPAL, JOOMLA, and WORDPRESS are best solutions. Some comments about each:
WORDPRESS - Is the simplest and most elegant CMS to work with. Originally a blogging software, it has a super-easy user interface, although that also reads as more limited power and features. It's excellent for content driven websites and templates are easily built.
DRUPAL - Is very flexible and configurable, but I find it more complicated than the others. The Admin interface requires more programming knowledge to pull off and adding components and extras is a little more complicated. But, DRUPAL has been proven in the business and government world as a secure and reliable CMS.
JOOMLA - Is my personal favorite. It is also very powerful and I prefer the Admin. interface. Joomla allows for much flexibility and has the most user created modules and plug-ins out there. You have to invent near nothing with this one. I am biased in favor of Joomla, because I use it the most. That said, it has limiting factors against DRUPAL, such as user security features. But this is being fixed in the next upgrade.
Hope that helps as well.
I have development experience using both DNN and Drupal to build content-rich websites. My preference is Drupal for a number of reasons:
Development time-line was shorter; I was able to produce more in less time.
Drupal has a larger and more active developer community. More resources are available to aid in development.
DNN is not actually a CMS. It is only a framework; Drupal is a framework with a foundational CMS.
Drupal is easier to install.
DNN modules cost money; Drupal modules are free.
Actually, I put together some notes a while back when trying to understand the architectural differences between DNN and Drupal. Found those notes, they are here: DNN versus Drupal. Hope this is helpful.
I experienced a fairly high degree of frustration when working with DNN and I don't believe I am alone in that regard. About a year ago, ASPdotnetStoreFront abandoned their involvement with DNN calling it a "disaster to work with".
I am curious to know what piqued your interest in DNN and if you have a specific website project in mind. Regardless, I wish you success and I hope this helps.
I worked in a .NET development shop utilizing Kentico CMS. I agree, it is feature rich and stable. The API and DB are documented well. Overall, it is a great CMS. There is a limited free version: http://www.kentico.com/freecms.aspx
I'm testing out DNN right now. So far, so good, but I think it depends a lot on what you are using it for. I've only been looking at it for 3 days, but so far I do find the documentation lacking or outdated.
I evaluated many of the different Portal/CMS systems out there back in 2004 and DotNetNuke ended up being my choice and I've been very pleased with it, for everything but E-Commerce, ever since. DotNetNuke is endlessly extensible, easy to skin, easy for non-technical folks to update, has a great 3rd party eco-system, and the development team is very active and talented. There isn't a great Articles module in the core but there are several really good ones available from 3rd parties for a reasonable price.
I tried using Joomla a few years ago and hated it. Wordpress is good for a blog style site but doesn't have nearly the power or flexibility of something like DNN. I am intrigued by SiteFinity, Umbraco, and Kentico for sites where all that's really needed is a CMS, but not enough that I've bothered trying them over DNN.
Another good .NET solution - from what I've read - is Umbraco.
Take a look at Kentico CMS. It's commercial, but still affordable. In my experience from dozens of projects on both CMS, Kentico is much more feature-rich, stable and well documented.
Or maybe other OS cms?
I want to form a members website, with registration, member profile and member personal photo galleries
What would you suggest? I'm pretty advanced with PHP just don't have the time to develop from scratch
I don't know much about Drupal but if you're using Joomla you may need to install something like Community Builder and/or Simple ACL. Joomla's default user management isn't great.
Drupal does what you are asking from a basic install with quite a degree of fine grained control over members, profiles, permissions etc. I have set several up with little or no extra modules, plugins or programming.
I actually run one site with several hundred members with not problems. I am not saying you cannot do this with Joomla, just have not had the experience. I think Drupal may well be more "community" oriented in this respect.
I vote for Drupal. Even Obama has voted for Drupal.
Joomla and Community Builder / JomSocial should be a nice pair.
In my experience, Drupal is far more flexible than Joomla. If you're comfortable with PHP, I'd recommend picking it.
Definitely Drupal, especially if you already know advanced PHP.
Nobody has great user features out of the box, but Drupal has more and better quality user-related modules.
Look at drupalmodules.com for 'user' modules in the 6.x versions, and you'll see tons of related modules for each one you check out.
There are modules for advanced profiles, for a percentage (of the profile) completed, user badges to make them feel special, imagecache for excellent image support, image upload with cropping, ckk and views can setup many different kinds of photo galleries from scratch so they are completely customized for your site, ubercart if you want to sell premium memberships, etc.
I think both Drupal and Joomla would be able to handle creating a basic version of what you describe. The turning point is going to be, what more you want to do.
One of Drupal's strengths is first truely uncovered when you develop. You can very easily customize the look and feel of your Drupal site. You'll have more fine grained control of both what it does and what how it outputs it's markup etc. It's a powerful tool, only downside is that it can be a bit hard to understand for normal people. But knowing PHP that shouldn't be a hindrance to you.
I already created 2 Drupal Sites and 1 Joomla Site with this Feature.
Since I've worked with Joomla some years too, I think I can give you some Hints on it:
Drupal is WAY more flexible and professional than Joomla. But you have to put some effort into it. But if you know how to use it, it will do what you want. And since Drupal itself is so flexible the core does handle almost every feature you need. So it is possible to mix a lot of features together and do things nobody has thinked of before.
If you use Joomla, you have to pick a module for this task (like CommunityBuilder http://www.joomlapolis.com/) and while this module is very powerful, it may work together with other modules, but likely it will not.