gingko / client

Gingko Writer. Tree-based writing software, written in Elm.
https://gingkowriter.com
MIT License
361 stars 49 forks source link

No Word Export after version 2.4.11 #196

Closed toppinglift closed 4 years ago

toppinglift commented 4 years ago

Describe the bug A clear and concise description of what the bug is. After updating to versions 2.4.12 and 2.4.13, there was no Word export. The app does not save any file. To Reproduce Steps to reproduce the behavior:

  1. Go to File-->Export as MS Word-->Current Card and Children OR Entire Document. Export to MS Word dialog box pops up. Enter a file name with docx extension.
  2. Click on 'Save"
  3. Nothing happens--no file is saved. This error only occurs in versions 2.4.12 and 2.4.13. If you roll back to version 2.4.11, you can export to Word.
afenc commented 4 years ago

similar bugs noted here. In fact all export options (word, text, JSON; entire document, current card and children, column 1 or 2) are not working.

Software info: OS: [macOS 10.15.4] Gingko Version [2.4.13.567] (2020-05-30 updated) -> new release [2.4.14.569] has same issues

Every export options work well after Reinstalling the older version (2.4.10). Sadly, gingko automatically updated to 2.4.13 after quit-restarting the app.

AdrianoFerrari commented 4 years ago

Thanks for the bug reports, I wasn't aware of this and didn't come across it during testing.

@toppinglift are you on macOS as well? Anyone else having this issue, or not having this issue in 2.4.12+?

toppinglift commented 4 years ago

My OS is Windows 10. My gingko also updated automatically to 2.4.13. Can we please have the option to shut down auto-update for cases like this?

AdrianoFerrari commented 4 years ago

Thanks for the bug reports everyone. I've uploaded a new release that should fix this.

Regarding disabling auto-updates: it's a possibility, but it's work to implement. In case of a new bug introduced with no quick fix, I can disable the version on my end, so it won't autoupdate people to the buggy version. I should have done that sooner in this case.