Bookshelf | Reports | Community | KDP Select

Home » Amazon KDP Support » Ask the Community » General Questions

Thread: Here's a New One


Reply to this Thread Reply to this Thread Search Forum Search Forum Back to Thread List Back to Thread List

Permlink Replies: 13 - Pages: 1 - Last Post: Jan 27, 2018 8:41 PM Last Post By: Patrick A. Smith
maineauthor

Posts: 693
Registered: 07/14/12
Here's a New One
Posted: Jan 27, 2018 4:42 AM
Click to report abuse...   Click to reply to this thread Reply
Last weekend, I did some tweaking of book covers, primarily font changes. Today, after a week of looking at one of them, I decided that a white title font would be more readable than the black I'd originally used, so I made the change, loaded the cover, and hit the button to continue. And got an error message saying there was a problem with my manuscript. It couldn't be published as-is. I was directed to reformat and reload the manuscript. The same manuscript that's been up there, unchanged and untouched, since 2014. The same one I've changed covers on several times, including a week ago, and never received an error message. The same one I wasn't trying to republish.

Last weekend, it was Createspace. I had reformatted a manuscript and created a new cover. I uploaded everything with no problem, then couldn't get the online previewer to open. I tried everything: three different browsers, reloading the manuscript as both a doc and a pdf. Nothing worked. I turned to my best friend Google, where I learned that my flash player might be out of date. Although I knew it wasn't (the computer is a year old), I tried updating it anyway. Twice. Didn't make a bit of difference. I spent literally hours cussing at my computer in frustration while my poor husband tried to ignore me. Finally, after about four hours of this ridiculous nonsense (there are other words I could use to describe it, but I'd be banned from the forums forever), I left the new computer, went to the dining room where my ancient laptop was sitting, logged into Createspace and had no problem whatsoever opening the online previewer. I still have no idea why I couldn't open the previewer with the new computer, but now I live in fear that one of these days, the laptop will go on to its eternal reward and I'll never again be able to preview a paperback online.

I'm not sure I'm up to what may happen today if I try to take this any further. Far easier to just leave the black font on the cover and leave well enough alone. Or let sleeping dogs lie. Or any one of a dozen other cliches I could come up with. In the greater scheme of things, black versus white isn't that big a deal. Right?

I think I'm getting too old for this stuff.

Edited by: maineauthor on Jan 27, 2018 5:14 AM
Cynthia E. Hurst

Posts: 1,898
Registered: 02/25/13
Re: Here's a New One
Posted: Jan 27, 2018 4:52 AM   in response to: maineauthor in response to: maineauthor
Click to report abuse...   Click to reply to this thread Reply
I had a similar thing happen to me last autumn, where for the first time in five years, CreateSpace wouldn't display the online previewer and insisted I needed a new version of Flash, which then wouldn't download. I ended up crossing my fingers, going ahead and publishing, and then immediately buying a copy to check.
Then in December, I uploaded another book on the same old laptop, and everything worked fine. So I have no solution, but don't give up -- sometimes the problems seem to correct themselves.
maineauthor

Posts: 693
Registered: 07/14/12
Re: Here's a New One
Posted: Jan 27, 2018 5:13 AM   in response to: Cynthia E. Hurst in response to: Cynthia E. Hurst
Click to report abuse...   Click to reply to this thread Reply
Yep, I have noticed that things sometimes just get better on their own. Ah, technology!
Joseph M Erhardt

Posts: 4,894
Registered: 12/21/15
Re: Here's a New One
Posted: Jan 27, 2018 6:58 AM   in response to: maineauthor in response to: maineauthor
Click to report abuse...   Click to reply to this thread Reply
Occasionally, changes in standards will get you, too. I tried to update a title and my epub upload failed--not because of any changes that I had made, but because the standards of acceptability had changed. A fellow at KDP support pointed me to the epub validator, which nailed it down to file and line of code, so I was able to figure out that my ToC page hook (bookmark) had to use

id="toc"

instead of

name="toc"

One thing I will say about IBM, from years of working with their stuff, both on mainframes and microcomputers: Upgrades that they did RARELY broke existing code. I mean hen's-teeth rarely. In a way, it's too bad that they didn't lead the microcomputer revolution instead of the amateurs at Microsoft.
Notjohn

