urosm
/
ikiwiki
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

debugging information

master
https://id.koumbit.net/anarcat 2012-04-23 09:59:26 -04:00 committed by admin
parent 2a951515be
commit 5487c524df
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/plugins/contrib/ikiwiki/directive/ymlfront/discussion.mdwn
View File

@ -28,4 +28,6 @@ I have tried both the ymlfront directive and the YAML markup (with the
> > Document: 0 > > Document: 0
> > at /usr/share/perl5/YAML/Loader.pm line 38 > > 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]]