Answer / ritesh bhargav

Joomla and Drupal are two magnificent Open Source Content
Management System which provide the framework to develop
effortless with various ready to us modules and website in
short span of time.

Main differences are as under

1. Drupal use smarty template where as on the other hand
Joomla dose not

2. Joomla uses plugin and modules whereas Drupl has module only

3. In drupal php code can be written directly whereas in
Joomla you need to install plugin for php support

Answer / hari krishna prasad

joomla and drupal those are open source content management
system .this two softwares using for framework.

Answer / mahesh

Site Building
- Flexibility & Power: Drupal looks significantly more
powerful — much more flexible. Looks like Views, CCK,
Panels give Drupal a huge advantage over Joomla. You simply
can’t get that flexibility with Joomla. Joomla developers
design around their own paradigm with very little
flexibility. You can get up and running much quicker with
Joomla, but you will hit the wall sooner or later.

Performance
- In my initial tests, Drupal blows away Joomla. With the
new version of Joomla, the good template makers junk them up
with gee-whiz gadgets that are not suitable for the enterprise

Learning Curve
- Joomla is far easier to get up and running. Even with all
the free videos, blogs, etc, Drupal is still a lot more
challenging. Big oppty for comprehensive business
business/enterprise book/education

Templates
Joomla wins by a huge margin. For example, companies like
Joomlart, Joomlashack do a good job. Drupal theme companies
are simply horrific. What’s needed is a Template strategy
that emulates the requirements for the top web sites in the
country and, bundles modules, blocks etc. that work
out-of-the-box to give businesses a head-start. For example,
with our Websphere Portal product, we deliver incredible
Themes/Skins that are rock solid and professional with no
fuss or muss. I think you guys have a good stated strategy,
but you’re missing a big oppty to deliver what enterprises
really need.

Your templates are the best I’ve seen, but, an enterprise
that is just getting started with Drupal will still have a
huge ramp to climb to get a News site, mag site, etc. to
look good. Joomlart delivers their Teline II template with
a special install that gives you all the sample data, all
the components in place — everything in place.

Finally, the biggest problem with Drupal templates is that
the developers completely miss one of the key elements that
any evaluator looks at: the menu system. If you don’t have
a professional navigation system on your web site, you’re
perceived as a low quality site. The other top items:
Layout, Graphics, speed are also critical, and Drupal
developers don’t seem to care. Exception:

Code developers
Based on my limited review, it looks Drupal coders are much
more professional, skilled, disciplined. Good Joomla coders
are rare. Must have something to due with the Drupal
culture. I’m sure the Joomla devs are just as capable, they
just don’t institute the same rigor

Admin
Drupal’s backend admin functionality is bad. The front end,
backend separation is tenuous and confusing. Joomla is far
better.

Content Management
- Drupal’s taxonomy system is excellent. Joomla’s
"straight-jacket" approach (Content items confined to one
Section/Category) is poor. Joomla’s admin console is much
easier to organize, find content. Joomla’s WYSIWYGPro is
better than the options available for Drupal.

Content Presentation
- Drupal’s tools are very, very good — they don’t come close
to the built-in power of IBM tools — but they’re light years
better than Joomla. I like CCK, Views, but wonder why they
aren’t part of the code base. Seems odd. WIth Joomla, you
have to acquire components that will meet 60-80% of your
needs. For example, iJoomla has a tremendous news
component, but it will never meet the capabilities of
Drupal’s CCK, Views, etc.

Multitier Deployment
I’m shocked that there are no good tutorials, articles,
education on the proper method for implementing Dev, Test,
Staging, Dev environments. Drupal and Joomla communities
both suffer from this. Also, basic backup and restore is
not addressed adequately. The Drupal community is clueless
on this. Joomla at least has two good solutions. If I
decide to recommend Drupal for a production site, I’l
recommend use Xcloner from Joomlaplug — this product will
work with Drupal and does backup and restore of the site and
the SQL db.
Summary to Date

