Lines Matching defs:frontmatter

13  * A page represented as a frontmatter
16  *   * change the content of the frontmatter
17  *   * add a header/frontmatter to the content
25     const NAME = "frontmatter";
30      * @var bool Do we have a frontmatter on the page
122      * Update the frontmatter with the managed metadata
130          * Default update value for the frontmatter
141             return Message::createInfoMessage("The frontmatter is not enabled")
149                 throw new ExceptionRuntime("Error while synchronizing data in the frontmatter", self::CANONICAL, 1, $e);
160             return Message::createInfoMessage("The frontmatter are the same (no update)")
166         return Message::createInfoMessage("The frontmatter was changed")
228     public static function createFromFrontmatterString($page, $frontmatter = null): MetadataFrontmatterStore
230         if ($frontmatter === null) {
233         $jsonArray = self::frontMatterMatchToAssociativeArray($frontmatter);
235             throw new ExceptionBadSyntax("The frontmatter is not valid");
237         $frontmatter = new MetadataFrontmatterStore($page, $jsonArray);
238         $frontmatter->setContentWithoutFrontMatter('');
239         return $frontmatter;
260              * where the first element is empty followed by the frontmatter
264                 throw new ExceptionBadSyntax("The frontmatter is not the first element");
305      * making the frontmatter compacter (one line, one meta)
319          * Double Guard (frontmatter should be quick enough)
324             throw new ExceptionRuntime("The generated frontmatter json is no a valid json");
453             LogUtility::msg("The content without frontmatter should have been set. Did you you use the createFromPage constructor");
459             $resourceCombo->setContentWithLog($newPageContent, "Metadata frontmatter store upsert");
472      * @return string - the new markup (ie the new frontmatter and the markup)
480          * EOL for the first frontmatter