Hi, normally it should not be like that. It seems there is a mis-configuration in the database side. I will check your project and write you back asap.
Hi, thank you very much. I imagine this applies to all entities, but I would like to do it for just one entity.
Hi, when you do this the related placeholder will be applied to all of your index.js files. However, since you will only write your custom code for a single index.js file, the other placeholders will be empty and they will be shown as comment blocks. So, you will be able to write your custom code per file by your choice.
Hi, yes you can use the custom code support to add an entity-action to the data table directly. You can apply the following steps:
1-) Edit Frontend.Mvc.Page.index.js.txt template and add custom-code block placeholder:
//<suite-custom-code-block-10>
//your custom code goes here...
//</suite-custom-code-block-10>
2-) Regenerate the same entity, after you do that the placeholder will be added for the related entity, and you can update the content in the placeholder for the related index.js file:
//<suite-custom-code-block-10>
,{
text: l("ClickHere"),
action: function (data) {
//define what should happen when to the action clicked
}
},
//</suite-custom-code-block-10>
3-) Then in the next code generations, ABP Suite will respect your change, and will not override the specified section.
For further info please refer to the documentation: https://abp.io/docs/latest/suite/customizing-the-generated-code#adding-new-custom-hook-points-changing-their-places-1
<suite-custom-code-block-10>is just an example placeholder, you can use any number, however, please note that the number should be used only once per page.
Hi, indeed there is a problem as you stated. But this is by design for now. I will create an internal issue for that because I agree that we should also reflect the impersonation on the auth server side.
Thanks for reporting. Regards.
Hi @EngincanV ,
why did you close the thread about abp 8.3?https://abp.io/support/questions/7844/Bugs--Issues-v83x
Thanks
Hi, it was by mistake. Thanks for reminding me. I've reopened it.
yes! worked
Glad to hear that. Probably it was a temporary problem due to your projevlct and suute integration. Closing the question since your problem is resolved.
Feel free to reopen it if it occurs again. Best regards.
Hi, this is indeed a very strange bug. Can you remove your solution from ABP Suite, then clean&build your solution and try to add the solution again and regenerate CRUD pages?
Indeed there is a problem as you stated. I will create an internal issue for this problem.
However, for a quick workaround you can apply the following instructions:
1-) Open the appsettings.json file (it's under the %%user-profile%%.abp\suite) and manually fix the following parts in the solution section:
Change UiFramework to 7, set the BlazorWebAppProjectDirectory as your project directory:
//...
"Name": "<YourMicroserviceName>",
"UiFramework": 7,
//...
"BlazorWebAppProjectDirectory": "<your-directory-structure>\\apps\\blazor",
"UiFrameworkName": "BlazorWebApp"
This will fix the code generation path but the menu item creation still be problematic and give errors. So for now, I suggest you to generate everything except the UI, and wait for the next patch. In the next version, once we fix this problem, you can regenerate it with the UI.
Sorry for the trouble. Regards.
Hi Engincan, thank you for your return.
As I have a limited amount of credits in my licensing, considering this is a Bug and will be fixed, please reset this credit Issue counting on my account. Now I have no more credit but when you return me this credit I will be able to open a new ticket in the future.
Sure, I have refunded your ticket and closing the question.
Thanks for your understanding. Regards.
Hi again, we reproduced the problem as you stated and created an internal issue (with number 2626) and will fix the problem as soon as possible.
Best Regards.