Posts: 24,153
Registered: 02/27/13
Re: Here's a New One
Posted: Jan 27, 2018 8:06 AM   in response to: Joseph M Erhardt in response to: Joseph M Erhardt
Click to report abuse...   Click to reply to this thread Reply
Yes, name= has been "deprecated" for years, though enforced only on epub. Apple would have rejected the book all along, because it wouldn't have validated through Epubcheck. Interesting that Amazon is finally catching up with epub standards, given that it has accepted epubs since 2011.

I had the identical experience with my first epub. There was absolutely nothing wrong with it from my point of view, but it got scores of errors on epubcheck. It was the wonderful Hitch who pointed out that "name" should be "id". I have been her admirer ever since.

(Don't trust KDP to publish a print edition. Don't trust CreateSpace to publish an ebook. Each does one thing well and the other thing poorly.)

Good luck! -- NJ

Notjohn's Guide to E-Book & Print Formatting (2018 edition)

The blog: https://notjohnkdp.blogspot.com
Joseph M Erhardt

Posts: 4,894
Registered: 12/21/15
Re: Here's a New One
Posted: Jan 27, 2018 10:08 AM   in response to: Notjohn in response to: Notjohn
Click to report abuse...   Click to reply to this thread Reply
Notjohn wrote:
Yes, name= has been "deprecated" for years, though enforced only on epub. Apple would have rejected the book all along, because it wouldn't have validated through Epubcheck. Interesting that Amazon is finally catching up with epub standards, given that it has accepted epubs since 2011.

I had the identical experience with my first epub. There was absolutely nothing wrong with it from my point of view, but it got scores of errors on epubcheck. It was the wonderful Hitch who pointed out that "name" should be "id". I have been her admirer ever since.

(Don't trust KDP to publish a print edition. Don't trust CreateSpace to publish an ebook. Each does one thing well and the other thing poorly.)

Good luck! -- NJ

Notjohn's Guide to E-Book & Print Formatting (2018 edition)

The blog: https://notjohnkdp.blogspot.com


And one other thing: My original book had a couple of illustrations that were not within paragraphs. That raised a flag, too. Put them into paras, and all was well.
Patrick A. Smith

Posts: 1,924
Registered: 04/27/13
Re: Here's a New One
Posted: Jan 27, 2018 2:10 PM   in response to: Joseph M Erhardt in response to: Joseph M Erhardt
Click to report abuse...   Click to reply to this thread Reply
Joseph M Erhardt wrote:
Notjohn wrote:
Yes, name= has been "deprecated" for years, though enforced only on epub. Apple would have rejected the book all along, because it wouldn't have validated through Epubcheck. Interesting that Amazon is finally catching up with epub standards, given that it has accepted epubs since 2011.

I had the identical experience with my first epub. There was absolutely nothing wrong with it from my point of view, but it got scores of errors on epubcheck. It was the wonderful Hitch who pointed out that "name" should be "id". I have been her admirer ever since.

(Don't trust KDP to publish a print edition. Don't trust CreateSpace to publish an ebook. Each does one thing well and the other thing poorly.)

Good luck! -- NJ

Notjohn's Guide to E-Book & Print Formatting (2018 edition)

The blog: https://notjohnkdp.blogspot.com

And one other thing: My original book had a couple of illustrations that were not within paragraphs. That raised a flag, too. Put them into paras, and all was well.


No doubt your newer pc has win 10. As for epubs, I'm glad I don't have to mess with them. When I had bks at apple sw made them.
maineauthor

Posts: 693
Registered: 07/14/12
Re: Here's a New One
Posted: Jan 27, 2018 3:16 PM   in response to: maineauthor in response to: maineauthor
Click to report abuse...   Click to reply to this thread Reply
UPDATE: I had a lovely day away from the computer, went to the beach with my camera instead of fighting with the evil KDP system, and came back an hour ago to see what I could figure out. There was some formatting I wanted to update in the book anyway, so I found the original manuscript on my old laptop, transferred it to the new computer, went through it and made the changes I wanted, and tried again. Again, it gave me the same error message. And I remembered that I'd read on here quite some time ago that KDP doesn't always play well with docx files. So I saved it as a doc instead, loaded the revised manuscript, and had no trouble whatsoever. It's now in publishing mode.

