New Landing How can we help? Atelier woocommerce major upgrade – atelier license for test-surroundings?

Viewing 6 posts - 1 through 6 (of 6 total)
  • Posted in: Atelier
  • #291270
    D-atix
    Member
    Post count: 2

    Dear Developers,

    First question:
    the WooCommerce Database has to be upgraded after a major upgrade of Woocommerce.
    The Woocommerce Developers urgently advise to test this upgrade in a test surrounding and not on the live system.
    Can I use my license for a second (test) installation of my website for such purposes?
    If yes, how?

    Second question: I developed a child theme but noticed that MOST changes in style.css never show in the site’s frontend (some, yes).
    I turned off all the cache settings in theme options and in swift framework, I turned off my browsers’ cache management – nothing changed.
    I can place my css only in the “Custom CSS and JS” theme option, then my changes show in the frontend.
    But I have read in the forum that these settings sometimes disappear.
    I’m used to working with child themes, and a child theme would please me better.
    How can the caching / loading of minimized stylesheets etc. be turned off so that changes in the child theme show immediately on the frontend page?

    Thanks a lot in advance, have nice summer days…!
    Dorothee

    #291281
    Kyle – SUPPORT
    Moderator
    Post count: 35880

    Hi

    1) Yes you can use the license for a test environment, as long as only one site goes live

    2) If you are changing fonts/colours/font sizes (basically anything that you set in the theme options) you will need to add !important too, or make more specific, as the option styles are outputted last, so even though you have a css rule in your child theme, the option styles are loaded after it so will override it

    – Kyle

    #291325
    D-atix
    Member
    Post count: 2

    Thank you dear Kyle for the immediate answer.

    Question One: Just to make sure I understood it right: So I can clone the whole Website and put it in any test-environment, but only on a webserver that is not reachable online?

    Question Two: Of course I added !important or tried being more specific in my css selectors, but all this did not help a bit. Therefore my question: is there another cashing mechanism hidden somewhere?
    Theme Options-Performance, Swift Framework-Performance I already switched off, Browser Caching, too.

    Thanks again
    Dorothee

    #291597
    Swift Ideas – Ed
    Keymaster
    Post count: 15264

    Hi @D-atix

    It can be reachable online, just not a live actual-use site. A staging site like you have described, is completely fine.

    Can you please check this css file directly in your browser, to see if you can see the css there? There is nothing in the theme that would cache your child theme stylesheet.

    – Ed

    #294049
    D-atix
    Member
    Post count: 2

    … firefox inspector shows me an older version of my stylesheet – so it must be cashed somewhere.

    i can avoid cashing problems if i use custom css in the theme options but would prefer very much using my child theme style sheet.

    dorothee

    #294156
    David Martin – Support
    Moderator
    Post count: 20834

    Have you cleared the FF browser cache?

    Have you added the CSS to your child theme, I’ll need to take a closer look at this to confirm it’s loading correctly.

    Please add a URL/FTP details to your test site if the issue persists.

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in and have valid license to reply to this topic.

License required for one of the following items
Login and Registration Log in · Register