Print-Layout has no structure after Updating to 2.0

Thank you for starting this issue. We are going to make it sticky for awhile, as it’s sure to come up more than a few times.

2.0 is a complete rewrite that not longer requires a separate print window to be created. While the benefits are many, the single drawback is that all of the ‘custom print-page css’ that was injected into the new ‘print’ document, works a bit differently. In short: the new print system uses standard @media print CSS.

Unfortunately, many themes use their own ‘print-only’ css and this often produces less than desirable results — causing our plugin to be installed in the first place.

Moving forward you have two options:
1. stick with version 1.7.14 for current sites that do not migrate seamlessly to version 2.0.
2. upgrade to version 2.0 and modify the @media print CSS so that it meets your needs.

We can not help everyone with their specific needs using the free version, but we will use this thread to address the main steps in migrating to version 2.0.

Step One would be to use your browsers inspector and toggle on the print-view to see what CSS the theme has included. Here is how do this in:
Chrome
Firefox
Safari

I have the same problem.
I made the rollback too.

When I put the code, in the additional CSS of the Astra Child theme it doesn’t work… All my sites are made in Astra… Astra is a very common and simple theme.

In the previous version it works perfectly, but in 2.0 the print is wrongly positioned.

My code:

.printomatic {
    margin: 0 auto;
}

@media print {
#Header, #Footer { display: none !important; }
@page {
margin-top: 1cm;
margin-right: 0cm;
margin-left: 0cm;
}
img {
width: 95%;
height: 95%;
}
}

• This reply was modified 3 years, 5 months ago by Steven Stern (sterndata).

Basically, without this code, the plugin prints only a small image of about 100×200 px in the upper left corner of the page. With the code (and in the past version), it prints the entire page as I need.
Please help me @twinpictures

@gfsuarez this is a sticky post regarding the migration to 2.0
For help on your specific issue, please start your own thread and be sure to include a link to the page in question.

Ok, but this only happens in 2.0. It started the minute I made the migration. In the previous version does not happen. It’s the same problem as the creator of the post @jpkarmatech.

@gfsuarez yes, this is addressed in the sticky thread above. If you want to use version 2.0 which a complete rewrite then you will need to:

start your own thread and be sure to include a link to the page in question

.
You also have the option of staying with version 1.7.14.