Attachments fixes after migration to meteor files (image preview, global search)

[mfilser]

Attachments fixes after migration to meteor files (image preview, global search)

• global search was broken
• image preview is back again
• wrong mongo index was created
• attachment count on minicard was missing

should also fix: #4395

[BabyFnord]

@mfilser and @xet7 though stated otherwise, this did not fix #4393 unfortunately. We would be happy, if you could have another look into it. Thank you!

[mfilser]

@BabyFnord
I think your issue is completly different from this pull request. I don't have any experience with uberspace deployment, maybe the migration wasn't completed at your installation. As i see uberspace is commercial you should consider to contact the support of uberspace...

[BabyFnord]

@mfilser Apparently @marek94901 has the same issue on a presumably non-Uberspace installation. @marek94901 maybe you can shed light on your install specs here, for further reference? WeKan deployment on Uberspace is on behalf of every user her-/himself, and largely follows this bundle based installation guide.

My WeKan instance never had this issue before, starting from v5.17 through (almost) every iteration. The changes introduced to v6.11 broke existing and new attachments. How should Uberspace support know what WeKan's issues are in this transition? If you do know what to ask or tell them, please tell me. @marek94901 probably would be glad to get pointers too, for his instance.

Switching Node main versions is just sending uberspace tools version use node 14 which renders

Selected node version 14
The new configuration is adapted immediately. Patch updates will be applied automatically.

Apart from that, nothing else changed on my server when upgrading to v6.11. Hence it remains hard to imagine where we users went wrong in this transition. So far I could maintain my WeKan instance without any programming language knowledge.

[mfilser]

Wekan needs a WRITABLE_PATH for migration, this is already mentioned https://github.com/wekan/wekan/blob/master/CHANGELOG.md and in the issue you mentioned here.
You can remove the migration attachement entry from the Migrations collection to force a new migration at next Wekan start. Here's the migration done by Wekan:

wekan/server/migrations.js

Line 1129 in 825bc4c

Migrations.add('migrate-attachments-collectionFS-to-ostrioFiles', () => {

[BabyFnord]

Please forgive me asking for more details, I am not a programmer but try my best by trial & error.

I am unable to find the specific file and set WRITABLE_PATH in a post-install bundle environment. Where do I find the specific file? Once this has been set, how do I

remove the migration attachement entry from the Migrations collection
?

[xet7]

@BabyFnord

Here:
https://github.com/wekan/wekan/blob/master/start-wekan.sh#L13
Bundle info for non-Windows platforms amd64/arm64/s390x/ppc64le is here (all platforms, not only RasPi)
https://github.com/wekan/wekan/wiki/Raspberry-Pi

Or for Windows, add similar setting to start-wekan.bat.
https://github.com/wekan/wekan/wiki/Offline

collections are database tables, you can edit your MongoDB (usually at port 27017, or Snap at 27019) with nosqlbooster:
https://github.com/wekan/wekan/wiki/Backup#using-nosqlbooster-closed-source-mongodb-gui-with-wekan-snap-to-edit-mongodb-database

[BabyFnord]

start-wekan.sh does not to exist neither in my post-install WeKan v6.11 nor v6.12. I see it in the base folder when downloading a fresh copy, but my running installation folder structure is different.

As start-wekan.sh can't be found, what about adding that path to ~/etc/services.d/wekan.ini ?

[BabyFnord]

I can connect nosqlbooster via SSH, but it won't connect to my MongoDB for reasons beyond me. Connecting via Terminal SSH and MongoDB shell, I can list collections like this:

AccountsLockout.Connections
__pre_attachments
__pre_avatars
accountSettings
actions
activities
announcements
attachments
attachments.chunks
attachments.files
avatars
avatars.chunks
avatars.files
boards
card_comment_reactions
card_comments
cards
cfs._tempstore.chunks
cfs.attachments.filerecord
cfs.avatars.filerecord
cfs_gridfs._tempstore
cfs_gridfs._tempstore.chunks
cfs_gridfs._tempstore.files
cfs_gridfs.attachments
cfs_gridfs.attachments.chunks
cfs_gridfs.attachments.files
cfs_gridfs.avatars
cfs_gridfs.avatars.chunks
cfs_gridfs.avatars.files
checklistItems
checklists
cronHistory
customFields
esCounts
integrations
invitation_codes
lists
meteor-migrations
meteor_accounts_loginServiceConfiguration
meteor_oauth_pendingCredentials
org
orgUser
presences
rules
sessiondata
settings
swimlanes
tableVisibilityModeSettings
team
triggers
unsaved-edits
users

Is meteor-migrations something I could work on, and how?

[BabyFnord]

Access by nosqlbooster now works, but in order to get anywhere, I would need to issue some commands. These answers require knowledge about MongoDB and database handling, which likely most end users do not have unless they are dev ops. No answer has been provided on where to set WRITABLE_PATH in a running instance of WeKan. I'm lost here, sorry.