How to require a /includes/classes file from admin page?

[neekfenwick]

Hiya,

I'm having trouble require'ing a class file from an admin file. I have zen cart 1.3.8a in a normal apache install, located at web root, nothing fancy. I've written a custom class (or three) e.g. /includes/classes/warranty.base.php which work fine from the customer-facing /includes/... side of things.

My admin side has a helper class in /admin/includes/classes/warranty.php. How should I require my warranty.base.php file from the admin's warranty.php file? That is, a class file in /admin/includes/classes is trying to include a class file from /includes/classes. I'd like to use the zen cart defines such as DIR_WS_WHATEVER if possible.

require(DIR_WS_CLASSES . 'warranty.base.php'); 

generates:

PHP Warning:  require(includes/classes/warranty.base.php) [<a href='function.require'>function.require</a>]: failed to open stream: No such file or directory in <obscured>/admin/includes/classes/warranty.php on line 8

That makes sense, the path should not be relative to admin, it should be relative to web root. A very basic hardcoded attempt that I thought should work..

require('/includes/classes/warranty.base.php'); 

generates:

PHP Warning:  require(/includes/classes/warranty.base.php) [<a href='function.require'>function.require</a>]: failed to open stream: No such file or directory in <obscured>/admin/includes/classes/warranty.php on line 8

I'm confused as to why that second attempt failed.
The warranty.base.php file definitely exists, I can direct my browser to my.site.com/includes/classes/warranty.base.php and get 200 OK.

Annoyingly, this does work:

require(DIR_WS_CLASSES . "../../../includes/classes/warranty.base.php"); 

This would seem to resolve to "includes/classes/../../../includes/classes/warranty.base.php", which relative to the /admin/includes/classes/warranty.php file would be "/admin/includes/classes/../../../includes/classes"

Thanks!
Nick

[DrByte]

Either of these will work:

 require('../includes/classes/warranty.base.php');  

 require(DIR_FS_CATALOG . '/includes/classes/warranty.base.php');

[neekfenwick]

Either of these will work:

 require('../includes/classes/warranty.base.php');

Ah, so the paths are relative to the page loading them (/admin/my_page.php) not the php file in which you place the require() directive (/admin/includes/classes/thing.php).

Many thanks for the pointer. I'm now using the DIR_FS_CATALOG approach, as my require's are in an /admin/include/classes file that I want to be able to require from any admin page without worrying about the position of that admin page in the file structure.

+1
Nick