At my local apache devkit and public staging server the symlinks to the plugin assets work. they are created and followed. but for my clients server (apache) they do not – 403 and error page. the htaccess file is identical. Options +FollowSymlinks should be available. at least provider support says so.
using Options +SymLinksIfOwnerMatch instead does not help.
symlink is created with same user and group as all other files. 777permissions.
Are you creating the symlinks with PHP, or by hand in the terminal directly on the server?
I’ve use symlinks to share stuff between projects, but i’ve only done it with folders, not individual files. Maybe try that?
Can you give a bit more detail about the use case? How do you deploy? Maybe that process is upsetting permissions somewhere. Have you checked the permissions of each part of the path?
its cheap shared hosting. i do not have access to the terminal. since it works in similar setup flawlessly i am suspecting a faulty/to-secure apache conf. i just need to find out what exactly.
Hmm…I was going say maybe do a shell exec with php and run the terminal command that way. I dont know what php symlink() does technically to create it. Probably just that. If its shared hosting, they’ve probably locked down php from executing commands like that.
Is the server running cPanel? Have look in it - sometimes there is a Terminal app inside it. I’ve seen it on some shared hosting, but its locked down to just that hosting folder. Might give you more info.
Do you have to use this cheap hosting? Maybe switch to fortrabbit. They give SSH access, even on the 5 Euro plan.