Width of invoice entry stretched out/displaying improperly

[johnanastasio17]

Not sure, what happened. Have made no changes to SI or it's underpinnings. When entering a new invoice, screen now appears like this:

Other pages and reports all seem to render properly.

[twobob]

Does pressing F12 and observing the console output show any obvious errors? Always good for a dev to know.

[johnanastasio17]

Nothing in the console under any tabs. (Inspector, Console, Debugger, etc)

I'm not a coder by any means, but I notice there is a lot of java code. I'm running Java Version 8 Update 161 if that helps.

Same behavior using Pale Moon, Chrome, Firefox. Tried it on IE and it completely crashes. I'm on a Win 10 64bit machine if that matters,

[twobob]

Well. opened the console and had a bit of a look. Seems like the total width is constrained by the length of the content in the boxes.

Has someone added an item accidentally that is 2000 character long or something? Either way you could constrain the box length actively via CSS at an absolute pinch. I have no idea what is wrong at your end but one could control that value by shoving a record for "#products0" in the stylesheet with a value of "width:500px !important" (if you find you really need the !important, try it without first)

Hope it helps at least be able to use your system while you figure it out. Justin said 8 years ago "the folder for the default template ./templates/invoices/default contains all the css etc.." main.css appears to be the file that the factory defaults go in. So check out that folder and shove it somewhere sensible. In case you don't know CSS cascades. So things that come after will replace things that came before in the same stylesheet and things that are "closer" (like for example attached directly to the HTML TAG) will win out over things that are "far away" like the stylesheet that got included first (see rule 1) or any rule that is NOT directly attached to the tag.

I would shove it at the bottom of the factory CSS to begin testing and then find somewhere more sensible once I was sure I fixed the problem. Enjoy your day

twobob commented 6 years ago

Also I note that you have n¹⁰ items in that list. is that supposed to be like that? No one else knows what you expect to see. So clearly stating your expectations really helps.

"It's broken!" is not specific enough :)

"IT'S BROKEN and I expected to see 2 items in my invoice template - HERE IS A PICTURE OF A WORKING ONE" is way more helpful.

johnanastasio17 commented 6 years ago

Has someone added an item accidentally that is 2000 character long or something? We have a winner! We did a "total" type invoice instead of an "itemized" invoice. This created an item that was a mile long which caused the behavior pictured above in the first post. Thank you for giving us an idea on where to look, the problem is solved.

fearless359 commented 6 years ago

I just uploaded changes that I believe will address this. The notes on the TOTAL_INVOICE get stored in the si_products table and the ID from that entry wasn't associating correctly with the invoice.

twobob commented 6 years ago

Score one for the crystal ball

• © Githubissues.
• Githubissues is a development platform for aggregating issues.

[twobob]

Also I note that you have n¹⁰ items in that list. is that supposed to be like that? No one else knows what you expect to see. So clearly stating your expectations really helps.

"It's broken!" is not specific enough :)

"IT'S BROKEN and I expected to see 2 items in my invoice template - HERE IS A PICTURE OF A WORKING ONE" is way more helpful.

[johnanastasio17]

Has someone added an item accidentally that is 2000 character long or something? We have a winner! We did a "total" type invoice instead of an "itemized" invoice. This created an item that was a mile long which caused the behavior pictured above in the first post. Thank you for giving us an idea on where to look, the problem is solved.

[fearless359]

I just uploaded changes that I believe will address this. The notes on the TOTAL_INVOICE get stored in the si_products table and the ID from that entry wasn't associating correctly with the invoice.

[twobob]

Score one for the crystal ball