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
{{ message }}
This repository has been archived by the owner on Dec 15, 2018. It is now read-only.
The second Lawena updated to 4.0.9 it stopped working. I get the error: "Failed to save lawena settings to file". Have tried reinstall, restart and muddled with settings cfg, there is no reason why it shouldn't work from my side.
Thanks.
//
Looks like the folders are constantly getting set to Read Only. Would that be the issue? As soon as I turn Read Only off it just pops back on.
//
Fixed by removing Lawena from the TF directory. Not sure if it's an error on my side. Worth a look at. Sorry for the spam.
The text was updated successfully, but these errors were encountered:
The second Lawena updated to 4.0.9 it stopped working. I get the error:
"Failed to save lawena settings to file". Have tried reinstall, restart and
muddled with settings cfg, there is no reason why it shouldn't work from my
side.
Thanks.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/25
.
I've just read your edits, Ok that's good news. You don't have to extract lawena to a folder related to TF, it's not recommended and it can mess things up.
Yeah, it just seems weird that for the last year or so it's been okay in that directory. Hopefully if anyone encounters the error they will at least get an easy fix from this. Thanks.
The second Lawena updated to 4.0.9 it stopped working. I get the error: "Failed to save lawena settings to file". Have tried reinstall, restart and muddled with settings cfg, there is no reason why it shouldn't work from my side.
Thanks.
//
Looks like the folders are constantly getting set to Read Only. Would that be the issue? As soon as I turn Read Only off it just pops back on.
//
Fixed by removing Lawena from the TF directory. Not sure if it's an error on my side. Worth a look at. Sorry for the spam.
The text was updated successfully, but these errors were encountered: