Page 1 of 1

Error installing plugins with shared s9y install

Posted: Thu Jul 21, 2005 4:15 am
by gwilsonmail
/s9y if a shared s9y install
/wifi is one of many blogs sharing the codebase at /s9y

I went to install the tagged entries plugin - which i don't think i ever installed previously. Spartacus thought otherwise and threw the following error -

Code: Select all

Trying to open URL package_sidebar.xml...
Fetched 34062 bytes from already existing file on your server. Saving file as templates_c/package_sidebar.xml...

Cannot write to directory /home/httpd/vhosts/gizmocha.com/httpdocs/wifi//plugins/. Please check the permissions.
Error: serendipity_plugin_freetag:6856898f17519e75d91875dca03eb16d (serendipity_plugin_freetag)

Fatal error: Call to a member function on a non-object in /home/httpd/vhosts/gizmocha.com/httpdocs/s9y/include/admin/plugins.inc.php on line 664
Further the plugin was partially installed and appears in the list of sidebar plugins, but bearing the name of the last correctly installed plugin - Remote RSS/OPML ... The regular text under the plugin header reads "Error!"

If I delete the plugin and attempt to install again the same happens.

Note that the error message above shows that there is an attempt to install the plugin in the plugin directory of /wifi and not /spy. /wifi has no plugin directory.

Re: Error installing plugins with shared s9y install

Posted: Thu Jul 21, 2005 11:30 am
by garvinhicking
Make the /wifi/plugins directory writable, the error message tells you that spartacus cannot write to the directory. chmod(777) will do. :)

Regards,
Garvin

Posted: Thu Jul 21, 2005 5:57 pm
by gwilsonmail
adding /wifi/plugins and chmod 777 fixed the problem.

There is no mention of this on the shared installation page - http://www.s9y.org/41.html

What would happen if /plugins/ were linked? Could all the plugins exist in one place?

thanks again for the help.

Posted: Fri Jul 22, 2005 11:42 am
by garvinhicking
The shared installation feature is not targeted at providing users the Spartacus plugin, so that's the reason it's now mentioned.

The idea of shared install is that no user-related own plugins are installed, and all are put into the central place.

If you link that, every user that downloads a plugin would make it available to anyone else using the shared install, yes.

Regards,
Garvin