Subject: Comment hacks
Posted on: 01/11/04 07:21pm
We are soon to embark upon some coding of some customised comment features and I was wondering if someone could help me with a couple of questions.
1. Is there a field in the comments table that I could use to encode (bitmask) 4 optional attributes? If not, what is the chance of the maintainers adding a "status" field to the official comments schema? The status would use bits 0-3 of a byte field, with 0 being standard (default behaviour), decimal 1, 2 and 4 representing other statuses - some mutually exclusive. Obviously, if accepted, we would have to document what each bit represents.
2. do duplicate functions in lib-custom.php automatically overide those in other libraries (specifically lib-common.php)? If not, what mechanism would be recommended to overide the comments output and administration?
With one (1) above I could of course create another table linked on the comment id, but I was hoping to avoid another join for performance reasons and I want to stick with the officially supported schema if at all possible. Hope someone can point me in the right direction.
Posted on: 08/11/04 10:35am
1. There is no such db column, but you can just a column to the comment table. Geeklog does not clober extra columns on tables during upgrades.
2. No, unfortunately PHP does not support function overriding at all. We could clobber together support for this my doing some magic, but it doesn't seem worth the trouble. A better method would be to request plugin hooks where they don't exist and are needed (within the function to override function behavior on a per plugin basis).
Posted on: 08/11/04 02:54pm
There's also a discussion
about this on the geeklog-devtalk mailing list.
Geeklog - Forum