FORBIDDEN changes

Permalink
This is an issue I'm having with Version 8 that didn't happen AFAIK with 5.7.5.13:
When I attempt to change the page name or URL slug in Composer, I get the following error:

"Forbidden: You don't have permission to access (root)/index.php/ccm/system/panels/details/page/composer/autosave on this server. Additionally, a 403 Forbidden error was encountered when trying to use an ErrorDocument to handle the request."

I have TURNED OFF ModSecurity.

What is unique about my installation is that my index.php has symbolic links to /concrete and /packages.
The structure works like this:
root/sitename
     /application
     /updates 
     /cgi-bin
     /.htaccess
     /index.php
     /license.txt,,,robots.txt....error_log...
root/share/concrete5/concrete5-8.1.0
     /concrete
     /packages

index.php:
<?php
symlink('root/share/concrete5/concrete5-8.1.0/packages','root/sitename/packages');
symlink('root/share/concrete5/concrete5-8.1.0/concrete','root/sitename/concrete');
require('concrete/dispatcher.php');


Clues?

yfsneals
 
MrKDilkington replied on at Permalink Reply
MrKDilkington
Hi yfsneals,

If you create a test install of v8 without the symbolic links, do you still experience the issue?
yfsneals replied on at Permalink Reply
yfsneals
Ummm. No. no error.

What I did was make a copy of the site, take out the symbolic links, and put copies of the existing shared directories where they should be.

I just went back and tested a 5.7 site with symlinks for this specific error, and it happened.

I haven't tried turning off autosave. Too late tonight...

Could the ISP have done something? Am i overtaxing symbolic links?

The problem is I will have several dozen sites relying on these shared directories.
yfsneals replied on at Permalink Reply
yfsneals
UPDATE:
After looking at this page:
https://legacy-documentation.concrete5.org/tutorials/how-to-run-mult...

I'm changing permissions to 775 for /share/concrete5/concrete5-8.1.0/concrete/(subdirectories)

It seems to work so far with my 8.1 installation. However, when I tested it in 7.5, I get the error. It seems to be isolated to the page composer.