Git storage does not support file rename #3707
Replies: 8 comments 2 replies
-
| https://docs.requarks.io/guide/pages#single-character-pages All single character paths are reserved to access various parts of the Wiki: | 
Beta Was this translation helpful? Give feedback.
-
| @akaRem pretty sure that's just example file names. I think I'm seeing the same thing. I created a new "2002" folder, and moved all files that were 2002-* into it, and am getting: There is no "2002" folder in the WikiJS front end, and the files are still accessible at their original paths. Which cache can I purge so this is re-read and displays correctly? What is the correct way to move / rename files via git so it is reflected in WikiJS? BTW: the reason I'm making this move is because I have too many files in one folder, so the front end browse navigation really slows down. | 
Beta Was this translation helpful? Give feedback.
-
| OS: Docker I've beed working on reorganising our wiki especially from a local clone of the repository. Then I pushed all changes and I can see the same issue here. 
 I've cleared all caches possible from the UI.  I thought it could come from inner links so we removed them all to switch to a "Browse" navigation only. No change. Is there a way to rebuild the entire wiki tree from the repo? I'd be happy to provide more informations to help if you have specific questions. | 
Beta Was this translation helpful? Give feedback.
-
| This is the same bug as #1440. | 
Beta Was this translation helpful? Give feedback.
-
| I'm also hitting this limitation, and that's really unfortunate. What I really liked about Wiki.js is the ability to keep the wiki in sync with git, so that changes could be made either from the web UI or directly in the repo. But that doesn't work well in 2.x: it's not clear when will changes in git will be reflected in the UI (if they are at all), and I find myself very regularly trying to rebuild the tree or re-render all the pages. | 
Beta Was this translation helpful? Give feedback.
-
| We also ran into this problem when evaluating wiki.js - unfortunately I think this will make the entire git integration and therefore wiki rather pointless to us A simple way to reproduce from a clean state is: 
 | 
Beta Was this translation helpful? Give feedback.
-
| I've submitted a pull request to address this; feel free to try it out. For now, file renames need to occur in Git as separate commits to remove and add the file in the old and new locations. | 
Beta Was this translation helpful? Give feedback.
-
| I'm running Wiki.js version 2.5.268 but renames in git don't seem to get synced. 
 Also, creating a page from git works just fine. | 
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the bug
When renaming a file in a remote git repository (used as main storage source), the old file remains available in the wiki frontend, and the new file is not available.
To Reproduce
Steps to reproduce the behavior:
git mv a.md b.mdgit commit -a -m 'move a to b'git pushExpected behavior
/ashould not be available, whereas/bshould be available.Host Info (please complete the following information):
Additional context
I got that warning in the docker logs, the last line looks weird, it's like if the wiki worker tried to process the filename
/wiki/data/repo/a.md => b.mdinstead of/wiki/data/repo/b.mdBeta Was this translation helpful? Give feedback.
All reactions