You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that repair_settings.php requires Sources/Load.php to work.
Whilst that's not an issue per se, it is an issue when you move SMF to a completely new directory (eg: from "site.com/smf" to "site.com/forum").
Repair_settings.php will throw a require_once error that it cannot access Load.php and dies, making it completely unusable.
Changing the associated variables in Settings.php ($boarddir, $sourcedir, $cachedir) fixes the issue.
However, considering this is meant to be a easy to use tool to fix all kinds of Setting issues, it would help if, should Load.php be inaccessible, that the user can define (and/or let repair_settings attempt to find/guess) the completely new basedir in order to fix any other issues that would normally require repair_settings to be ran.
The text was updated successfully, but these errors were encountered:
As per http://www.simplemachines.org/community/index.php?topic=513754.0, on Oldiesmann's request a copy here.
It appears that repair_settings.php requires Sources/Load.php to work.
Whilst that's not an issue per se, it is an issue when you move SMF to a completely new directory (eg: from "site.com/smf" to "site.com/forum").
Repair_settings.php will throw a require_once error that it cannot access Load.php and dies, making it completely unusable.
Changing the associated variables in Settings.php ($boarddir, $sourcedir, $cachedir) fixes the issue.
However, considering this is meant to be a easy to use tool to fix all kinds of Setting issues, it would help if, should Load.php be inaccessible, that the user can define (and/or let repair_settings attempt to find/guess) the completely new basedir in order to fix any other issues that would normally require repair_settings to be ran.
The text was updated successfully, but these errors were encountered: