Ok I give up... where is the documentation that WORKS?
|
TheGorf
Joined: 2005-08-15
Posts: 17 |
Posted: Fri, 2006-07-21 02:28
|
|
Gallery version (not just "2"): 2.1.1 The documentation CLEARLY says that after I have followed creating the tutorial1 modules that: Quote:
Using your Module NO It is NOT fun. Nothing I do can make this stupid module show up. I've created the tutorial directory and modules.inc file: Quote:
bash$ pwd But I get nothing in the administrative interface. I've been trying for over a week now to get answers to a permissions problem. But my requests have been answered with silence. So now I am relegated to writing my own module. But... what a shocker, the documentation doesn't do what it says. So can someone help me please? How do you make a module appear and work??????? For reference here is my problem that I am now writing a module for: |
|
Posts: 89
I had some frustration when starting to develop the two modules I've contributed (Updates and Google Maps). What worked for me was to take an existing module that I knew worked and modify it to do what I wanted instead. If you're interested, the Updates module is quite simple (or at least my last version was), and it even hooks into the permissions system to make sure you only see updates that you're allowed to see.
Beyond that, all I can say is that I've had good success using all of the standard debugging tricks. Turn debug logging on, watch the logs, print out things in places where you should expect them, throw some assertions in, and so on.
--
http://severinghaus.org/gallery/
Posts: 8601
try module.inc