billsaysthis

Holy schmolies, that was it. I missed the Rewrite base at the top of the file, fixed now.

Muchas gracias, amigo!

I used an SFTP client (Transmit) and moved the entire contents of the blog folder to my root. In fact I had to explicitly confirm that overwriting .htaccess was okay.

Additional info: If I leave the default permalink (?p=post_id, ?m=month) the post and archive links work correctly. Other blogs still fubar’ed though.

I did this as best I could figure. The main page of the main (first created, shows at root) blog shows properly, all other pages on this and the other blogs get 500 errors.

I updated wp-config.php plus these tables:

• wp_site
• wp_blogs
• wp_N_options (where N is nil for root blog and 2, 3 and 4 for the others)
• wp_sitemeta (siteurl)

Uggh!

There wasn’t an actual WPMU doc, just some forum posts, and they suggested doing what you did. I just don’t want to do that unless that’s the ‘official’ instruction.

That convertor is great if your Blogger export file is less than 2MB. As mine is about 9MB it chokes and fails.

Anyone have another solution?

Having the same issue, even after changing the blogger.php as suggested above.

I don’t get the array error with 1.3.3 but searching on the word I described above (deleted from the common words list) returns zero results, is this the expected?

Also, the default name for the query term highlight CSS class, search-results, is also the name used for the body class in search.php. I changed mine to search-query-term in the settings page but perhaps you should choose a default name that’s in the Relevanssi ‘namespace’ such as rlv-query-term or similar?

Updated to 1.3.2, thanks!

Getting this error searching on a term which WAS in the common terms list and which I deleted (that is, clicked the red circle next to it):

Warning: array_keys() [function.array-keys]: The first argument should be an array in C:\Program Files\EasyPHP 3.0\www\wp\wp-content\plugins\relevanssi\relevanssi.php on line 260

Sorry, I didn’t notice the dropdown box for choosing the highlight.

Enjoy the vacation! I’ll look forward to this when you have the chance to update.

Note that I agree a class is best, but I think the span is also necessary, otherwise (and I may misunderstand you here, and you already agree with me) what is the span applied to?

Very nice change! One small tweak I would appreciate is wrapping the search term in a span with a specific class (e.g. <span class="actual-search-term">example</span> so it can be styled to match our site.

Thanks much! When this site is published I will let you know so you can point to it as an English language example (if you wish, I’m just responding to the plugin page note about wanting some).

Also, is there a means to make the search results show an except that includes the text which caused the result to be included rather than the default first 55 characters?

Ok, maybe I was too fast to post that last comment ??

I refreshed the options page, clicked the Continue Indexing button and it finished a few seconds later.

However I would suggest adding some sort of Ajax progress indicator, if only to show that work is actually being done.