Shared Installation snafu - absolute path or what?

[steve]

s9y has sure covered some ground since we last upgraded, so in the spirit of things we installed the latest 1.1.3 stable release, following the s9y_conf script and double checked things at the shared installation instructions.

Spartacus wasn't around on our last installation, and well it still isn't!

When we sign in to the backend, and click Configure Plugins, our error log says
File does not exist: /www/docroot/bundled-libs/dragdrop.js

In the shared install, we understand this is not supposed to be in the users directory, but in the shared directory; we installed serendipity in the /usr/local/lib/php/ directory and called it s9y.

We checked and it does exist there.

Also, we checked in the /usr/local/lib/php/s9y/plugins and there indeed exists serendipity_event_spartacus directory, within which we see serendipity_event_spartacus.php.

In the tables (mysql) the serendipityPath field is set to /www/docroot/, we changed it to /usr/loca/lib/php/s9y/ and it didn't seem to make a difference. In a shared installation, what value is used in the initial setup screen for "absolute path" to your installation?

Can anyone point us in the right direction? Thanks

[garvinhicking]

Hi!

Spartacus wasn't around on our last installation, and well it still isn't!

Spartacus is not installed by default, but bundled with Serendipity. We cannot enable Spartacus by default because too many hosts are firewalled and cannot work with Spartacus. Checking for firewalling in PHP is virtually impossible.

When we sign in to the backend, and click Configure Plugins, our error log says
File does not exist: /www/docroot/bundled-libs/dragdrop.js

This was a bug in the 1.1 tree of serendipity. The new file 'Dragdrop.js' was first added to bundled-libs, but that path is often not available on shared installations. It was fixed in the Serendipity 1.2 versions, where this file is now put into the default theme directory.

Also, we checked in the /usr/local/lib/php/s9y/plugins and there indeed exists serendipity_event_spartacus directory, within which we see serendipity_event_spartacus.php.

You should be able to install spartacus then by going to the 'Configure Plugins' admin panel and then "Click here to install an event plugin".

In the tables (mysql) the serendipityPath field is set to /www/docroot/, we changed it to /usr/loca/lib/php/s9y/ and it didn't seem to make a difference. In a shared installation, what value is used in the initial setup screen for "absolute path" to your installation?

In a shared installation this path should point to /www/docroot/, so you should better change it back.

HTH,
Garvin

[steve]

Garvin -

Thanks for pointing that out/ we modded another file that continued to look for dragdrop.js there and all is well.

We also moved dragdrop.js to the root installation folder, so that it gets distributed out when the new blogs are installed in the individual user.


Great goings - I am very impressed with the suite.

[steve]

Garvin - thanks but i think we have still a path issue unresolved. In the original post we wrote:

In the tables (mysql) the serendipityPath field is set to /www/docroot/, we changed it to /usr/loca/lib/php/s9y/ and it didn't seem to make a difference. In a shared installation, what value is used in the initial setup screen for "absolute path" to your installation?

In this we mean that /www/docroot/ equals the users directory, which is the target of the htmlarea, templates, template_c folders, as well as the deployment files.

So now we have docrootA, docrootB and docrrootC.

Perhaps we didnt pay enought attention to what your wrote:

In a shared installation this path should point to /www/docroot/, so you should better change it back.

The problems we have are as follows:

When we install a plugin spartacus errors out, when the absolute path value is set to /www/docroot/.


We can set it to /usr/local/lib/php/s9y/ and spartacus reaches out, fetches, and the plugin installs and functions.

However, the path is still 'crossed'. We have to change the path back to the /www/docroot/ to get proper separation of the users' files.

For example, adding media by any users who's path is set to /usr/local/lib/php/s9y/ adds the media to base directory, in other words /usr/local/lib/php/s9y/uploads.

Adding the Gallery Viewer plugin naturally scans that folder, and if we play games and ftp or command line the images over the /www/docrootA/uploads, for example, we get no image display.

So our path definitions in this shared installation are crossed.

When we set the absolute path to /www/docroot/ plugins don't work. Can you give some advice on this please?

[garvinhicking]

Hi!

In the tables (mysql) the serendipityPath field is set to /www/docroot/, we changed it to /usr/loca/lib/php/s9y/ and it didn't seem to make a difference. In a shared installation, what value is used in the initial setup screen for "absolute path" to your installation?

In initial setup, the absoulte path points to the document root of from where the script is called from. In your case that should be /www/docroot/.

When we install a plugin spartacus errors out, when the absolute path value is set to /www/docroot/.

How does it "error out"? You must make sure that the /www/docroot/plugins/ directory is writable and/or properly symlinked.

HTH,
Garvin