Drupal Checklist

CHECKLIST FOR DRUPAL

1. What programming language is it written in?
• php, required version php 4.x
2. Which database is used?
• mysql v3.23.17 / PostGreSQL
3. What are the other packages it needs?
• no extra packages are needed
4. Does it require any additions to be made to apache?
• no, required version of apache is 2.0.x
5. does it have good collection of templates?
• yes, they are widely available. But sometimes some sections visible in one template may not be seen in others.
6. Is there a user friendly gui to edit the templates?
• No
7. Can we define our own drop downs?
• No.
8. Does it have an auto expiry feature?
• No.
9. How does html editing take place?
• Via full html text editor or the rich text editor.
10. How does image uploading take place?
• there is a content type image. That can contain images which can be uploaded via a browse button.
11. Can we upload files, pdf docs, etc?
• Yes.
12. Can the admin see who is online?
• Yes. That can be controlled depending upon whether he wants to see that or not.
13. Is there automatic mirroring between machines? if yes which type-master slave or multi master
• No.
14. Where are the pages kept? In database or flat file system?
• In a database. the revisions of the pages are also kept within the same table of the database.
15. Is there a separate template for separate sections?
• Yes that can be done.
16. Is there a text based search facility provided?
• Yes.
17. Do we need to add hyperlinks as pages are created?
• If the pages are linked to a particular section then the node id of the page is to be added.
18. Access control - Is there access control to -
• Create pages - yes
• View pages - yes
• Edit pages - yes
19. Can a user register himself ?
• That can be controlled as we can have options for -
• User can register himself and approved without admin permission
• User can register himself and will be registered only after admin approval
• Only admin can create users
20. Is there logging of work done (version control)
• Yes we can control that whenever a node is edited its previous version is saved and can be reverted back to and if user is privileged enough previous versions can also be deleted
• Admin can also check out various logs for top pages, top hits, recent posts