Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
The Drupal Fields (former CCK module) are great and a convenient way to present data on your Drupal site, but performance can sometimes be a problem. This is partly because the underlying data of your content type is spread over several tables and there can be lots of joins in the underlying SQL queries.
Just looking for some guidance on how some of the rest of you may attack this as a better starting point. The simplest way to describe the task would be to thing of standing in the middle of a house that someone is looking to buy. You want to be able to allow people to select what goes in the house. This is accomplished easily enough with views filter system and an image attribute (using relationship to switch out the images, similar to how would be done with different color products). But you also would want to allow someone to look around the house at their changes.
I'm working on module development. And before I get too far I was hoping to get some input from everyone about what makes a module "good".
Anything you really like on the interface?
I'm hearing a lot of posts which are saying to back off on the customization of the modules, that too much customization is really terrible and complicated. That instead use "smart" defaults and offer a advanced settings page.
Is there a memory specification it should be at?
Automatic update option vs Notification from module?
Why don't create an area to host "Extra Resources" like open and free Icon Sets, image, fonts and other resources for use by the community?
I'm creating a Base Icon Set that want to make available for use for all using CC or GPL, I don't know yet.
But I think that this could be cool!