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

Checking streams instead of hardcoded folders #11

Open
bkostrowiecki opened this issue Aug 11, 2017 · 5 comments
Open

Checking streams instead of hardcoded folders #11

bkostrowiecki opened this issue Aug 11, 2017 · 5 comments

Comments

@bkostrowiecki
Copy link

Hi there,

I tried to use this plugin to check if I can use Grav CMS on my hosting. I found a problem with permissions of logs directory. I changed the stream for logs to a different folder, but sadly Problems Plugin still checks the hardcoded logs folder instead of new folder pointed by logs stream.

I can think of two possible solution.

  1. Create a configuration file with paths
  2. Using streams from Grav CMS instead of hardcoded paths

What do you think about this?

@rhukster
Copy link
Member

Streams are not fully loaded when problems runs. I’ll,check tho.

@jza34
Copy link

jza34 commented Oct 20, 2019

Hi,
May someone have a look at this issue because today I am in this situation with latest version of GRAV.
Hosting company is 1&1, the logs directory is not writeable by the owner...by concept. So the alternative stream grav-logs is working but no way to activate the "problem" plugin without being stuck to error 500.
Thanks guys for the good work so far!

@mahagr
Copy link
Member

mahagr commented Oct 22, 2019

Just disable the plugin and you should be fine.

@bkostrowiecki
Copy link
Author

Yeah, I did it, but I don't believe it's a best possible solution. I assume this plugin should help in checking server configuration, so false negative is rather annoying.

@mahagr
Copy link
Member

mahagr commented Oct 22, 2019

@rhukster Streams should be fully loaded by plugin initialize, so I cannot see why it won't work.

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

4 participants