We're using MySql.Data package for connecting to MySql database.
When I checked this error, I saw that this is an issue in this package, and they fixed it in the newest version, see https://github.com/mysql/mysql-connector-net/commit/16ad749586b0e5eb1aad127e3744096692e4a6ae#diff-f422179f18fcab216691dde319e2c13c0a615a2474d2d8e227bdc15b3ed52f50
After updating this package to 8.0.32.1, it'll be fixed.
https://www.nuget.org/packages/MySql.Data/8.0.32.1
Download the package https://www.nuget.org/api/v2/package/MySql.Data/8.0.32.1
Then extract the zip file.
Overwrite MySql.Data.dll in the following directory (your version maybe different, check pls):
The bot automatically closes it, if there's no activity from the ticket owner. @kirotech, I reopened the ticket. and please send an email to info@abp.io if you have such issues. Many people are subscribed to this topic and reading your -personal- problem.
Hey I don't think this problem just for us. I would suggest you to keep tickets open for at least 30 days. Because not everybody has time to respond with technical details in 7 days.
Another suggestion I would like to make. We need private tickets. Because paying customers are paying for support also why all tickets has to be public? Some problems are delicate and includes security questions like we have with your not working oauth openid functionality we have to share our applications configurations publicly this just doesn't make any sense.
Also another thing. I think your support tickets creator filter is privacy problem. If I search @gmail.com I can find emails from your support system database. Also I can find your customers account names. I would suggest to improve that or just remove it from public.
Also another thing how you can improve you support is by providing reliable information when you going to release bug fixes what we found in your abp commercial. As example your abp commercial payments bugs which we reported and had to ask several times which version fix will be included in.
To ask questions privately, you can upgrade to the Enterprise License plan.
I understand your concern about email privacy but that combo box you mention only shows usernames. If the account owner writes his email to the username area then it'll be shown, if he writes his cell phone its shown. if we remove it from there, it's still visible in the question-answer sections. hence this is not a privacy deal.
On the other hand, if you want to see raw and detailed change logs for every release, please check the full change logs document that we recently started to publish https://docs.abp.io/en/commercial/7.1/change-logs/index
This is not a security issue because only the website can modify the cookies. 3rd Parties cannot alter the cookie value as the browser is responsible to secure the cookies. The scenario of attacking the local machine and getting the cookie is another issue that the victim should care about because even if the attacker retrieves the cookie, there's no need to evaluate a script on it. They can log in to your account with the cookie without any password and do whatever they want.
As summary, this is not a real-world attack vector.
could you provide us the entity JSON files.
can we close this question?
we'll test this case
The bot automatically closes it, if there's no activity from the ticket owner. @kirotech, I reopened the ticket. and please send an email to info@abp.io if you have such issues. Many people are subscribed to this topic and reading your -personal- problem.
I reopened the question.
hi,
ABP Suite overwrites the code that it generates. For backend code, you can create partial classes to have your custom code in separate classes.
did you set this cookie value manually?
