Activities of "yekalkan"

Hi @adrianl

As the Text Template Management module document says, it is used to store and edit template contents for the text templating system of the ABP framework. So there is no backend implemantation for creating a new text template. Furthermore, this is not the purpose of this module.

Is there also a way instead of saving the template as a virtual file we can store the template on the database?

When you edit a template, edited version will be stored on database and the default version will remain same in virtual file system. The time user wants to reach the template, database version will have a higher priority. Thats how the text templating system works.

Hi @trina.thompson

We suggest you to use the basic theme if you will create a website to use docs module.

I'm closing this issue because this is a known problem and a fix is already in our plans. Also, your question credit is refunded.

Hi @kapil

I've created an internal topic for all the issues you opened that day. Development team will deceide to implement them or not.

Thanks you for your feedback.

Hi @james

There is a known problem with parsing enum files, it will be fixed in the next patch. I'm refunding your question credit.

Urgent solution: Change the enum file to file-scoped namespace

example:

namespace MyApplication.Cars;

public enum CarType
{
    Sedan,
    StationWagon,
    Coupe
}

Hi @yasin.hallak.89

Pages feature comes from the free version of CmsKit module which CmsKit-Pro depends on.

You can access the source code from https://github.com/abpframework/abp/blob/dev/modules/cms-kit/src/Volo.CmsKit.Admin.Web/Pages/CmsKit/Pages/Create.cshtml

Hi again @LinchArnold,

Now I reproduced the issue, fixed it internally and added it to next patch release.

For now, i can provide you a simple but dirty workaround if this is urgent for you:

1. Change the name of DbContext interface file (I{Your_Project_Name}DbContext.cs) in your project to something else (example: Random_Name.cs).
2. Generate your entity via suite.
3. Revert the file name.
4. Manually add the new entity to DbContext interface file. (Line to add: DbSet<{Your_Enttiy's_Name}> {Your_Entity's_Name_Plural} { get; set; })

Be sure to rename both MongoDb & EfCore DbContext interfaces before entity generation, but do not take any action for DbContext classes.

Can you try AccountResource instead of AbpAccountResource?

@LinchArnold Have you made any changes to *{You_Project_Name}DbContext.cs file after project creation? Can you share the file content?

There is a typo in the screenshot (AbpAccountrResource instead of AbpAccountResource). Does the error persist when you fix it?

What does the error say?