This happens at first bootup with no cache files. Nothing in the logs to indicate a problem on debug level.
I noticed that JSPWiki does some calculations based on the requested page to try and find a file on disk. Looks like this happens somewhere around AbstractFileProvider#mangleName but there doesn't seem to be any check for case insensitivity. In this case, the files were created on windows, but served up on linux. I can PR a case for this to normalize to lower case or something like that if you want On Thu, Aug 22, 2024, 7:36 AM Juan Pablo Santos Rodríguez < juanpablo.san...@gmail.com> wrote: > Hi! > > As for the 1st issue, most probably is due to caching being turned on. > Deleting the ehcache files prior to starting tomcat up should fix the > issue. > > As for the 2nd issue, sounds like a very probable cause, log should clarify > that. > > Cheers, > juan pablo > > El jue, 22 ago 2024, 1:43, Alex O'Ree <alexo...@apache.org> escribió: > > > Is there anything special i need to know when creating files outside of > > jspwiki and then copying them into the wiki storage location? > > > > i'm seeing some strange behavior. If i link to the page that exists on > > disk, the link will show as a non-existent article. If i click the edit > > button, i'll get the content of the file on disk. If i press save (no > > changes), it will still register as a non-existent file. If i attempt to > > create/edit it again, then change the file slightly, then save, > everything > > works as normal. > > > > I'm also seeing some strange issues with files loading with jspwiki on > > windows and not loading on jspwiki on linux. This might be the fact that > > the file system is not case sensitive on windows. > > > > are any of these known issues? > > >