- Use Joomla if you want to get nice looking site up quickly
and can deal with a slower system, rigid content
categorization and limited design/configuration options.
- Use Drupal if you want high performance, scalability, good
content management and significant design flexibility. But,
be prepared to spend a lot of time/money to get the site to
look professional.

Answer / maninder dhiman

Joomla and Drupal are both CMS but they have lot of
difference. Like Joomla use plugin and modules but in Drupal
we can use modules only. Drupal is SEO Friendly whereas in
Joomla you need to buy a plugin. Drupal use smarty where as
Joomla use his own code format. In Druapl we can create
multiple website with single installation.

Answer / ajay kumar

1.joomla is easy to use. even the layman can understand the
admin panel for making chnages where as drupal admin is
quite complex.

2. drupal is best when you want multiple sites and only backend.

3. drupal use smarty , very easy to understand

4. if you know smarty you can easily do make the module in
drupal but in joomla you need to know the understading of
the inbuilt classes

5. lots of help you will get of joomla where as for drupal
help is not available widely

6. i suggest you to learn joomla if u have little knowledge
of core php other wise go for drupal

Answer / maninderdhiman

Joomla and Drupal are both CMS but they have lot of
difference. Like Joomla use plugin and modules but in Drupal
we can use modules only. Drupal is SEO Friendly whereas in
Joomla you need to buy a plugin. Drupal use smarty where as
Joomla use his own code format. In Druapl we can create
multiple website with single installation.

Answer / sukant

Mambo(Joomla):
The user and administrative interface for Mambo(Joomla) was
one of the best-designed options on our shortlist. We were
also interested to note the emergence of Soapbox, a
Mambo(Joomla) toolset geared towards the nonprofit
community. The Soapbox toolset is however limited (at this
point) to integration with the Democracy in Action CRM, and
to single sign-on among sites. The information architecture
of Mambo(Joomla) itself proved incompatible with the
telecentre.org project, since it is structured around
categorization (rather than tagging), which in practice
imposes such limitations as precluding multiple
categorization of inbound RSS feeds. Since much of the
telecentre.org network’s content will need to be distributed
to multiple categories (e.g. a story on a Bolivian wifi
project needs to be tagged “wifi” and “Latin America”), the
categorization structure was a deal-breaker.

Drupal:
With a fast-growing user base in the non-profit sector,
Drupal’s strong online community focus made it an appealing
prospect. Most importantly, Drupal was alone among all CMS
options in its compatibility with a distributed network
approach. The platform is essentially built for exactly this
kind of approach: it supports ubiquitous outbound RSS feeds,
complex aggregation of inbound feeds, per-feed or per-item
non-exclusive tagging, and native support for blogging.
Compared to the other options, which are virtually all CMS
platforms that have developed distributed community
features, Drupal is innately oriented towards community
networking and distributed content creation. The following
outlines how we anticipate using particular features of the
Drupal platform to support core elements of the
telecentre.org web strategy.


A great place to start is OpenSourceCMS, a site with user
reviews of pretty much all the major players in the CMS
space. What sets them apart is that they also provide live
demos of each CMS they cover. You can actually log in to the
front end or the back end of each one, reconfigure it, and
make changes to your heart’s content. Every two hours they
“reboot” and put everything back to a fresh install. It’s a
great way to experiment without having to go through all the
time and hassle of installing each system yourself.
Installing Drupal and Joomla on my host
In addition to testing each platform on OpenSourceCMS, I
also wanted to install them myself to gauge how easy they
would be to work with. Fortunately my hosting provider, Host
Gator, uses a product called Fantastico which makes
installing Drupal and Joomla as simple as a few mouse
clicks. Both installed successfully with minimal effort.
Purists abhor Fantastico, but for my purposes, it was a
quick and easy way to get up and running quickly to be able
to start kicking the tires of each product.
Installing Drupal and Joomla locally
As I’ll need a test environment before long, installing both
products on my local machine is a good idea as well. Before
I can do so, though, I need to install the LAMP (or WAMP)
stack commonly used by Open Source software. LAMP enables my
desktop to act like a web server, so that I can run
everything from my local machine just as if it were running
on my host.
For the curious, LAMP stands for Linux Apache MySQL PHP, and
they are the four products that make up the foundation that
Drupal, Joomla, and countless other products use. WAMP is
essentially the same thing, but uses Windows as the
operating system. Each product offers its own installer, and
I got WAMP working on my local machine in no time.
The local installations of Drupal and Joomla were a bit more
involved. I had to understand how to setup MySQL databases,
and know the right answers to a number of questions,
although the wizards that each product offered were pretty
good. A complete novice would probably be overwhelmed, but I
found it pretty much a snap to get both going quickly.

