You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been testing grav-theme-resume and since most of the content is in the frontmatter section of each file, I tried to update the content using the GRAV ADMIN. Once I do that the content dissapears from the page because the editor seem to damage the frontmatter content, like so
Once this happen, the section on the page renders empty. I've been loking for this issue on the GRAV ADMIN repo, but there is no mention of these kind of issues
The text was updated successfully, but these errors were encountered:
Update the problem is not that the frontmatter is changed upon editing the file, the issue is that GRAV ADMIN renames the file to default.md upon saving it. Maybe you should update the template, changing all of the files in the right and left folder to default.md, in order to allow for the content to be updated using GRAV ADMIN
This is a problem with both the skeleton and the theme structure, with the Admin plugin conventions. Not the other way around (not a problem of Admin).
Fast fix: rename your pages to default.md, and add for example, for education.md, template: education in the page frontmatter.
In Grav 1.1 and Admin 1.1, that property will be kept and the site should work the same way.
Longer fix: revisit completely how the theme is built, make use of modular pages, and edit the skeleton pages accordingly, at some point this needs to be done.
Hi:
I've been testing grav-theme-resume and since most of the content is in the frontmatter section of each file, I tried to update the content using the GRAV ADMIN. Once I do that the content dissapears from the page because the editor seem to damage the frontmatter content, like so
Once this happen, the section on the page renders empty. I've been loking for this issue on the GRAV ADMIN repo, but there is no mention of these kind of issues
The text was updated successfully, but these errors were encountered: