Skip to main content

HTML EXPORT - .ZIP DOWNLOAD CONTAINS A LARGE CACHE FOLDER OF UNKNOWN ORIGIN

Comments

8 comments

  • K C George

    Hello Geoff,

    We would like to investigate the issue you have mentioned.  Would you kindly provide us with your project's brizy.site URL?

    0
  • Geoffrey Summerfield

    Hi K C,

    Thank you for your response. My brizy.site reference is : "https://fig17220599.brizy.site/".

    I have saved the offending cache folder, so if you would like this please advise - its 23MB.

    Thanks.

    Geoff

    0
  • K C George

    Hello Geoff,

    I generated the Export HTML file for the above project. Have a look at https://jmp.sh/Hk1guh58 I don't see a cache folder when I unzip the file. The "assets" folder is the only one that is present. How do I reproduce the issue you are seeing?

    We have revised the procedure for Export HTML. After uploading the content of the ZIP file, you must also upload a .htaccess file. You can see the revised process at https://support.brizy.io/hc/en-us/articles/360026945332-Export-HTML   

    0
  • Geoffrey Summerfield

    Hi K C,

    The Export HTML file that you generated does appear to be correct, with no issues.

    I thought the issue was therefore just a temporary glitch, and I tried to confirm the issue was gone by completing another HTML Export publish. This time, the "cache" folder was NOT generated AND all the html files were fine with no unknown additions. However, the Export HTML file size was 9-10MB larger than usual and when I inspected the "assets" folder more closely, I discovered quite a lot of images that are not present anywhere on my own site. For e.g. there are several images of (again) German text, and several portrait pictures that are not on my site - so the problem remains, albeit now in a slightly different form.

    When generating my Export HTML file, I start from the initial admin screen listing all my "Personal Projects", hover over "FBP", click on the "..." that then appears in the top RHS, click on "publish", then click on the "Download Now" text link that appears at the bottom of the page.

    I have an .htaccess file containing the necessary .html rewrite code permanently in the root of my site.

    I can provide this latest export HTML file (which is 20MB, when should be about 11MB) containing the additional unknown images. 

    0
  • K C George

    Hello Geoff,

    Can you do two more tests?

    1. Sign into your dashboard using a different browser (that you don't often use for Brizy Cloud) and generate the Export HTML file like you normally do and check if it makes a difference.

    2. Sign into your dashboard from a "new private window" ( or a new incognito window) of your regular browser and generate the Export HTML and check if the issue persists
          
    0
  • Geoffrey Summerfield

    Hi K C,

    The tests you suggested do appear to have been instructive :

    - Google Chrome - ordinary window - no additional folders/files

    - Google Chrome - incognito window - no additional folders/files

    - Firefox - ordinary window - no additional folders/files

    - Firefox - private window - no additional folders/files

    - DuckDuckGo (My usual browser) - ordinary window - additional folders and/or files of unknown origin

    - DuckDuckGo (My usual browser) - Fire window - additional folders and/or files of unknown origin

    So barring the unlikely possibility of an intermittent fault that has just happened to crop up - repeatedly - when using the DDG browser - and NOT crop up when using the other browsers, it does look like it is something to do with the way DDG is interacting with the Brizy Html Export code on the server??

    Whilst using a different browser might be a viable workaround, due to the superior privacy features built-in to DDG - which may of course be the very thing causing the issue?? - I am hoping a solution can be found which makes it possible to continue using DDG.

    Any further thoughts would be much appreciated.

    0
  • K C George

    Hello Geoff,

    I appreciate the thorough troubleshooting you carried out.  You've discovered something interesting regarding how extra folders and files are created in the ZIP file when exporting HTML using the DuckDuckGo browser. I am afraid we may not bring out a solution specifically for DuckDuckGo as its not being used widely. What if you keep DuckDuckGo as your go-to browser and use an alternate browser only for exporting HTML?

    0
  • Geoffrey Summerfield

    Hi K C,

    Thank you for your feedback. I was thinking that doing as you suggested might be a half solution - particularly as DDG seems to work fine for doing all the design work online, so I could just login via a different browser, as you suggest, simply for the creation of the .zip file.

    I may well have to do this, as these days it is seriously NOT a good idea to have other people's files and folders appearing on your website!!

    Many thanks indeed for your assistance.

    Kind regards,

    Geoff

    0

Please sign in to leave a comment.