View Issue Details

IDProjectCategoryView StatusLast Update
0016845phpList 3 applicationpluginspublic27-08-13 22:01
Reporterduncanc Assigned To 
Status resolvedResolutionfixed 
Product Version3.0.2 
Target Version3.0.3Fixed in Version3.0.3 
Summary0016845: Plugins not detected on public pages
DescriptionOn the public pages, subscribe etc, plugins are not detected when PLUGIN_ROOTDIR is a relative directory, such as the default 'plugins'. The value is implicitly relative to the admin directory.

The problem arises because the public pages have a current working directory of lists and therefore the plugin directory does not exist.
Whereas the admin pages have a current working directory of admin.

See file admin/pluginlib.php line 22
  if (is_dir($pluginRootDir)) {

When I changed the PLUGIN_ROOTDIR value from 'plugins' to the full file system path then the plugins were detected.
TagsNo tags attached.



24-08-13 00:01

administrator   ~0052212

I guess
   if (is_dir($pluginRootDir)) {

should become
  if (is_dir(dirname(__FILE__).'/'.$pluginRootDir)) {


24-08-13 10:08

updater   ~0052213

That will not work when the plugin root dir is an absolute path.

The problem is the current working directory. That needs to be changed to the 'admin' directory when on a public page prior to the include of pluginlib.php.
That might break something else but I tried adding this at line 29 of index.php and it seems to work:


Or in pluginlib.php temporarily change the current working directory to the 'admin' directory, and then change it back. But that would be redundant when not on a public page.


27-08-13 22:01

administrator   ~0052224

rev4212 - expand the pluginrootdir, if not found as is.