Jeremy, Yes, HTTP errors, and yes this is in relation to SharePoint but possibly other cases. Yes in SharePoint because someone does not check out the document when they save (I turn off autosave) they get a HTTP 500 error. If they save while a previous save is in progress they get another HTTP error.
It was with this experience and knowledge of how other servers allow these error pages to be changed, I wondered if there may be a way to provision these with tiddlywiki, so the response could be designed for users. I expect on a PHP server I need only provide or redirect the HTML pages that match where the error looks, but on SharePoint I am not so sure. I imagine this could be handled by tiddlywiki on node (if designed to) but not for single file wikis. *A related aside* Unfortunately I am currently trying to address an issue where a user has all the rights but can't save to sharepoint within tiddlywiki because its throwing a HTTP 405 error *A 405 Method Not Allowed Error is an HTTP response status code that indicates a web browser has requested access to one of your web pages and your web server received and recognized its HTTP method. But, unfortunately, your server has decided to reject that specific HTTP method, so the web browser can’t access the requested web page. When this happens, your website will serve an error web page to your site’s visitors.* This is only occurring for one of three users and I have duplicated permissions etc... with not luck. So just not sure where to look now. Fortunately they can take the file offline, work on it and upload it again, but this defeats the value of using a SharePoint library. Thanks Tony On Saturday, September 21, 2019 at 3:04:49 AM UTC+10, Jeremy Ruston wrote: > > Hi Tony > > I am currently trying to address some save problems with my (single file >> wiki) Wiki on top of SharePoint. A few html errors like 405 and if the >> documents in not checked out 500 that are ungracefully presented to the >> user when the save fails. >> > > Those would be HTTP errors, not HTML errors. They are being reported by > the saver that you're using. Exposing those errors so that you can respond > to them via action widgets would be a biggish job, but making the error > messages themselves customisable might be more practical. Is this is in the > context of your work with Sharepoint? > > Best wishes > > Jeremy > > >> >> I am wondering if it like other sites there is anyway tiddlywiki could >> trap such errors and allow us to write custom responses to such html errors >> as can be done in other environments. >> >> It would be nice to feedback like please checkout filename in another >> window and try again, >> >> I do not know if the underlying technology would permit this but it would >> be helpful. Especially if we can make use of browser sniffer and $:/info >> fields in the message we may be able to intercept and assist people with >> save problems in general. >> >> thanks for your thoughts >> Tony >> > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/031ccaaf-d8f4-4b50-86ca-2d2b5e91e8c5%40googlegroups.com.
