Update: I have fixed Github Bug by pulling a "hacky trick" to their search 
algorithm that detects PAT in file. Hopefully they don't realize their 
issue in the code anytime soon and fix it:) Unfortunately, when bypassing 
their code, the html wiki file was reset, so it'll take about another day 
until the content's all back up

On Thursday, January 21, 2021 at 12:35:31 PM UTC-5 Finn Lancaster wrote:

> @ludwa6, the site is still under construction. What you saw is the most 
> recent of my bugs. The issue occurs because the Github save config is only 
> saved on my PC. I have slightly modified the file since then with a 
> localStorage change, but Github security policies keep revoking my PAT 
> since it is hard-coded in the file. If this were not to happen, it would 
> work perfectly
>
> On Thursday, January 21, 2021 at 12:09:44 PM UTC-5 ludwa6 wrote:
>
>> Sounds like an interesting project, @flanc... So i visited the site, 
>> added a comment (seemed to work fine; nice!), made a slight edit on a 
>> tiddler, pushed save... And the edit didn't stick, it just downloaded the 
>> .html file, as would be the case with any TW5 file hosted on any server.  
>> Is that how this is intended to work, i wonder?
>>
>> On Wednesday, January 20, 2021 at 1:44:19 AM UTC [email protected] 
>> wrote:
>>
>>> Hi all!
>>> I have recently been working on a collaborative tiddlyWiki on my website 
>>> at wiki.finnsoftware.net. I would like to make it so that users cannot 
>>> delete any pages, and have removed most every way that this is possible. 
>>> For any wily users, however, they would just end up using advanced search 
>>> to find the hidden Delete References, so I would like to get rid of 
>>> Advanced Search. Any Ideas?
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" 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/tiddlywiki/5451bb9d-65d8-4fe5-a3ac-1d1bf3821bc1n%40googlegroups.com.

Reply via email to