encapsulated plugins require question....

[carlwhat]

using a v157 base install.... i'm working on new admin plugin...

lets say there i have a class file, that is in:

zc_plugins/myplugin/1.0.0/admin/includes/classes/class.php

i now want to require() a new script in this class file. previously i might do something like

require_once DIR_FS_ADMIN .  'includes/classes/other_class.php'; 

when i look at the $_SERVER vars, available to me, nothing pinpoints where i am in the file system to refer to new files that ideally i would like to keep in my encapsulated plugin.

is there an easy way to accomplish this goal? i'm guessing there is a ZC var that knows where i am. as i do not...

thanks in advance.

[DrByte]

There isn't any special function or variable for that as far as I recall.

But if the file is in the same or nearby directory structure, you could explore using relative paths with ../.. etc.

However, your post raises a question, and understanding context would help:
WHY are you requiring another file from within a class? Perhaps it's better to put your other desired file code into a class of its own and then simply refer to the class?

[carlwhat]

There isn't any special function or variable for that as far as I recall.

But if the file is in the same or nearby directory structure, you could explore using relative paths with ../.. etc.

However, your post raises a question, and understanding context would help:
WHY are you requiring another file from within a class? Perhaps it's better to put your other desired file code into a class of its own and then simply refer to the class?

drByte, thanks for the input. it seems:

$path_info = pathinfo(__FILE__)['dirname']; 

works.

as far as why... whole other can of worms...

using api wrappers for some of the heavy lifting on common carrier codes rather than hand coding seems to make much more sense to me. and it is actually not within the class, but extending the class prior to the class declaration. ie:

<?php

    $path_info = pathinfo(__FILE__)['dirname'];
    if (!file_exists($sdk_loader =  $path_info . '/prose/vendor/autoload.php')) {
        return false;
    }
    require $sdk_loader;
    require_once $path_info . '/prose/shipping.php';

    class ups extends shipping
    {

does that make sense?

[carlwhat]

i suppose my next question is whether observers work within the encapsulated plugin?

my initial testing suggests they do not. or perhaps it is just the auto loading observers that do not work?

i will try to manually load it.

[carlwhat]

i suppose my next question is whether observers work within the encapsulated plugin?

my initial testing suggests they do not. or perhaps it is just the auto loading observers that do not work?

i will try to manually load it.

i can not get any observers to load from within an observers directory structure. which i suppose is why it is not listed here:

https://docs.zen-cart.com/dev/plugin...ory_structure/

it seems that the auto_loaders operates a little differently from within the zc_plugins directory that outside of it.

it seems that i can make do using a few hacks, but i think being able to load an observer from within the encapsulated directory structure would be a good idea.

[mc12345678]

i suppose my next question is whether observers work within the encapsulated plugin?

my initial testing suggests they do not. or perhaps it is just the auto loading observers that do not work?

i will try to manually load it.

In observing did you both load the observer class and instantiate it as well as ensure that the observer is loaded/instantiated before the trigger point of the notifier is reached?

Also as to the require type condition as DrByte was discussing, the initial portion of the path is not mandated. Note how the admin's index.php file has in it a require includes/application_top.php and not an "admin" related prefix (which of course also doesn't exist at that point in loading the file).

[DrByte]

    class ups extends shipping 

Be careful about declaring a new class named `ups` if the store might already have a `ups` module installed.

[carlwhat]

In observing did you both load the observer class and instantiate it as well as ensure that the observer is loaded/instantiated before the trigger point of the notifier is reached?

Also as to the require type condition as DrByte was discussing, the initial portion of the path is not mandated. Note how the admin's index.php file has in it a require includes/application_top.php and not an "admin" related prefix (which of course also doesn't exist at that point in loading the file).

i turned the DEBUG_AUTOLOAD on. and i could not get the proper file path to come up with for an observer from within the encapsulated directory. so instantiating it is kind of besides the point.

file paths are much trickier from within the encapsulated plugins. i'm not sure how much you have played with them. the auto load does a whole bunch of different things which unfortunately i do not have time to debug and play with.

my testing suggests that currently you will have to do some tricky things from within the auto_loaders config file to get to an observer from within an encapsulated plugin.

would love for you to prove me wrong or show me the way!

best.

[DrByte]

v158 will support auto-loaded observers
(https://github.com/zencart/zencart/b..._observers.php)

But v157 does not.
For v157 you could use the auto_loaders config files to declare which files/classes to load/instantiate "the old way".

[DrByte]

There isn't any special function or variable for that as far as I recall.

zcwilt just mentioned that there does exist a getPluginVersionDirectory() function:

https://github.com/zencart/zencart/b...ginManager.php

which is also used in the various methods of
https://github.com/zencart/zencart/b...InitSystem.php