-
Notifications
You must be signed in to change notification settings - Fork 27
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
Updates to Mediawiker delete custom wiki entries in sublime-settings file. #178
Comments
Default on the left side, User settings on the right. |
Correct. My defaults were overwritten. That is where the Is a second EDIT: And as previously stated, if the defaults are overwritten, such as |
All your settings, including This scheme works in all ST plugins. |
Huh, never knew that. Alright then. |
Greetings again. I initially posted my issue with a custom wiki in issue #171, however I had received an update to Mediawiker shortly after that. I have recently gone back to work on my wiki entries again and noticed that none of the Edit Panel functions were working. I thought that my issue regarding link suggestions was resolved, but in actuality, Mediawiker was not connected to any wiki at all.
My
site_active
settings remained the same, beingTCRF
, however aTCRF
entry no longer exists due to the update. As such, Mediawiker threw no errors at all informing me of this, and simply silently failed at everything I tried to tell it to do, such any option in the Edit Panel that involves interacting with the wiki. The only error messages displayed where when I attempted to open a template for a new page, in which case this error was thrown:So I guess I am wondering if I can define a site in the User folder so the site is not overwritten by updates.
It should also be noted that if the suggested fix #171 (comment) were implemented and changed
"page_prefix_min_length": 100
it would be defaulted to"page_prefix_min_length": 3
after an update.EDIT: After idling about in a .wiki file that I had previously used the "Open Page" function with, it now occasionally throws this error in the console:
The text was updated successfully, but these errors were encountered: