Tizra / Tizra-Customer-Tracker

Bug/Enhancement tracking for Tizra publisher project
3 stars 0 forks source link

Can't Change dimensions of PDF #100

Closed ghost closed 12 years ago

ghost commented 12 years ago

http://s64705085-preview.tizrapublisher.com/erisa-outline-book-chapter-3a/4

For some reason I can not adjust the width of the PDF on the ASPPA site using the "Page Content" block in tizra. Can you please look into this and let me know how to fix this?

daviddurand commented 12 years ago

I'm going to need a bit more detail to understand your problem, I'm afraid. There are a couple of tricky things around page dimensions that could be problems for you, and I've put them here in case they are the answer to your questions (and because I think they may make a good wiki page sometime):

ghost commented 12 years ago

What is happening isn't a browser issue, and I know I can impact the size with css, but your system doesn't appear to be doing what it should. So, I created a video: http://screencast.com/t/YmIOB41vEc.

In the video, I jump the width of the PDF up by 200 (px? not labeled in your system) then go back to the staging site and refresh. Nothing changes. I do not have any css controlling the width on the staging server, or I can't find it if I do.

I was able to drop the size down, but it refuses to go over 686px wide.

As a side note, although chrome uses their own plugins, you can force acrobat to be the pdf plugin that is used. I think the same can be done with safari, but I have only tested on a mac.

daviddurand commented 12 years ago

OK, I wrote something complicated, but in that process, I missed writing the first thing that popped into my head on reading your question:

It's at least arguable that CSS is the best way to resize things in modern site designs anyway.

I can imagine a lot of controls that we could add to the page block to adjust this better or at least differently, but the whole sizing process is undergoing radical change at this time (as we move away from PDF plugins), and any changes will be driven by the needs of the new reader.

[as an aside, forcing adobe's plugin solves nothing because most users don't want to install it, and it is unavailable for most browsers on the mac. If it does work for Chrome, that is a recent event of the last few months at the longest.]

I'd also like to remind you that this is a product. We're always interested in hearing suggestions, and I'm often willing to spend a little time talking about pros and cons, but if there is a workaround (or more than one), that's what you have until such time as we (Tizra) may decide to change the way the product works. Unless you are willing to pay for a custom feature, and we agree that the change makes sense. I spend time to try to explain some some of these decisions, but unless really significant new information or arguments surface, they are still decisions, not points for debate.

ghost commented 12 years ago

I'm not trying to debate you on anything. I'm making changes to an editable block in your system, and it does nothing. It seemed like a bug, so I reported it. I'll fix everything with css.