Hi there, today I was prompted to update my Mac OS to 10.14.4. One of these periodical intermediate updates. After everything worked again I fired up Scrivener 3 to prepare some webpages for one of my sites. I imported an existing webpage into the research folder as an example. I then discovered that instead of displaying the webpage, as it normally does, Scrivener displayed the following message on the page: "Failed to load web archive".
Now I checked this in another Scrivener project with a number of web-pages in the research folder, and they all came up with the same message. So updating MacOS to the latest version apparently created a problem with displaying webpages.
Has anyone in this good forum experienced the same problem? If so, did you solve it? Is it a Mac issue, or a new compatibility problem? Any Scrivener people around to shed some light on this.
It would be very nice to know if there is a solution.
Thanks!
Problem with importing websites after update Mac OS Mojave 10.14.4
-
KB
- Site Admin
- Posts: 20920
- Joined: Tue Jun 13, 2006 11:23 pm
- Platform: Mac
- Location: Truro, Cornwall
- Contact:
Unfortunately there is no solution for this at the moment - 10.4.4 introduce a bug whereby web archives won't load using the standard method that Scrivener is using (this is a bug in macOS 10.4.4). I have found a workaround, however, which will be implemented in the next free update of Scrivener 3.
All the best,
Keith
All the best,
Keith
"You can't waltz in here, use my toaster, and start spouting universal truths without qualification."
Thanks for the quick reply Keith. The topic has been discussed in the FB Scrivener user group too. So if people query the forum or search in Facebook they will discover that you are aware of this issue caused by external circumstances and will address it.
Best,
Eelco (Submarin)
Best,
Eelco (Submarin)
KB wrote:Unfortunately there is no solution for this at the moment - 10.4.4 introduce a bug whereby web archives won't load using the standard method that Scrivener is using (this is a bug in macOS 10.4.4). I have found a workaround, however, which will be implemented in the next free update of Scrivener 3.
All the best,
Keith
Thanks Keith—looking forward to this workaround.
While I think of it, it would be great if Scrivener could employ some kind of cookie system to save us having to permanently squash those interminable pop-ups which plague the internet these days.
I know Scrivener shouldn't really have to work as a fully-fledged browser, but it would improve our lives quite a lot if we only have to squash the blighters once!
Thanks for reading.
Stephen
I've just come across this problem myself and am now regretting having updated to Mac OS 10.14.4.
Keith, do you have any estimate for when the next Scrivener update will be? If it's beyond the end of April, I'll give up on web archives for my current project and start importing them as pdfs.
Thanks - and thanks, as ever, for Scrivener itself
Gary
Keith, do you have any estimate for when the next Scrivener update will be? If it's beyond the end of April, I'll give up on web archives for my current project and start importing them as pdfs.
Thanks - and thanks, as ever, for Scrivener itself
Gary
-
lindywarrellli
- Posts: 68
- Joined: Fri Nov 27, 2009 9:50 am
- Location: Australia
Glad to know it was the Apple update at fault and more importantly, delighted to know I don't have to go through all my saved 'links' to try to find them again. Some being quite obscure.
Looking forward to hearing about the workaround...
thanks
Looking forward to hearing about the workaround...
thanks
-
KB
- Site Admin
- Posts: 20920
- Joined: Tue Jun 13, 2006 11:23 pm
- Platform: Mac
- Location: Truro, Cornwall
- Contact:
We should have the fix out for this soon. I was away for two weeks in mid April so was unable to release the fix, and now Ioa is away for a few days and we have some urgent web store issues to address. Once Ioa is back and those issues are in hand, we'll get the update out. Thanks for your patience.
All the best,
Keith
All the best,
Keith
"You can't waltz in here, use my toaster, and start spouting universal truths without qualification."
KB wrote:We should have the fix out for this soon. I was away for two weeks in mid April so was unable to release the fix, and now Ioa is away for a few days and we have some urgent web store issues to address. Once Ioa is back and those issues are in hand, we'll get the update out. Thanks for your patience.
All the best,
Keith
Ok, Keith, thanks a lot, we'll be patient "for a few days" more... Regards, maracuja
KB wrote:We should have the fix out for this soon. I was away for two weeks in mid April so was unable to release the fix, and now Ioa is away for a few days and we have some urgent web store issues to address. Once Ioa is back and those issues are in hand, we'll get the update out. Thanks for your patience.
All the best,
Keith
Hi, Keith! This seems like a pretty major functionality to leave broken for such a long time. Any update as to when your paying customers will once again be able to properly use the product we've purchased from you?
newo32 wrote:Hi, Keith! This seems like a pretty major functionality to leave broken for such a long time. Any update as to when your paying customers will once again be able to properly use the product we've purchased from you?
Have you contacted Apple to ask when they're going to fix the Mac OS bug that is the root cause of the problem?
To load an existing web archive in the interim, choose the Navigate -> Open -> In External Editor command.
Katherine
Scrivener Support Team
kewms wrote:newo32 wrote:Hi, Keith! This seems like a pretty major functionality to leave broken for such a long time. Any update as to when your paying customers will once again be able to properly use the product we've purchased from you?
Have you contacted Apple to ask when they're going to fix the Mac OS bug that is the root cause of the problem?
To load an existing web archive in the interim, choose the Navigate -> Open -> In External Editor command.
Katherine
Have I contacted a third party to figure out why your product, which I paid for, isn't working?
No. No, I have not. I believe what you've just described would be your job. Not mine.
What a rich lesson in customer service. Informing your paying customers that it's on them to figure out why your product isn't working as advertised is the polar opposite of a good look.
I'm excited to learn when I'll be able to use the full functionality of the product I purchased from you once again.