> Whoa, slow down.  Does your new installation work?  When you follow the
> exact instructions in the INSTALL file under "Testing your 
> Installation", do you get the expected results?
Actually I am not so fast, as you see.. All the steps mentioned above
are passed successfully. No wonder, because I've used to install
SMW0.6 and SMW0.7 previousely, and the later one runs fine on my site.

> Since you're having problems with categories (see later), try making a
> few nested subcategories and doing queries on them.

> I don't know if the old backups are compatible.  With each SMW and
> MediaWiki update I made a backup but I made the upgrade in-place and ran
> the updates scripts and SMWAdmin with no incident, so I never had to try
> the backups.
Yes, I've executed SMWAdmin before the XML restore. It worked fine. I
do not trust upgrade scripts, I feel they are more vulnerable to bugs
comparing to XML backups.

>    Error in fetchObject(): Table 'yarsu.cats4' doesn't exist (127.0.0.1)

> I think "catNNN" are temporary tables that SMW creates in 
> getCategoryTable() when it makes "a (temporary) table that contains the
> lower closure of the given category wrt. the category table."  I'm not
> sure why it's failing.  It could be a database-level problem, such as a
> permissions issue.
Database permissions are  SELECT, INSERT, UPDATE, DELETE, CREATE, ALTER, LOCK 
TABLES
These were enough for SMW 0.7. And yes, I've restored the XML backups
with older versions. Though, I realize that the difference between 0.7
and 1.0 is much wider.


> What PHP and MySQL versions are you running?
PHP 5.2.4 and MySQL 5.0.45, accordingly. Works with MW 1.10/SMW 0.7
just fine. When I've used to install 1.93/SMW 0.6 some time ago, I've
had a major screwup with mysql RPM, which installed by default with
charset settings ISOsomething instead of unicode. Since then, I
implicitely specify UTF8 as default charset.

> In the failures you attached, the MediaWiki import script is parsing the
> XML of a page that apparently has an <ask> inline query in it, so it's
> calling smwfProcessInlineQuery()

> Can you try making a simple query for a category from Special:Ask?  E.g.
> [[Help:+]]
Can't right now, see below the explanation why..

> I guess you could try removing the inline query (search for ask) from
> the XML file and try reimporting.
> It's the inline queries for category that seem to be causing grief, so I
> think you should focus on removing those first.
Yes, I've removed all the ask queries and it imported just fine.

> I think you can and should run the SMW_unifyProperties.php maintenance
> script after import.
I've changed the namespace names to <page>Property:Propertyname</page>
manually inside the dump... Another advantage of using the dump :-)

> I think that must be a table produced by something.  SMW doesn't use
> class="tbl...".  So maybe you have some other extension or template 
> that's generating tables.
I've not realized that tags were quoted so <div was encoded as
&lt;div. So it was my div, but I was unable to find it :-)
It was used inside the template, used by <ask format="template" ...>

> I hope these guesses help.
> --
Thanks for the help.

I guess there are more permissions needed by SMW 1.0RC2 comparing to
SMW 0.7. I've added CREATE TEMPORARY TABLES to mysql priviledges and
now it imported the rest of the dump just fine, too. But, I wasn't
happy for a long time. An attemnt of executing Special:Ask page
results with httpd consuming 99% of CPU infinitely, until I shutdown
it and restart :-( Will investigate further tomorrow...

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