I can't imagine why the KDP system would have done this when all I was trying to do was upload a new cover file, but I managed to work it out, so the world is a kinder and prettier place tonight.
maineauthor

Posts: 693
Registered: 07/14/12
Re: Here's a New One
Posted: Jan 27, 2018 3:18 PM   in response to: Patrick A. Smith in response to: Patrick A. Smith
Click to report abuse...   Click to reply to this thread Reply
Patrick A. Smith wrote:

No doubt your newer pc has win 10. As for epubs, I'm glad I don't have to mess with them. When I had bks at apple sw made them.


All my computers have Windows 10, otherwise known as The Spawn of Satan. But it seems the problem was that it was a docx file. Not sure why KDP would flag it when it's been up since 2014 and all I was trying to do was upload a new cover, but I found the original manuscript file, changed to a doc file, and it worked just fine. As my former boss used to say, wicked weird.
Joseph M Erhardt

Posts: 4,894
Registered: 12/21/15
Re: Here's a New One
Posted: Jan 27, 2018 5:44 PM   in response to: Patrick A. Smith in response to: Patrick A. Smith
Click to report abuse...   Click to reply to this thread Reply
Patrick A. Smith wrote:

No doubt your newer pc has win 10. As for epubs, I'm glad I don't have to mess with them. When I had bks at apple sw made them.

No, I'm running Win7. The change in epub standards has nothing to do with Windows. (In fact, I had to fight to keep Microsoft from updating me to Win10, as I'm maintaining legacy software for a couple of clients, and I had ZERO CONFIDENCE that the legacy compiler would run under Win10--I barely got it fully installed and running under Win7.)
Dave Casey

Posts: 424
Registered: 03/03/16
Re: Here's a New One
Posted: Jan 27, 2018 7:33 PM   in response to: maineauthor in response to: maineauthor
Click to report abuse...   Click to reply to this thread Reply
I've had the same problem with CreateSpace and trying to upload a manuscript while using Google Chrome. I must have updated the Flash player software ten times and CS still can't pull their collective heads out of their butts and recognize it. So, I end up switching over to Firefox and the whole process goes as smooth as silk.
Danny W. Patter...

Posts: 5
Registered: 05/26/14
Re: Here's a New One
Posted: Jan 27, 2018 7:34 PM   in response to: maineauthor in response to: maineauthor
Click to report abuse...   Click to reply to this thread Reply
As far as opening the online previewer on createspace. Go to createspace and click the Secure tab in the upper left hand corner (it has a picture of a lock). Go to the bottom of the screen that pops up and click site settings. Make Flash setting Allow (default is ask) and that Popups are also Allow (default is ask). This worked for me on a new Windows 10 computer but one never knows. Good luck.
Danny W. Patter...

Posts: 5
Registered: 05/26/14
Re: Here's a New One
Posted: Jan 27, 2018 7:36 PM   in response to: maineauthor in response to: maineauthor
Click to report abuse...   Click to reply to this thread Reply
Sorry, I should have added that I am using Chrome, I don't know if it will work on Edge.
Patrick A. Smith

Posts: 1,924
Registered: 04/27/13
Re: Here's a New One
Posted: Jan 27, 2018 8:41 PM   in response to: maineauthor in response to: maineauthor
Click to report abuse...   Click to reply to this thread Reply
maineauthor wrote:
Patrick A. Smith wrote:

No doubt your newer pc has win 10. As for epubs, I'm glad I don't have to mess with them. When I had bks at apple sw made them.

All my computers have Windows 10, otherwise known as The Spawn of Satan. But it seems the problem was that it was a docx file. Not sure why KDP would flag it when it's been up since 2014 and all I was trying to do was upload a new cover, but I found the original manuscript file, changed to a doc file, and it worked just fine. As my former boss used to say, wicked weird.


That doesn't surprise me at all. .docx contains track changes and other unneeded stuff. I write in .doc and then after its edited I save it as html, which takes a bit more from it and send that, although a .doc works as well.

My wife and I got a good laugh at your nickname for win 10! I have written several books on my win 10 laptop but now I'm back to using win 8.1 again, mainly because that desktop pc is where my Photoshop and word 2016 is. And my large logitech keyboard. I'm glad you finally got your project done!
Legend
Helpful Answer
Correct Answer

Point your RSS reader here for a feed of the latest messages in all forums