I installed Zim-Wiki (075.2) from opensuse on my fairly standard Leap 15.6 distro after reading and about it in this and FOSS forum. I found it to be really great for my requirements and easy to setup and use.
Unfortunately I get an error when trying to export to html or markdown format and can’t find help in Zim-wiki.org or searching through. It seems Zim users are moving to other apps, but if somebody here can point me in the right direction it would be great.
In the off-chance, I include below an extract of the error I get:
ERROR: Exception exporting page: <10 DISTROS>
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/zim/templates/expression.py", line 120, in __call__
value = value[p]
TypeError: 'PageProxy' object is not subscriptable
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/zim/notebook/page.py", line 153, in makeValidPageName
Path.assertValidPageName(newname)
etc
Thank you @marel , I wasn’t sure if this was better raised here (i used the suse repository) or with Zim (what I found seemed to be all about ubuntu distros).
Thank you @malcomlewis , I can see how there is a possible connection to the old bug report, but the details and patch are completely beyond me. So will need to wait to see if someone more knowledgeable than me has some plain instructions that I can follow on Leap!.
Incidentally, I tried the flatpak version but I got a different error and quickly abandoned it
I followed your suggestions, created a new test user, created a new Zim notebook, very small but inserted test jpg and a pdf attachments and tried to export: it worked perfect.
I then copied my original (~2Mb) Zim notebook back to the new test user. I tried again to export but this time got the same error. Finally I tried with another, larger Zim notebook (13Mb). This time it exported perfect.
So the problem must be due to something in the original notebook, its attachments, insertions or even extraneous characters that sometimes my unreliable touch-typing creates. It will be hit-and-miss but hopefully I should be able to identify the culprit.