I was able to reproduce this. I think we have to refresh the wms source when entering the print view, otherwise old cached tiles may be used and mess up the print.

Is there any quick fix for WMS source refresh.
As in looping through visible layers and implementing

    if (layer.get('type') === 'WMS') {
      const layerSource = layer.get('source');
      layerSource.refresh();
}

Please test #1741
Perhaps a check if a layer is visible makes sense before doing unnecessary refreshing

It would be nice to get the full picture here before we rush into masquerading the error with a refresh. Although the solution may be just a refresh but I think it may not have to be performed as a general rule.

Is this something that has started to happen recently?

Does the map has the same coordinate system as the layers?

Are the WMSlayers cached on geoserver?

What are the values of the print settings:

• supressResolutionsRecalculation
• suppressNewDPIMethod
• scales

Are the WMS-layers tiled or image?

Is the constrainResolution setting true?

I just think it is a bit strange that this hasn't been observed before unless something has changed or you have a different setup than most. I'm thinking that this could be related to the grid recalculation when the DPI changes, in which case it should probably be solved when the grid is recalculated instead.

It would be nice to get the full picture here before we rush into masquerading the error with a refresh. Although the solution may be just a refresh but I think it may not have to be performed as a general rule.

Is this something that has started to happen recently?

Does the map has the same coordinate system as the layers?

Are the WMSlayers cached on geoserver?

What are the values of the print settings:

• supressResolutionsRecalculation
• suppressNewDPIMethod
• scales

Are the WMS-layers tiled or image?

Is the constrainResolution setting true?

I just think it is a bit strange that this hasn't been observed before unless something has changed or you have a different setup than most. I'm thinking that this could be related to the grid recalculation when the DPI changes, in which case it should probably be solved when the grid is recalculated instead.

The print settings are default

    {
      "name": "print"
    },

WMS tiles are default settings from Geoserver

I suppose the tiles are still in an EPSG:3010 gridset? If the map is set to 3010 I mean.

Am unable to repro the issue.
I have tried: a print definition like your example (empty), a wms layer that isn't the background layer cached in 3010, a wfs layer from the same geoserver, turn on both layers, print, exit print, no issue. The map is set to constrainResolution:true (because cached image layers)

@Lundqan Is this still an issue? When I'm testing with master it seems to work, perhaps something is changed in latest OL release.

@Lundqan, @jokd and everyone else: Is this still an issue? If not, I think we can close this issue and the related PRs rather soon.

@Lundqan, @jokd and everyone else: Is this still an issue? If not, I think we can close this issue and the related PRs rather soon.

Unfortunately it is. In certain situations it just messes up the tiling:

@jokd Good to know!

And don't think I didn't notice the lil' chirpers!

@jokd Good to know!

And don't think I didn't notice the lil' chirpers!

Knew you would love it. Heard complaints about the lack of sound effects.

Raising the bar. Next step - inspirational background music.