Create New Schema Field Like HTML Markdown Field, Slug etc. #360
-
Hello, |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
New collection field types cannot be added adhoc like "plugins" since this will complicate a lot of things (data persistence, db constraints, validation, filtering, etc.). If you have modified the source and want to display your custom field types, you'll have to also:
I'm not sure what is your use case, but I wouldn't recommend going with this approach, especially since the project is not stable yet and you'll have to manually keep your modifications in sync. If you have a need for a "slug" type field why not use the existing There is also option to add new fields in the PocketBase core so that they are available for everyone, as long as the use case is generic and fairly common. I'll have to think a little more on this, but since the markdown/html field type is practically a |
Beta Was this translation helpful? Give feedback.
-
Thank you very much for your valuable reply. Yes I read in the answers that this system was not developed for a CMS. But why not ? In order for it to be a CMS, a few fields such as slug and HTML are sufficient to present a simple CMS structure. Apart from these, there are no serious shortcomings. Text fields are sufficient to use for SEO meta. Relations is sufficient for taxonomies such as categories and tags. There isn't much left. Of course, if there is a plugin logic, this will speed up the development of the system, but it is not an urgent priority for CMS. Personally, I can make a very adequate CMS out of this system with html field. Because the system provides me with almost everything I need. For example, I have read the map field suggestion, and it seems to have been added to the road map. It will also be a super feature for CMS. When Slug and HTML support comes, I'm sure many people will start using this system as a CMS. This will certainly contribute to further support of the project. As this project supports CMS structure, I am sure that modules such as html template editor and liquid template editor will be developed by other developers. I will probably do the first study on this subject :) In short, maybe a few areas that you can easily add in a few days will allow the project to gain many contributiors. Frankly, I've been experimenting with orchard core cms and docs for months. It's a very well planned project, but the way it's broken down into too many parts has made the project overly complex and difficult to understand. Therefore, while I was looking for something more practical, I saw your project and was amazed. The flexibility I was looking for and the simplicity I was looking for in this project. Of course, they are not exactly the same things, but I also studied Qor, but Pocketbase offers a more flexible structure than that. I will continue on my way with pocketbase and try to contribute as much as I can. Best regards Gani |
Beta Was this translation helpful? Give feedback.
New collection field types cannot be added adhoc like "plugins" since this will complicate a lot of things (data persistence, db constraints, validation, filtering, etc.).
If you have modified the source and want to display your custom field types, you'll have to also:
I'm not sure what is your use case, but I wouldn't recommend going with this approach, esp…