Tyler Tork

On reflection, I’ve decided there really is no excuse for this. Even if you fix it now, leaving it open for so long displays great disregard for security. I can’t recommend this theme.

Did not have problem when using new version of Parallax. However, slow response to support questions gets you a poor rating from me.

I confirm that manually editing the .htaccess file in the way you describe, does work around the problem.

So, congratulations, you have identified the bug and you know what the plugin needs to do to fix it. Now please implement that fix. WordPress does already update .htaccess, so I assume it should be possible for your plugin to insert its own lines in there.

While the bug affects all Bluehost servers in the way I’ve described, it seems to me that all servers would be affected by this in a different way. Now it seems clear that the MIME type value the user enters in your UI is ignored. It seems to me that if the site admin specifies a MIME type for a particular file extension which is different from the server’s default association for that extension, the admin’s intent is to override the default association.

Why are you even having people enter a MIME type if WordPress isn’t going to do anything with it?

Now, I’m not so familiar with the internals, so you might argue that this is a WordPress bug rather than a plugin bug — certainly the three other plugins I tried that allow registration of MIME types seem to have the same issue. But if so, perhaps you could write it up in the WordPress bug tracking system? I don’t know the internal functions involved, to describe it in such a way that they could fix it.

I tried just putting the file on my server, in the root directory of my website, and entering the URL. That worked fine; the server recognized the file extension and added the correct MIME type. So the problem is somewhere in the WordPress code or your plugin. Are you sure you’re using the same version as I am — 4.5.2? Also tried 4.4.3 and had same problem.

Perhaps there’s something about MIME I’m not understanding, but since WordPress doesn’t know how to interpret the contents of these files, it shouldn’t matter what’s in it — only the filename. And it seems to me your test proves there’s nothing wrong with the file, since you used the same file without a problem. So there must be something going on either with the version of WordPress, or elsewhere on my server. But I don’t know what that might be.

I changed my theme to Twenty Sixteen and disabled ALL plugins except yours. I still see the problem. You can see it for yourself at eleanorarnason dot com/temptess — there’s a link to the file on that page. Under Settings > Media > MIME Types I confirmed there is a row with file type mobi and the other three columns filled in application/x-mobipocket-ebook. If you want to take this offline, email me directly at tyler at tylertork.com

Also tried with version 4.5.2 — same problem.

I have not. I value f(x) Editor and my chosen theme, more than I value your plugin. I doubt the theme is a factor, but perhaps you could try the f(x) editor and see whether there’s a way to be compatible with it?

For instance, here’s a screenshot from the iPhone 6s: link using Twenty Sixteen theme. The cover image is too small for me to read even the largest text on it, and there’s a whole column of empty space below the cover image. If you simply made the cover larger the problem would be worse. I think the cover should float left so that text will wrap around it.

Sure.

More:

• How about links for Scribd, Goodreads, Lulu, and BookBaby?
• This one is so stupid I couldn’t believe my eyes at first. There’s no way to control what order the books of a series are listed in on the Series page. Series are meant to be read in a given order. They should be listed in that order. There’s a field on the book page where one can type an ordering number. This field is ignored. I’m not sure whether the order is random or based on something non-obvious.
• The blurb you display in your widget is the entire book description. That’s too long for a sidebar. As I said before, you need a separate blurb field.

I’ll quit now. I could probably come up with more but I’ve seen enough for my purposes, so I don’t need to do more competitive analysis work for you for free.

Also:

• Don’t use h1 for headings within the content of a page. h1 is used for page titles. Your headings shouldn’t be as large as the page title.

Sure.

• By default, book page should have reasonable formatting and the same padding/margins around the title and content area, as the rest of the site.
• Need shortcode to display all books, with sorting options including by date of publication, ascending or descending, or grouped by series, with all books that aren’t in a series listed together at the end.
• Need shortcode to display all that are not in a series, in case they didn’t want those at the end, but instead want to choose which series to list in which order.
• By default, the book table/list should include a blurb. It looks like you would have to add a field for this.
• Put the books in divs displayed as inline-block with a minimum width, so that the books don’t appear in a single column, which looks totally dumb, but take advantage of the available width of the content area to show a grid. Obviously the minimum width will be larger if the blurb is displayed.
• The default ‘alt’ text for the book cover, if the user hasn’t entered alt text, should be ‘Book cover: ‘ followed by the title.

I understand what you are saying, and that would be fine if it were just me, but my customers will not maintain PHP code, they need it to work reasonably out of the box, and I don’t know why it can’t.

I am ready for the update anytime!!! In fsct if you’re not ready to release it, could I have a beta copy? I’m writing a book and would like to mention your plugin prominently.