ChestShop Notifier

ChestShop Notifier

10k Downloads

/Csn clear not working

Castiella opened this issue ยท 14 comments

commented

When a player does /csn clear, it will clear the history. However, if they leave the server, the history is still there when they re-join.

Here is a latest log, which should include me testing this. I am also using paper 1.13.1 (build 229)

let me know if
latest.log
you need any information.

commented

Did this get resolved @mare-on @Castiella ?
Do you still have this issue?

commented

Not working on Build 51, latest versions are not working that great with chestshop which is why i'm on build 51.
image

commented

@Laukage What do you mean? The latest builds work completely fine. I run them on my server. If you are having problems with it then please open issues!

As for issues with the clean command here: Please test on the latest build and if you are still experiencing issues with it then provide the following information:

  • A full server log
  • What you do when you run into the issue and what you expect to happen
  • If you can the entries in the database (e.g. in form of a mysqldump or SQLite file) that cause the issue
  • (if using MySQL) the MySQL server type and version
commented

It works for me using 1.3.0-SNAPSHOT (build#35)
PaperSpigiot 1.12.2 #1574
Just saw this issue because I faced the same problem before updating.

commented

Im using 1.13, not 1.12 - the plugin works fine on 1.12

commented

It is working for me on 1.13. I've found another bug though which might be the behaviour that you are noticing? Please test the latest dev build.

commented

Using latest dev build and still having this error.

commented

Please test with the latest development build and see if it still happens with that.

commented

Still happening with the recent build

commented

any update on this?

commented

The issue is in file Clear.java on line "statement.executeUpdate("DELETE FROM csnUUID WHERE Unread='1' AND ShopOwnerId='" + senderId.toString() + "'");" Where Unread='1' is wrong, it must be Unread='0'

commented

Using the latest build and have the same issue. I will look at the code, maybe I will find where is the problem.

commented

Ok... it's weird... it didn't work but now it works good... hmm... I will be watching it but for now looks like evething is fine idk how.

commented

I'm pretty sure Unread='1' is correct there as the command should only remove read entries, not unread ones. (If it's 0 it means that it hasn't been read with /csn history yet and yes, the naming is unfortuantely backwards to what one would expect)