On Jan 4, 2008 5:46 PM, Derek Wright <<a href="mailto:drupal@dwwright.net">drupal@dwwright.net</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>On Jan 3, 2008, at 6:28 PM, Khalid Baheyeldin wrote:<br><br>> The reason I added the file element is that I got an error on<br>> another module<br>> (system.admin.inc ...) and that element made it go away.
<br><br></div>For clarity:<br><br>system.admin.inc is not a "module". It's an include file that should<br>be included by system.module when it's doing admin-related things.<br>system.module is a module. The .module files for every enabled
<br>module are always loaded when bootstrapping Drupal. The performance<br>gain from splitting modules up into .inc files (made easier by the D6<br>menu changes) is that you don't have to load all the code that's only
<br>rarely used in your .module files.<br></blockquote><div><br> I realize it is not a module. What I meant was that another module spat out an error message<br>about system.admin.inc, and when adding the 'file' element (wrongly) that error went away.
<br><br>When I changed the other things Peter pointed out, all was well.<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>Peter's point is that you should never tell the menu system to
<br>include a .module file again, since those are *always* loaded. You<br>should only tell the menu system to include a .inc file, never<br>a .module file.<br></blockquote></div><br>Yup.<br><br>Thanks for the extra explanations.
<br clear="all"><br>-- <br>Khalid M. Baheyeldin<br><a href="http://2bits.com">2bits.com</a>, Inc.<br><a href="http://2bits.com">http://2bits.com</a><br>Drupal optimization, development, customization and consulting.