From 50af3fc6e2e199104660e1dc4b5e8baa2796a260 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Michael=20Gro=C3=9Fe?= Date: Mon, 15 Jun 2015 13:21:17 +0200 Subject: [PATCH] Do not save data during metadata run Saving data on the metadata run conflicts with the hidepages plugin. A loop is created and within one sql-query another one is started. This creates lots of 'database locked' error messages --- syntax/do.php | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/syntax/do.php b/syntax/do.php index 2f3530f..28f1d6d 100644 --- a/syntax/do.php +++ b/syntax/do.php @@ -159,6 +159,10 @@ public function render($mode, Doku_Renderer $R, $data) { // we don't care for QC FIXME we probably should ignore even more renderers if($mode == 'qc') return false; + if($mode === 'metadata') { + return true; + } + // augment current task with original creator info and old assignees $oldtask = $this->_oldTask($ID, $data['task']['md5']); if($oldtask) { @@ -167,10 +171,9 @@ public function render($mode, Doku_Renderer $R, $data) { $data['task']['status'] = $oldtask['status']; } - // save data to sqlite during meta data run - if($mode === 'metadata') { + // save data to sqlite during xhtml run + if($mode === 'xhtml') { $this->_save($data); - return true; } // show simple task with status icon for export renderers