Join the conversation

Sign in to join this conversation, and others like it, in the communities you care about.

Wekan

Wekan is an open-source kanban board (Trello like) which allows a card-based task and to-do management.

Wekan / Bugs

Update recently? deleting

Update recently? deleting

Wekan / Bugs · February 28, 2020 at 4:04pm (Edited 5 years ago)

was there an update last evening or the day before?

deleting archived cards do not stay deleted. Refreshing screen and they return in the list of archived things to delete

HOW do you clear out all cards from the system not using the GUI? Its suddenly happening on all three systems with no code changes.

Can we roll back to the last version. THis is broken

other issues: when updating with new cards from the api looking at the contents of the new cards put the GUI into some sort of wait mode. Until you refresh the screen several times you get this behavior that indicates its not connecting to Mongo or something

In fact the deleting the archived boards works and on screen refresh they are still there seems like its never deleting from Mongo at all

Another hint: in addition to the GUI thinking the archived card is deleted and when you refresh its not, the webhooks are not being sent out when the delete happens. So it seems that the GUI is disconnected from the mongo and webhook piece entirely.

Question: in addition to rolling back the code, using snap installed wekan, what is the correct way to get into mongo shell under snap wekan? I can at least see what is in the database then and perhaps clear it out

LMK

more hints, I can't delete archived cards but I can restore them. When I do I cannot disable or remove webhooks associated

HOw do I get into wekan under snap mongo to clear these out?

Load previous messages

March 1, 2020 at 3:27pm

you should be able to repeat this without any more details from me

    • reply
    • like

    LMK your thoughts or if my procedure is flawed

      • reply
      • like

      Thanks again

        • reply
        • like

        as expected the first of the three boards that was attempted to be deleted with the gui is now gone on browser refresh, the other two (in order) remain

          • reply
          • like

          that single webhook fired at the same time and worked without server errors and did what it was supposed to do on my end, it deleted several database rows in two different tables ( a card table for each card - 3 rows) and a list table that for each board has a row with all list ids for that board - 7 rows)

            • reply
            • like

            going to fix that NTP issue then try and figure out when the nightly check and update that is indicates is run between 2 and 4 AM shows a change in code

              • reply
              • like

              Would like to figure out when exactly that code was changed and then if possible what the version sub id is.

                • reply
                • like

                thanks

                  • reply
                  • like

                  March 1, 2020 at 4:55pm

                  hint: although I deleted all three boards together initially, I thought they would delete one at a time. I was incorrect. after the first one actually get deleted you have to requeue each deletion. Meaning that the second and third deletes are not in queue, they are being thrown out till the one before it goes through. So after each delayed delete actually fires you have to go back and issue a new delete request for the next one

                    • reply
                    • like

                    Hmm, I think I'll revert my in-progress Wekan background url feature code and make a new Wekan release with auth fixes

                      • reply
                      • like

                      I mean Wekan background image feature code

                        • reply
                        • like

                        it seems completely related to web hooks

                          • reply
                          • like

                          Do you use LDAP ?

                            • reply
                            • like

                            nope

                              • reply
                              • like

                              I have two users (the admin who owns all api elements

                                • reply
                                • like

                                and when I add boards another password based "user" is added to every board as a viewing member

                                  • reply
                                  • like

                                  are there any Rules at board?

                                    • reply
                                    • like

                                    not sure what you mean

                                      • reply
                                      • like

                                      IFTTT Rules, it's at Lists/Swimlanes/Calendar/Rules menu

                                        • reply
                                        • like

                                        I add one public board and wait till it returns and capture its id and swimlane

                                          • reply
                                          • like

                                          then I add one member

                                            • reply
                                            • like

                                            Anyway, I'll make new release and then we'll try does it still happen.

                                              • reply
                                              • like

                                              then I add one integration, seven lists this is a recursive call capturing each id and storiung in my databse

                                                • reply
                                                • like

                                                sound good

                                                  • reply
                                                  • like