Same with me. Has been ever since this service was added.
I’ve copied settings across from Transmit so many times now, I just stick with Transmit, it’s faster for me.
We have been having similar problems with Transmit 5 for some time now. (since macOS Sonoma). Looks like something is going wrong with the macOS keychain, access is denied or fails. But it is not really reproducible. Deleting the entries in the keychain has helped to some extent, but this is of course not a solution across the board. Perhaps this will help with troubleshooting…
This is awesome news @Norm and really appreciate the focus on enhancing the publishing capabilities. that you’re able to add in the capability to authenticate with a certificate.
Wow. All this time I’ve overlooked the FTP feature in Blocs! After reading this thread I checked the Knowledgebase article, and sure enough, it’s there!
Haven’t used in-app FTP since my SoftPress Freeway days! Even back then there were times when it couldn’t make the connection. But even Transmit 5.10.4 throws a connectivity fit now and then. I’ve used Transmit for years though and it works well.
It’s funny because when I first started using Blocs 2, I mourned the loss of in-app FTP like I had in Freeway. Might be nice to go back to it, when the bugs are hammered out, of course.
I guess the real question I have at this point is how Blocs handles files on the server that were either manually added (using something like Transmit), or added using a different Blocs document. For example, if I setup the Publish Site panel to link to my server, uploading document web pages and content to a particular folder on the server, what happens if I later use Transmit to add an unrelated folder in that directory? The next time I use Blocs FTP to upload there, will that folder be left alone (as it should be), or will Blocs try to overwrite it?
This is an important question because I have separate Blocs documents for English web pages and for Japanese web pages. All my English pages are put in a “/en” directory within the main directory. So naturally, if I use Blocs to upload my Japanese document, I wouldn’t want it to delete my /en directory. Freeway never had a problem with that because it would ignore files and directories that it never uploaded. Meaning, Freeway knew what it had control of (for a given document) and ignored everything else. But what of Blocs’ FTP function?
Anyway, I appreciate this thread because it showed me something new today!