First, I should mention that "naked" scripts of this type are not the
preferred way of building administrative tools. It is much better to
create an Admin Module and register it, as then you get a lot of
sanity checking and input cleanup for free, not to mention
allowing you to remain inside the Reason interface.
That, said, here's the answer to your immediate question:
Every administrative script that lives in lib/core/scripts/ has to
have a counterpart file in www/scripts/ that includes the file in the
core.
The idea is that all functional code lives in the core, and that these
"stubs" under www exist to provide http access.
An example is the Allowable Relationship Manager, which lives at
lib/core/scripts/alrel/alrel_manager.php but access is through a
script at www/scripts/alrel/alrel_manager.php. The contents of the
latter file are:
<?php
/**
* Stub for the Allowable Relationship Manager
* @package reason
* @subpackage scripts
*/
include_once( 'reason_header.php' );
reason_include_once( 'scripts/alrel/alrel_manager.php' );
?>
I hope that helps!
Matt
> --
> You received this message because you are subscribed to the Google Groups "Reason Discussion" group.
> To post to this group, send email to reason-d...@googlegroups.com.
> To unsubscribe from this group, send email to reason-discuss...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/reason-discussion?hl=en.
>
>
On a related note, is there a sample Admin Module I could look at?
Ultimately that's probably the direction to go in.
--Charles