Editing a post's tags doesn't remove old ones

roughnecks commented

2024-10-09 23:52:54 +02:00

I added this bookmark: https://blasta.woodpeckersnest.eu/url/25b8b3674c7fa11fa6c6674fc5f230cf
without remembering that tags have to be comma separated, so it published a very long tag with several words.

Then I thought to edit my post and replace the tags, this time correctly written, but the post retained the old wrong tag, and also added the new ones.

I think it should "forget" the old ones if you want to replace them.

I added this bookmark: https://blasta.woodpeckersnest.eu/url/25b8b3674c7fa11fa6c6674fc5f230cf without remembering that tags have to be comma separated, so it published a very long tag with several words. Then I thought to edit my post and replace the tags, this time correctly written, but the post retained the old wrong tag, and also added the new ones. I think it should "forget" the old ones if you want to replace them.

sch commented

2024-10-10 06:59:50 +02:00

Owner

I think so, too.

I did not add a mechanis, to update am entry upon update by the first JID.

This is how the mechanism works:

The first time, that a new bookmark is aggregated to a Blasta instance, determines the entry in the system database which be displayed to others. In other words, the first JID to bookmark, is the JID which determines the details that be displayed by Blasta.

Please. Connect and check again. And see whether your bookmark is dispplayed differently.

As displayed to the public

As displayed to JID which has that entry

The sidebar for JID should display its own tags.

I think so, too. I did not add a mechanis, to update am entry upon update by the first JID. This is how the mechanism works: The first time, that a new bookmark is aggregated to a Blasta instance, determines the entry in the system database which be displayed to others. In other words, the first JID to bookmark, is the JID which determines the details that be displayed by Blasta. Please. Connect and check again. And see whether your bookmark is dispplayed differently. As displayed to the public ![scrot-rofi_20241010-080134](/attachments/890ba8d3-0e43-4a65-b237-865e6cb9e6fb) As displayed to JID which has that entry ![scrot-rofi_20241010-080156](/attachments/8f477b4f-9105-44f6-8434-367399adbd6e) The sidebar for JID should display its own tags.

scrot-rofi_20241010-080156.png

68 KiB

scrot-rofi_20241010-080134.png

34 KiB

roughnecks commented

2024-10-10 07:24:21 +02:00

Author

I was already connected.
Anyway, disconnected and connected again, the long tag is still there:

I was already connected. Anyway, disconnected and connected again, the long tag is still there: ![image](/attachments/6ea66af0-82ba-48a6-99dc-1a58bc9b3f4f)

image.png

2.5 KiB

sch commented

2024-10-10 20:03:16 +02:00

Owner

If that tag is not associated with any other bookmark, then Bkasta should set the counter to zero (0) and the SQLite database should trigger an action to remove that tag from the database.

Please verify, that this tag is not associated with any other bookmark in the system.
Please confirm, that you are using the latest version.

If that tag is not associated with any other bookmark, then Bkasta should set the counter to zero (0) and the SQLite database should trigger an action to remove that tag from the database. - Please verify, that this tag is not associated with any other bookmark in the system. - Please confirm, that you are using the latest version.

roughnecks commented

2024-10-10 20:18:07 +02:00

Author

I have posted the bookmark link and a picture which shows the number (1) on the tag.

~/Blasta$ git pull
Already up to date.

I have posted the bookmark link and a picture which shows the number (1) on the tag. ~/Blasta$ git pull Already up to date.

sch commented

2024-10-10 20:35:59 +02:00

Owner

Please backup the database, and connect to Blasta again.

mv main.sqlite main.sqlite.bak

Please backup the database, and connect to Blasta again. `mv main.sqlite main.sqlite.bak`