Skip navigation
Currently Being Moderated

Did cf9 fix the issue with text getting cut off in cfdocument?

Apr 7, 2010 1:00 PM

See: http://kb2.adobe.com/cps/000/ea53f6ec.html

 

I am displaying a query with cfdocument type="pdf" and it continues to cut text off at the end of the page.

 

I assumed cf9 would have corrected this...

 
Replies
  • Currently Being Moderated
    Apr 8, 2010 10:51 AM   in reply to idesdema

    Since it was already fixed in MX 7.x, I would imagine it fixed in CF 9.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 9, 2010 1:26 AM   in reply to idesdema

    The example code you cite is not much chop as far as a reproduction case goes, because the issue you're seeing is contingent on the contents of the include files, not the <cfdocument> tag itself.

     

    Can you create a simple, working, stand-alone example that demonstrates what you're seeing?

     

    --
    Adam

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 9, 2010 9:03 AM   in reply to idesdema

    Well... no, not really.

     

    I don't doubt you're seeing something you don't want to see, which is all the screen cap demonstrates.

     

    However there's no way of telling why you're seeing what you're seeing without you providing code to replicate it.  Plus if you provide code to replicate it requires you to actually write the code, which will quite possibly help you isolate what the problem is.

     

    I created a couple of include files with some lorem ipsum text in it and ran the code you posted.  It worked fine.  So... it's not intrinsically bung.  And also an attempt to replicate it with bare bones code did not replicate it, so the repro case needs to be a bit more thorough: it's something about what you're rendering in those include files.  You need to isolate what.

     

    As it stands there's no reason to think it's not something you're doing wrong (which is what it usually is when someone has problems, I'm sure you'd agree... I'm not being obtuse or rude when I say that).  I'd at least put equal money on that as I would on the bug still existing.

     

    --

    Adam

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 10, 2010 5:57 AM   in reply to idesdema

    I literally just generated two sets of 15 paragraphs of lorem ipsum text and put them in template1.cfm and template2.cfm.

     

    http://www.lipsum.com/

     

    --

    Adam

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 13, 2010 12:56 AM   in reply to idesdema

    I'm not sure that me showing it to you working (which it does) really helps your cause.  I don't need to demonstrate to you that it works: you need to demonstrate to us (in a replicable fashion) that it doesn't work, then we can go about working out what you're doing to cause it to "not work".  Did my test not work for you when you tried it?  Or is it - as I suspect - you've not actually tried it?

     

    Have you done what I have suggested and tried to come up with a good reproduction case for this?  That would be the best usage of people's time here.

     

    But... here's the screen cap of it working fine on my machine:

     

    pdf_page_break_ok.png

     

    Now. Can we (read: "you" ;-) please focus on why it's not working for you, rather than why it is working for me.

     

    Come back to us with a good repro case...

     

    --

    Adam

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 13, 2010 7:14 AM   in reply to idesdema

    This is on a governement site so I can't have you see what it outputs (meaning give you a link) other than showing the screenshot.

     

     

    That's fine.  I don't want to see your actual code based on live data: that will be full of irrelevant stuff which will just muddy the situation.

     

    Writing a repro case will actually involve some leg work on your part.  We've demonstrated it's not an intrinsic bug: the plain text version works fine.  So this means you need to start looking at what else is in those includes that might be impacting it.  I think you're on the right track thinking about the styles, and that's as good a place to start as any.

     

    So make another set of of files, stick the styles and some place holder content in it, and see if that breaks it.  If it doesn't... stick some other element in and see if that breaks it.  Continue until you can break it.  Then factor out stuff that probably doesn't seem to break it, and keep factoring stuff out so you have the bare minimum requirement to demonstrate the problem.

     

    You should be left with three small files:

    1) the file with the <cfdocument> call;

    2) the first include;

    3) the second include.

     

    That's your repro case.  And, indeed, it's a general strategy for trying to solve a problem: identifying what the problem is.  By the time you do this, you will probably have worked out what the problem is by yourself, but if not, at least the rest of us have something to work with.

     

    Its hard to post here sometimes because it seems like I always run into some snide remark or attitude issue.

     

    Well I don't know if there's any snide remarks going on.  All I'm doing is asking you to throw us a bone.  You're asking for help - fine, that's what we're here for - but you're not actually acting on the advice given.  But you do seem to expect a solution withough working towards it.  How is that supposed to work?

     

    --

    Adam

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 13, 2010 8:09 AM   in reply to idesdema

    Cool, we're getting somewhere.

     

    Can you clarify something... you say include_1449_p2_lines.cfm is the "lorem ipsum" stuff... what's in include_1449_p1_lines.cfm then?

     

    Is that page break being displayed there in your screen cap the one you're specifically putting in with <cfdocumentitem type = "pagebreak"/>, or is it just a soft break due to the length of the text?

     

    --

    Adam

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 26, 2011 11:12 PM   in reply to Adam Cameron.

    Why is this thread dead? As far as I can tell, this is still an open issue.

     

    Apparently cfdocument can't handle page breaks in the middle of tables. I'm having this same problem and I haven't found a work around, but I have found plenty of people who have had this problem.

     

    Please vote for this bug:

     

    http://cfbugs.adobe.com/cfbugreport/flexbugui/cfbugtracker/main.html#b ugId=82761

     

    Or please let me know if there's a workaround.

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points