Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

writing in plugin directory is a bad idea #11

Closed
df8oe opened this issue Nov 7, 2016 · 1 comment
Closed

writing in plugin directory is a bad idea #11

df8oe opened this issue Nov 7, 2016 · 1 comment

Comments

@df8oe
Copy link

df8oe commented Nov 7, 2016

Hello,

I am using getsimple symlinked to mnany different websites. Plugins directory is symlinked and not writeable for customer websites. So it is mandatory to move configuration file config.php to data directory. So p01contact plugin works symlinked, too.

Todo:

  • at first configuration test if p01config.php exists in data directory. If not, copy template from plugins directory.
  • if p01config.php exist use this for storing individual settings of website.

Best regards
Andreas

@nliautaud
Copy link
Owner

Hi,

An implementation of that feature should consider that p01-contact is also functional as a standalone script, or may be used with another CMS (the only handle to GS here being p01-contact_gs.php). Thus, directory structures and strategies may differ.

So you could probably add a "config_path" setting, empty for default path, and if this setting is defined the alternate file is created/used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants