Dirty Butter

Well mine is so far from stock it's almost unrecognizable. I print the whole page and use Dazzle for shipping labels. I didn't even have the page break code in there. It was a matter of getting the div's paired up correctly - my first few attempts had the break in the wrong place, thanks to a stray div. Good luck!! I'll mark this as Resolved when it does what you want.

My orders.print.php, like everything else about my install, if FAR from stock. But I think I see the issue. Copy the print.css section about page-break and add it to the #printLabel section. The one at the bottom is to break off customer notes to a second page. https://github.com/cubecart/v6/issues/1605

WOW! Talk about unintended consequences! It sure sounds like a div issue of some kind. Maybe instead of <p></p> try div? Can you be more specific about where you put the page break code?

I'm in the US, but I can make good use of this as well for our UK customers! I just tried it, and it works - but it puts a comma in front of the ZIP on the delivery address for the packing slip. Creating orders for a UK customer are extremely rare for me, but this comma might need to be edited out of your packing slip for those who need to do this a lot.

I wish I understood all this well enough to be of help, but I certainly do not. Maybe it would be best to make a new thread about what you need, since this thread has gotten so long.

Great!

OK - thanks for answering. That explains why the upgrade did not work smoothly for you. There was a bug that was introduced in the last few versions concerning upgrading within Admin. That's why the Announcement of 6.1.6/6.1.7 upgrade said to do it manually, rather than from within Admin. That bug has been fixed in 6.1.7, so upgrading via Maintenance should work just fine from now on.

I quit trying to do that because it printed just the way you are describing. But I don't remember ever seeing anyone bring this up on the forum or on GitHub. This looks like the way to fix it, but it's beyond my skills to know how to implement it on orders.print.php. https://www.w3.org/TR/REC-CSS2/page.html

I've added this to GitHub. https://github.com/cubecart/v6/issues/1604

Maybe this post from Bsmither will help:

That plugin is one of SemperFiWebServices's. He has recently upgraded several of my own plugins from him to be compatible with 6.1.7. And I'm sure he is working to get the rest to work with all the code changes in 6.1.7. CSRF is just one of several sea change coding changes in 6.1.7. Daren was AFK for an Easter vacation, according to his website, but may be able to help you get this upgraded more quickly if you contact him via Support on his website.

I'm wondering why your upgrade did not work properly. Could you tell exactly how you did the upgrade and what you upgraded from?

What CC version are you using? What version of the Minimaliser skin? Have you been able to contact indrum.com? May I suggest that you try the stock Foundation skin and see if you still have the same issues? You will need to clear all cache except images from admin>Maintenance. Also clear your browser cache - Ctrl/F5 usually works. And you will have to do all that clearing again to go back to your own skin.

Thanks for that, Christopher. Good to hear!! Hoping for feedback about automatically changing to Processing, so I can change this thread back to Resolved.

Has anyone had a successful purchase via PayPal or some other gateway that automatically changed to Processing within CC?

The error log will be at the root of your store. That's the level that has the includes folder in it. View it either by FTP or cPanel FileManager.

Glad to see this progress with gateways, for sure. But I have a MailChimp API plugin that communicates both ways with the store that apparently isn't able to communicate back to the store at this time on 6.1.7, thanks to CSRF. So there's still more to be done here. I understand CC is trying to shut down unauthorized server access to our stores, and that's a good thing. We just need a way to tell the code what is allowed through. Windows does the same thing with allowed exceptions in Defender. (I think it's Defender that does that - maybe something else?)

Well, I tried to do that, but didn't find anything useful. As long as it's no more than an old link - I'm not going to fret over it. Thanks for the help!

Thanks for the explanation - but it does make it sound like this NULL product issue probably is not cache related.

HA! Maybe that's why most of our sales come when I'm not on the computer!!!

I saw this in our Customers Online information. It resolves to the homepage, but what in the world is it and where is it coming from? This store is basically on 6.1.5.

Are you saying that any and all changes made in 6.1.7 admin currently clears the cache in the storefront?????

Interesting idea - is there some way you can test your theory?

I would suggest you message @Noodleman , if you don't mind paying for his time. He is a developer. This sounds like something he may have already done for someone else.

Sorry I didn't find this sooner: https://www.semperfiwebservices.com/easter-2017.html