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 }}
Repository navigation
Add instructions for if symlinking fails for newly-added extensions/skins #398
Well, the directions are "correct" - though whether or not they actually work is a different story. Adding an extension directory to the user-extensions/ directory is meant to cause a symlink to it in the extensions/ directory to automatically be created - so that you can then call wfLoadExtension() directly on that. If it didn't happen in your case, that's a bug.
That's a fair point - right now the documentation just assumes that it will always work. I suppose the best course of action to give to the user, if the symlinking fails, is to "symlink it yourself", i.e go to the extensions/ directory and call "ln -s ...".
Now I'm curious: did you try adding a new extension, and did the symlinking fail for you?
changed the title [-]Website gives wrong directions for installing additional extension.[/-][+]Add instructions for if symlinking fails for newly-added extensions/skins[/+]on May 8, 2024
This is still a good idea to do - but I just wanted to note that, with the latest fixes in CanastaBase (included in the recently-released Canasta version 3.0.3), symlinking of user-added extensions and skins should work a lot more consistently than before - various problems were fixed.
Activity
yaronkoren commentedon May 5, 2024
Well, the directions are "correct" - though whether or not they actually work is a different story. Adding an extension directory to the user-extensions/ directory is meant to cause a symlink to it in the extensions/ directory to automatically be created - so that you can then call wfLoadExtension() directly on that. If it didn't happen in your case, that's a bug.
hexmode commentedon May 6, 2024
With the symlink dependency that may not happen sometimes, it would be good to add a troubleshooting section.
yaronkoren commentedon May 6, 2024
That's a fair point - right now the documentation just assumes that it will always work. I suppose the best course of action to give to the user, if the symlinking fails, is to "symlink it yourself", i.e go to the extensions/ directory and call "ln -s ...".
Now I'm curious: did you try adding a new extension, and did the symlinking fail for you?
[-]Website gives wrong directions for installing additional extension.[/-][+]Add instructions for if symlinking fails for newly-added extensions/skins[/+]yaronkoren commentedon Sep 3, 2025
This is still a good idea to do - but I just wanted to note that, with the latest fixes in CanastaBase (included in the recently-released Canasta version 3.0.3), symlinking of user-added extensions and skins should work a lot more consistently than before - various problems were fixed.
cicalese commentedon Feb 25, 2026
The symlinking is working reliably at this point. We can address this if it becomes a problem again in the future.