Wanting to understand plugin's $filePathXXXX variable #5811
Unanswered
mc12345678
asked this question in
Q&A
Replies: 1 comment 1 reply
-
No explanation provided, but looks like it's addressed in #5879. At least that code make sense, even if currently a draft. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
zencart/admin/includes/application_bootstrap.php
Lines 170 to 189 in 0bf8a8f
and
zencart/includes/application_top.php
Lines 213 to 230 in 35dc5cb
Why does
$filePathAdmin
resolve the filepath to:PLUGIN_DIRECTORY . 'classes/admin'
instead ofPLUGIN_DIRECTORY . 'admin/includes/classes/'
? (Note two things about the original code, the appended content doesn't address the class being in theadmin
'sincludes/classes
folder and that the final character does not include the directory divider.)and why does
$filePathCatalog
resolve the filepath to:PLUGIN_DIRECTORY . 'classes/'
instead ofPLUGIN_DIRECTORY . 'catalog/includes/classes/'
(Noting here that the original code does resolve to a path that ends with the directory divider.)Further, why is
$filePathAdmin
even defined in the catalog side? Is consideration being given for catalog side operations to have access to plugin's admin software?Meanwhile the current direction about plugin directory structure (which doesn't (yet) describe the above filepath) is: https://docs.zen-cart.com/dev/plugins/encapsulated_plugins/directory_structure/
(Update was that in attempting to explain the expected, I still demonstrated an incorrect expectation in the example path.)
Beta Was this translation helpful? Give feedback.
All reactions