Bug in saving files in developer mode that are in a directory

  1. last year

    Via developer mode you can change less, css, twig, etc files. Save works ONLY if the file is in the root of the package. If in a directory, you will get an error that it is not possible to save changes.

    This limits the functionality of the developer mode :(
    Workaround = download zip, change, upload zip.

    I hope it will be fixed some day.

    Hi!

    The developers here have had a look at the issue. This should be fixed for you now! Let me know if you're still having trouble.

  2. richardhealy

    20 Dec 2015 Administrator

    We will raise a ticket and get it checked out for you.

  3. Great! thank you

  4. richardhealy

    23 Dec 2015 Administrator Answer

    Hi!

    The developers here have had a look at the issue. This should be fixed for you now! Let me know if you're still having trouble.

  5. Unfortunately we are still experiencing the issue... (or maybe again) If we remove the content from default.twig, save works. If we fill the file even with 1 line, the error occurs.

    This also happens with default.twig that is not inside a directory.

  6. richardhealy

    17 Feb 2016 Administrator

    I'll get the support team to look at it.

  7. It looks like that if there is an error in the twig save fails.

    If in a feature widget the background is set with:
    asset(images/image.jpg)
    and we change it into
    url(http://www.x.nl/image.jpg ) <- incorrect parameter for the widget

    We are not able to save it. But with "http://www.x.nl/image.jpg" it works.

    So it looks like the unable to save error actually means: you have an error in the syntax of your twig

  8. richardhealy

    24 Feb 2016 Administrator

    Our developers are still looking into the issue. As soon as I know something, I'll get back to you.

  9. richardhealy

    25 Feb 2016 Administrator

    Hi ajvhek,

    The first issue discussed is about deleting content and adding it again on the default.twig. This should throw an error but it's not (when you try it). So, if you can generate a few steps to replicate it, that would be great.

    The second issue is about the syntax. I have raised this to our product team (as it is a product request more than a bug) and asked them if we can add this to the roadmap.

    Let me know about the reproduction steps, and we'll get back on the case.

or Sign Up to reply!