Previewing theme changes locally (Guide Professional and Enterprise)

Have more questions? Submit a request

48 Comments

  • Trapta

    Hi,

    Is anybody else here facing issue with zat theme preview recently? I am running zat theme preview and every time it is throwing parsing error:

    Can anybody tell why it is throwing this error? I have tried using it in two different accounts other than mine too but with no luck.

    Thanks

    1
  • Augusto Silva

    Hey @Trapta,

    I haven't encountered this issue, but maybe you can try to switch the port you are using by providing a --port option. You can also try to switch off live reload by providing the --no-livereload option.

    Let me know if it helps.

    0
  • Eduardo Alberto

    @trapta, were you ever able to fix this? I keep losing connection to the socket on every code change.

    1
  • Trapta

    @Eduardo Alberto, in my case it was the Duck Duck go which was creating an issue. We marked the URL in the whitelist and that does the trick.

    Thanks

    0
  • Eduardo Alberto

    Has anyone had any luck troubleshooting livereload constantly losing connection?

    1
  • Trapta

    @Eduardo Alberto, what error you are getting exactly everytime you are losing connection? Can you post a screenshot of the error you are getting?

    Thanks

    0
  • Eduardo Alberto

    @Trapta Here's a screeshot: 

    I've already tried using incognito, checked if ports were being used, if extensions could be impacting, etc.

    1
  • Trapta

    @Eduardo, what is showing on your terminal?

    0
  • Jen Culp

    @Eduardo & @Trapta - I'm constantly fighting the same issues. The errors Eduardo mentioned show in the browser console but nothing in terminal until stopping. Upon stopping I usually see some version of this:

    I've checked for hung processes, checked for other services using the port, isolated browser extensions, gem updates, etc etc etc. The standard process when trying to troubleshoot similar types of issues. I don't understand why local development for Guide themes has to be so convoluted and herculean. Spinning up a local virtual server and developing against it is nothing new, yet, based on these and other comments across the support site, it seems to have been problematic in this case for quite some time. What is the solution here?

    0
  • Trapta

    @Jen, have you tried updating your zat using zat update?

    0
  • Jen Culp

    @Trapta - yup. Updated zat, updated all gems, yadda yadda yadda...in short, I believe I've followed all suggestions published here and elsewhere within the support site. It's so incredibly frustrating to have localhost lose connection every time  after about 10 seconds. So I build, quickly navigate to the page where my most recent changes are, view those changes, then have to Ctrl+C and do it all over again for each and every change. Overly laborious for what should be standard development.

    0
  • Eduardo Alberto

    @Jen Culp I don't see Zendesk fixing this any time soon. just run zat theme preview --no-livereload and manually refresh the page. It's better than having to restart the server every time.

    0
  • Jen Culp

    Thanks @Eduardo - I guess that's what I'll have to do :shrug:

    0
  • Jessie Schutz

    Hey all!

    Trapta brought this thread to my attention, and I'm chatting with our Developer Support team about it. We'll let you know if we have any insight to share on this.

    0
  • Alexey Vorobyov

    Hello! Thanks for convenient tool.

     

    Recently noticed, that the script.js file is not live to update. So, whenever I make a change in a script.js file

    it is not being synced(uploaded in preview). Everything else works just fine.

    What could be the problem?

    What info should I provide for debugging?

    Using:
    macOS Mojave 10.14.3,
    ruby 2.3.7p456

    0
  • Trapta

    @Alexey Vorobyov, try hard reloading. script file gets cached resulting in showing older version of file instead of updated one with the changes.

    Let me know if this solves your issue.

    Team Diziana

    1
  • Alexey Vorobyov

    Thank you @Trapta. It works today good actually with normal reload.

    Did you change anything or it just universe makes magic? =)

    0
  • Elisabeth Wetchy

    Hello all, great feature! Just mentioning that for me on Windows 10 it works best with --no-livereload as well, without that flag the style seems to disappear once the page is reloaded.

    I'm also noticing that some of the $assets references in my style.css seem to be resolved correctly while others arent - for example something like background-image: url("$assets-foundry_logo-svg"); works fine, but referencing our fonts like so doesn't work:

    @font-face {
    font-family: "Avenir";
    src: url("$assets-avenirnext-regular-08-ttf");
    font-weight: 300;
    font-style: normal; }

    and gives me the following error:

    GET http://localhost:4567/guide/$assets-avenirnext-regular-08-ttf net::ERR_ABORTED 404 (Not Found)

    Is this a known issue?

    0

Please sign in to leave a comment.

Powered by Zendesk