Use Mambo(Joomla) when:
* you don't know about the tech stuff at all
* you want easy install & setup with your mouse
* you don't want to learn the tool you're using
* you don't need to integrate other scripts etc. to your site
* you want a candy site and don't mind several other sites
using the same template(s)
* you don't need SEO out of the box
* you don't care about server resources
* you're running (or planning to to run) only one or max a
couple of sites
* you don't need one log-in to several sites
* you don't need user groups & permissions
* you don't run membership site(s)

Use Drupal when:
* you want a rock solid & high quality platform for your sites
* you want or need a real multi-site-feature (only one
installation for several sites)
* you need any kind of user groups & user permissions
* you need to run also membership- and community sites, not
only CMS etc
* you want a Powerful templating system
* you're ready to invest a bit of your time in order to
realize all the huge possibilities of Drupal
* you understand the meaning of clear, high quality code and
API (easy to integrate with other solutions etc)
* you want flexibility and don't like limitations

A number of Major Advantages of Drupal over Mambo(Joomla)

With Drupal, you can set up several sites with only one
installation ...think about that, when you have tens of
sites and security holes are found almost daily! ...what
about then, when you quickly need to uppdate some additional
components / modules / themes... you actually face a lot of
work in Mambo(Joomla) - in Drupal you do it only once.

With Drupal, you can (if you want to) use the same
log-in-details for different sites... in some cases it opens
quite interesting possibilities.

Drupal has also SEO-friendly URL's out of the box... for
Mambo(Joomla), you need to buy a commercial component from a
core developer or use labor-intensive free ones.

Someone mentioned, that Drupal is focused on communities...
you're right... however, it does not mean, you can't use
Drupal for content sites. Actually, Drupal is a great choise
also for content sites. I can't imagine Mambo(Joomla) as a
natural community building system, though.

When talking about user profiles and permissions to
different parts of the site, Mambo(Joomla) is actually a
joke... on the other hand, Drupal is the opposite... it's so
easy to set up and fine tune different user-roles and give
them some permisssions

some main differences are
=========================
1. Drupal use smarty template where as on the other hand
Joomla dose not

2. Joomla uses plugin and modules whereas Drupl has module only

3. In drupal php code can be written directly whereas in
Joomla you need to install plugin for php support

Answer / mayank drupal developer

Joomla is based on a framework that is made of classes and
objects while drupal don't use the class/object model.

drupal make use of associated array. Drupal provide the
hooks to extends the functionality. It supports the function
and theme overriding on various levels. It has a very big
code base that is very easy to understand.

Drupal has the some modules in pocket that the joomla going
to copy the functionality. One of them is CCK

What is session_register()?

0 Answers  

Tell me how to retrieve a cookie value?

0 Answers  

How can we encrpt a text?

3 Answers  

How are variables declared in php?

0 Answers  

How to get elements in reverse order of an array in php?

0 Answers  

when you will get the message/error "headers already sent"?

5 Answers  

What is the difference between html and php?

0 Answers  

What is the difference between php traits vs interfaces?

0 Answers  

What are the different types of statements that are present in php?

0 Answers  

What is button in html?

0 Answers  

How to create the PHP Script to Calculate the Age Using the Inputs Of our Birth date and the Current date?

6 Answers  

How do you define a constant?

0 Answers