Okular Printer Defaults - Where are they?

I am having trouble when trying to print from Okular.

My problem is that there are several routes to setting the printer defaullts; the HPLIP printer settings, the Leap 15.3 CUPS settings; the Browser settings and Okular which is brought up when I am trying to print a downloaded invoice.

Strange thing is this used not to be a problem but now I get a printer complaint when I try to print that the settings are wrong and do I want to correct. It seems that Okular thinks the printer is set for duplex operation but I have been unable to find any switch in Okular to change this. If I go to the printer options I can change the print to single side and then Okular is happy.

Any clues would be appreciated please.

For me system-config-printer worked properly forwarding the preferences to all applications.

Okular
Print… → printer options → Advanced tab

General setting in YaST Printer
YaST2 - printer -> select printer -> Edit button -> “All option for the current driver” button

…or set them for the given print queue via the CUPS web interface: “localhost:631/printers/”

I am still having trouble with this problem. It is great to have so many ways to make these settings but it seems likely that some are in conflict or not being applied.
I have now found that if I use the Settings>System Settings>Printers and make a change and apply it I am asked for my CUPS local host password but have found that this change is not actually applied.
I had assumed that I had done what was required and only recently discovered the problem when using a networked duplex printer. I have found the settings are wrong, not as I have tried to set and inconsistent.
What is the priority for these settings and which controls what actually works please?

Please ignore my last email. Yast takes precedence and overrides the System Printer settings set on menu Settings.

Yes. YaST configures /etc/cups/printers.conf as do the other CUPS config methods that were suggested to you.

Hi Deano,
Many thanks. It appears that my printer configuration had been damaged. I always set up my printers using Yast and only posted here when one started playing up. It is a networked printer which sits on a shared vlan on a different subnet which might have been the source of the problem.

When I looked into this in detail I found that the printer IP had changed. Very strange as nobody but me has access and I hadn’t touched the configuration for many months and it had been set with a static IP. I have restored the correct configuration and all is well. I have no idea why this happened but all is now good.