By aryanto on

Hi everybody,

After more than a year using Drupal, I am still wondering the real advantage of CCK and Views. I experienced only disadvantages, such as unpredicted problems due to compatibly, etc,. I tried to use them at the beginning, but never actually use them until now. In my case, I found it much easier and the pages load faster by implementing what I want using simple modules which I built for that.

So could anybody give me practical examples of the advantage of using CCK and Views modules?

Kind regards,

Anto

⋅ Categories: Drupal 6.x

Comments

Jeff Burnz’s picture

Jeff Burnz commented

- rapid prototyping
- play well with many other modules
- low entry level

Example - image galleries, blogs (without the blog module), archives, showing user contributed content on users profile + many many more.

Add Panels and the options really start to open up.

Pimp your Drupal 8 Toolbar - make it badass.
Adaptivetheme - theming system for people who don't code.
aryanto’s picture

aryanto commented

Actually, the main reason I tried to use CCK and Views was to build the image gallery with the specification that I explained on http://drupal.org/node/246624.

If that is not impossible, it was quite difficult for me to build that using CCK and Views. Especially that I want my gallery to be updated on the fly when I add the pictures to the gallery. So without touching anything on the administration page a part from only uploading the pictures to the folders. I finally use Brilliant Gallery which I massively modified to also manage all the picture related displays on my site. That is why I said that it is easier to build a module than using CCK and Views.

As I am lazy to always Google for information when I am stuck doing PHP scripting, I am wondering whether I should use CCK and Views for managing blog archive for instance, instead of creating a module.