Hi Jeremy!
My experiments shows
- When save to GitHub you don't see the "Start to save" as we see for
tiddlyspot. So you can realize if clicking button start saving or not
- When save using master branch it works fine
- When save using master branch and sub-folder, TW create the fold
Thanks Mark, Cade. That's helpful, I'll do some testing.
Best wishes
Jeremy
--
Jeremy Ruston
jer...@jermolene.com
https://jermolene.com
> On 27 Aug 2019, at 17:11, 'Mark S.' via TiddlyWiki
> wrote:
>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki"
For me, I can save to master but not to any other branch. I am not
rapid-firing saves. The 409 is consistent whenever I try a branch other
than master. The first time
I use a new branch, it works (sends the file), but all subsequent attempts
fail. Since timing may depend on whether you're using
I'm not sure - nothing is being committed to GitHub outside of TW in my
testing, and I get the fresh file before starting, so I think there might
very well be a timing issue. It's hard to see what's going on, I guess I
should probably pull up the browser dev tools and look at traffic.
Thanks,
Hi Everyone
Apologies, I'm late to this thread. What's the current status? Do we have bugs,
or do we need to improve the docs?
The error HTTP 409 typically means that the file has changed on Git inbetween
the start of the save operation and its conclusion; this can happen very easily
if save o
Mark,
after several trials I was able to save to another branch. Strangely on
GitHub I see this message
Your recently pushed branches: gh-pages
gh-pages is the name of branch I used instead of master.
By the way the saving was successful!
I hope Jeremy could have a look on saving mechanism in
Hi Mark,
I failed to save in other branches!
But I don't see any error message!
The bad thing is when you click the save button even when everything is
correct
Tiddlywiki does not show "Start to saving" like when you save to tiddlyspot!
So seems everything is performed silently and user cannot
Hi Cade
>
For me nothing happened and the save button remains red!
I confirm there is somewhere something wrong!
No success on other branches!
--Mohammad
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop rec
Hi Mohammad,
Have you tried saving to a branch other than master? For me, it works just
once
to push to a different branch. After that there is a 409 error. I notice
your example
is still on the master.
Thanks!
On Monday, August 26, 2019 at 8:13:32 PM UTC-7, Mohammad wrote:
>
> Cade,
> Have a
Same happens on master branch.
On Monday, August 26, 2019 at 12:37:53 PM UTC-7, Mark S. wrote:
>
> This is definitely one for Jeremy.
>
> How about if you delete your file from the master on github, reload your
> local copy, and reset github settings to use master? Then can you at least
> use m
This is definitely one for Jeremy.
How about if you delete your file from the master on github, reload your
local copy, and reset github settings to use master? Then can you at least
use master?
I found that by going through a similar sequence I could get ONE save on
the development branch. It
So I merged everything into master, switched over to master, pulled
everything, opened the file from the filesystem in browser, switched it
over to master, put in user name, edited a tiddler and clicked save:
[image: Capture.PNG]
[image: Capture.PNG]
But - it does say in GitHub "Saved by
Let me try that. I did originally have develop instead of development
because another repo used that convention and I got a 404.
Thanks,
Cade
On Monday, August 26, 2019 at 1:50:10 PM UTC-5, Mark S. wrote:
>
> Does it save if you switch to master?
>
> On mine, I got everything to work, includin
Does it save if you switch to master?
On mine, I got everything to work, including working on development branch.
Then I downloaded and reloaded the file, and after that
I couldn't get it work on "development". I had the same 409 message. Then I
switched back to "master" and it worked OK again.
Sure.
I have a token in the password
This is what GitHub looks like in the Web interface:
[image: Capture.PNG]
On Monday, August 26, 2019 at 12:52:14 PM UTC-5, Mark S. wrote:
>
> It might help if you could show a screen shot of your set up.
>
> I found that you MUST specify
>
> Path to target
It might help if you could show a screen shot of your set up.
I found that you MUST specify
Path to target file (e.g. /wiki/)
>
That is, that field can not be blank. I was using the top level, so put in /
Good luck!
On Monday, August 26, 2019 at 10:40:19 AM UTC-7, Cade Roux wrote:
>
> I have a
16 matches
Mail list logo
