Closed xiopt closed 3 years ago
I created a empty ss-constats.php file for now
Thanks for reporting @xiopt
I believe this is happening on new installs because ss-constants.php
is created by ss-worker
which doesn't run until a few minutes after ss-install
has completed.
So for now I've added that snippet to ss-install-wordpress-config
as well to ensure this doesn't happen.
Ref: https://github.com/littlebizzy/slickstack/commit/e041b91a7dc0986fdba4e55a701677a7496bfaf0
Until now we've tried to avoid having any bash scripts that install SlickStack core stuff, to avoid confusing users, etc... instead we've just included that in the ss core cron jobs and bash scripts. In other words, the creation/permissions of the core files and folders that involve SlickStack's general structure do not have dedicated scripts currently.
In the future we may need to rethink this a bit, but for now it should be fixed.
Oh ok, I thought it was a leftover file from previous versions. Thanks for the info.
Another note on this is that there are still some cases where the public mirrors (GitHub) times out, resulting in empty files or even non-existent files. We are continuing to improve file integrity checks via wget
to avoid this happening.
See this Issue for more information: https://github.com/littlebizzy/slickstack/issues/90
Just installed the stack on a fresh installation of Ubuntu 20.04. The installation went well, everything works from what I tested, but the error log is spammed with this line:
include_once(/var/www/meta/ss-constants.php): failed to open stream: No such file or directory in /var/www/html/wp-config.php on line 27
Contents of
/var/www/meta
: