Activities of "EngincanV"

Also, please share your exact ABP Version (v8.x.x), index.js and EditModal.cshtml.cs file contents.

Hi Engincan, Thank you for your reply. Please follow the below steps

1. Create project with 7.0.4 version
2. Add one entity with few columns and UI using abp suite
3. Now upgrade your project to version 8.0.5
4. Open abp suite and modify the existing entity which was created in version 7.0.4 & add one more column
5. Keep all the options check in abp suite except "Custom Change" in abp suite 8.0.5.
6. It will gives an error while updating database.

Thank you.

Hi, thanks for the explanation. I reproduced the problem and will fix it asap. Closing the question because I created an internal issue to track the problem and refunded your ticket.

In the meantime, you can remove the duplicated dbset for a quick workaround.

Regards.

Hi, I could not reproduce it. Can you explain your steps in detail with entity metadata if possible?

Any updates on the frontend portion?

Hi sorry for the late response, you should add the @volo/abp.ng.payment package to package.json and configure the Payment Angular Module as below:

.....
import { PaymentAdminConfigModule } from '@volo/abp.ng.payment/admin/config';

.....

PaymentAdminConfigModule.forRoot(),

{
path: 'payment',
loadChildren: () =>
  import('@volo/abp.ng.payment/admin').then(m => m.PaymentAdminModule.forLazy()),
}

But since you use Blazorise, can you also integrate the BlazeSpark - Admin & Dashboard theme from Blazorise?

Hi, this is a custom need, so you should manually implement it if you want, but yes it's possible.

And the chat module should open in a disappearing overlay or in a popup and not on the page, so the users don't loose the work that they are you doing.

Please, create a new question for that.

OK that will work for now, can you let me know how to track this so I know when it is fixed?

And since this is a bug can you refund my question credit?

Thanks,

Karim

I have refunded your ticket, just now. Thanks again for reporting the problem. This problem has been fixed and will included in the first upcoming release. (probably with v8.1.0)

Hi, for a quick workaround, please remove the .ToString("d") statement from the faulty lines and add (int) before the context. statement. For example:

{(int)context.Message.SenderUserType}

I'll check and fix this problem for ABP Suite. Thanks for reporting.

Hi, we don't support it yet. We have an issue for that in backlog. Regards.

For the backend side, please remove the *.WeChat.Web and *.AliPay.Web projects from both Volo.Payment.sln and your project's solution reference. )

I'll check for the frontend side.

ABP Framework version: latest

Can you say which version do you use exactly, the latest stable (v8.0.5) or the latest preview (v8.1.0-rc.3)?