I found category.module (and its bundle of modules) and didn't quite understand what it is for.
Did anybody use it before and can explain what exactly it can do and why it is better then just using taxonomy to categorize content ?
I made some major improvements to the forum module. This was done mostly as proof of my Drupal skills for a potential job. All the coding was done on the live site and can be seen here. The features so far are
forum moderators
better moderation UI for nodes and comments
totally seperate access control.
improved looks, it looks like a forum.
I found that CCK module is going to be used as a node building system instead of flexinode soon. But, as I know there is still no solution to perform a custom search over created content.
Flexinode had its own search, then it was moved into flexisearch.module ... but neither of all existing search solutions provide an ability to create a *custom* search form for each content type with a *custom* query.
What if on the drupal module list showed all the modules in cvs, and the only modules that would be installed at first would be the required modules. Also, all the modules would have .install files. When a module is installed, it is downloaded from cvs and then the .install is run. Themes too. This is only an idea.
Looks like when you have a table that pages each page of the table counts as one read on the node.. Is there a way to not have that count towards a node read..
It makes sense to me that we should only be counting when you go into the node.. and any action that is taken while viewing that node is not counted toward a read/view.
Hello everybody!
I'm very interested in creating a modular approach for cache management on Drupal.
Currently, the "cache system" is composed by three functions on includes/bootstrap.inc: