Jump to content

Dirty Butter

Moderator
  • Posts

    6,634
  • Joined

  • Last visited

  • Days Won

    139

Posts posted by Dirty Butter

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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?)

  6. 24 minutes ago, havenswift-hosting said:

    I cannot see how order details could be affected when clearing cache (but stranger things have happened I suppose) but as every single action done by an admin currently clears cache (each and every single time - see https://github.com/cubecart/v6/issues/1536) I think you would have no correct orders if that was the case !

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

×
×
  • Create New...