> Did you ever run SMW_refreshData after the import?
Of course not. That's because I am using XML import instead of
standard way described in INSTALL, and also I believe that moving from
SMW 0.6 to SMW 0.7 had filled smw_attributes properly during the XML
import (though it was many months ago, so I can't remember for sure).

> Plain import does probably bypass SMW's (save) hooks, so that this
> last part would be needed (twice, as described in INSTALL).
It's really strange - because XML export/import scrpts do include
LocalSettings.php, where the extensions are included. And these
extensions obviousely setup their hooks there.

But it seems that you're right - re-installing everything again,
importing XML dump and performing SMW_refreshData twice did fill the
smw_attributes table..

It's extremly disappointing and frustrating and also a sign of bad
design that MW does not call extension hooks during the XML import :-(

> SMW's tables are completely determined by the page contents of your wiki, and
> so they do not need to be imported or backuped. If they cannot be rebuilt via
> SMW_refreshData, then normal editing in the wiki would also not fill them
> properly (which is possible, but not related to the import itself).
No, I am not going to re-save hundreds of pages, of course. And of
course I do realize that SMW needs to extract and store it's data via
the hook during the page save. It's an MW's XML import that really
frustrates me...
Dmitriy


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel

Reply via email to