From 5487c524df984d7e2f79dd8f9c01edf08403e07c Mon Sep 17 00:00:00 2001 From: "https://id.koumbit.net/anarcat" Date: Mon, 23 Apr 2012 09:59:26 -0400 Subject: [PATCH] debugging information --- .../contrib/ikiwiki/directive/ymlfront/discussion.mdwn | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/plugins/contrib/ikiwiki/directive/ymlfront/discussion.mdwn b/doc/plugins/contrib/ikiwiki/directive/ymlfront/discussion.mdwn index ab8ed85de..e9431dc83 100644 --- a/doc/plugins/contrib/ikiwiki/directive/ymlfront/discussion.mdwn +++ b/doc/plugins/contrib/ikiwiki/directive/ymlfront/discussion.mdwn @@ -28,4 +28,6 @@ I have tried both the ymlfront directive and the YAML markup (with the > > Document: 0 > > at /usr/share/perl5/YAML/Loader.pm line 38 > > -> > Now *that* has to be related... ;) In the index.db, there is no ymlfront metadata for the sandbox page... Note that the `---` delimiter approach doesn't trigger the warning but doesn't populate the DB either... --[[anarcat]] +> > Now *that* has to be related... ;) In the index.db, there is no ymlfront metadata for the sandbox page... Note that the `---` delimiter approach doesn't trigger the warning but doesn't populate the DB either... +> > +> > Finally note that after adding debugging code, I was able to figure out that this seems to be using the `YAML::XS` library. I have also traced the data and confirmed that `$yml_str` does get properly initialized in `parse_yml`, and it is where the error is generated. So maybe there's something wrong with the YAML library? --[[anarcat]] -- 2.44.0