> I have no idea where 'c' is coming from--like I said, I've instrumented
> {SERVER,DIR}_{CREATE,MERGE}, which I think should cover everything.actually, probably too much :) you haven't replied to my email yet, where it looks to me like some of your directives are coming through just fine, but that got me thinking... you sayid at the start that you have created one per-server directive and several per-directory directives. you understand that the per-server and per-dir object are different object, right? that ones created with DIR_CREATE are not part of the SERVER_MERGE process so they will not show up in the per-server object, even if they are used on a per-server level? the rules to follow for custom directives wrt merging are this - if you have only one directive, you do not need to write _any_ merge routines - if you define _both_ per-server _and_ per-directory directives then you need to write _only_ DIR_CREATE and DIR_MERGE (though you can maintain them separately from per-server directives if you wish). - if you define _only_ per-server directives then you _should_ use SERVER_CREATE and SERVER_MERGE (but the DIR_ equivalents will work as well, they just add overhead). the reasons for the later two rules are outlined at the end of recipe 7.10 http://www.modperlcookbook.org/chapters/ch07.pdf unfortunately, the first rule didn't sink in until after the book came out, so the example in 7.11 doesn't actually need the per-dir merging foo. whether you are using mp1 or mp2, the stuff in chapter 7 is pretty valuable if you're doing custom directive work. more equally valuable resources can be found under the "More Information" header at the end of this article: http://www.perl.com/pub/a/2003/07/08/mod_perl.html?page=3 HTH --Geoff -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
