New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Page Metadata #1149
Comments
Hi there! Luckily the solution is very simple:
Done! Regards |
I knew it had to be something simple. Thanks! |
Hello, I have something related to this.
These values are currently being generated through an enum and I would like to have them be generated dynamically from an external source when I open the page edit screen in the manager. Is there a simple solution to this? |
@yiqi0110-glitch The built in https://piranhacms.org/blog/creating-a-custom-tag-field Regards |
However, this is a good idea that I'll add an issue for. |
Hello again, I have followed the steps from the blog and I get this issue in the browser console. piranha-deps-dev.js:16016 [Vue warn]: Unknown custom element: - did you register the component correctly? For recursive components, make sure to provide the "name" option. found in ---> The code that seems to differ from mine to the example is,
|
Please open a new issue if you need help instead of adding comments to closed issues. / Regards |
I have a handful of fields that I would like to add into the manager page settings modal. These will be used by our custom search module for indexing and are not needed to be rendered on the front end. I'd prefer not to extend pagebase or the db schema for that but it's not clear if I can add those as per https://piranhacms.org/docs/extensions/fields to a child class? If so, can I specify that they be rendered in the manager settings modal? I am able to customize the modal partial and js to have a new tab and fields and it posts the field values to the api/page/save/draft endpoint but it's not clear how to persist them to Piranha_PageFields.
I can manually persist those in PageService.Save(PageEditModel model, bool draft), or I can just persist the fields to a separate table in the same method, but it seems like I'm missing something simple here.
Am I approaching this correctly?
The text was updated successfully, but these errors were encountered: