billsaysthis

1.1.2 no longer throws those errors but I’m not sure the index building is doing the right thing. I have zero posts and about a dozen pages (none of which has all that much text) but 20 minutes after clicking the build index button the Options page is still blank.

Fixing that by removing the if test (since I know I have later than 2.8dev) I get another error:

Plugin could not be activated because it triggered a fatal error.

$stopwords = array( “a”, “about”, “above”, “above”, “across”, “after”, “afterwards”, “again”, “against”, “all”, “almost”, “alone”, “along”, “already”, “also”, “although”, “always”, “am”, “among”, “amongst”, “amoungst”, “amount”, “an”, “and”, “another”, “any”, “anyhow”, “anyone”, “anything”, “anyway”, “anywhere”, “are”, “around”, “as”, “at”, “back”, “be”, “became”, “because”, “become”, “becomes”, “becoming”, “been”, “before”, “beforehand”, “behind”, “being”, “below”, “beside”, “besides”, “between”, “beyond”, “bill”, “both”, “bottom”, “but”, “by”, “call”, “can”, “cannot”, “cant”, “co”, “con”, “could”, “couldnt”, “cry”, “de”, “describe”, “detail”, “do”, “done”, “down”, “due”, “during”, “each”, “eg”, “eight”, “either”, “eleven”, “else”, “elsewhere”, “empty”, “enough”, “etc”, “even”, “ever”, “every”, “everyone”, “everything”, “everywhere”, “except”, “few”, “fifteen”, “fify”, “fill”, “find”, “fire”, “first”, “five”, “for”, “former”, “formerly”, “forty”, “found”, “four”, “from”, “front”, “full”, “further”, “get”, “give”, “go”, “had”, “has”, “hasnt”, “have”, “he”, “hence”, “her”, “here”, “hereafter”, “hereby”, “herein”, “hereupon”, “hers”, “herself”, “him”, “himself”, “his”, “how”, “however”, “hundred”, “ie”, “if”, “in”, “inc”, “indeed”, “interest”, “into”, “is”, “it”, “its”, “itself”, “keep”, “last”, “latter”, “latterly”, “least”, “less”, “ltd”, “made”, “many”, “may”, “me”, “meanwhile”, “might”, “mill”, “mine”, “more”, “moreover”, “most”, “mostly”, “move”, “much”, “must”, “my”, “myself”, “name”, “namely”, “neither”, “never”, “nevertheless”, “next”, “nine”, “no”, “nobody”, “none”, “noone”, “nor”, “not”, “nothing”, “now”, “nowhere”, “of”, “off”, “often”, “on”, “once”, “one”, “only”, “onto”, “or”, “other”, “others”, “otherwise”, “our”, “ours”, “ourselves”, “out”, “over”, “own”, “part”, “per”, “perhaps”, “please”, “put”, “rather”, “re”, “same”, “see”, “seem”, “seemed”, “seeming”, “seems”, “serious”, “several”, “she”, “should”, “show”, “side”, “since”, “sincere”, “six”, “sixty”, “so”, “some”, “somehow”, “someone”, “something”, “sometime”, “sometimes”, “somewhere”, “still”, “such”, “system”, “take”, “ten”, “than”, “that”, “the”, “their”, “them”, “themselves”, “then”, “thence”, “there”, “thereafter”, “thereby”, “therefore”, “therein”, “thereupon”, “these”, “they”, “thickv”, “thin”, “third”, “this”, “those”, “though”, “three”, “through”, “throughout”, “thru”, “thus”, “to”, “together”, “too”, “top”, “toward”, “towards”, “twelve”, “twenty”, “two”, “un”, “under”, “until”, “up”, “upon”, “us”, “very”, “via”, “was”, “we”, “well”, “were”, “what”, “whatever”, “when”, “whence”, “whenever”, “where”, “whereafter”, “whereas”, “whereby”, “wherein”, “whereupon”, “wherever”, “whether”, “which”, “while”, “whither”, “who”, “whoever”, “whole”, “whom”, “whose”, “why”, “will”, “with”, “within”, “without”, “would”, “yet”, “you”, “your”, “yours”, “yourself”, “yourselves”, “the” ); ?>

Uh oh. Using WP 2.8 I get the following error on activation:

Plugin could not be activated because it triggered a fatal error.

Parse error: parse error in C:\Program Files\EasyPHP 3.0\www\wp\wp-content\plugins\relevanssi\relevanssi.php on line 452

Terrific! I’ll give it a go.

Except that WordPress is released as GPL and, as the recent WP Developmnt blog post points out, this carries into (infects, some people say) certain related software. IANAL and so I won’t go into whether plugins are covered by this requirement but to blithely say they are not is not a good way to end this thread :).

Okay, weird, I don’t now what I did but this problem cleared up. As far as I know the only action I took was to update a static page that serves as a table of contents entry point with the two categories I just added. So never mind ??

Ryan, the patched file didn’t work for me. Firefox is giving me this error message: “Firefox has detected that the server is redirecting the request for this address in a way that will never complete.” I never get to see the live WP page, though the Admin stuff works fine.

I figured out a workaround…

They also want to have reviews loaded in, and since I have a movie review blog it would be one more way to find readers.

However, since its based on the GData API I think this is worthwhile as it will, in the not very long run, be the main way to interact with most of their services. Already Calendar and Blogger use it.

In which WP field do you want to store this information?

I did recheck after noticing, moshu. All the files had the 2.0.3 sizes and dates. But I just redid the upgrade and the problem went away. Weird but probably my fault.

Guys I appreciate the responses but as I mentioned twice before I did delete the old files before uploading so I don’t see how the particular problem you mentioned could be the problem and even so the version would be reported as 2.0.2, not 2.0.

Looking at the file you named, it says:

$wp_version = ‘2.0’;
$wp_db_version = 3308;

Weird, eh?

My header.php has the normal bloginfo(‘version’) call, so I’m assuming that for some reason the update script didn’t change the db field. My question is why not and is this indicative of something else wrong, though there’s nothing visible.

Right, but I was using 2.0.2 before yesterday and updated by deleting the entire folders, not overwriting them. So even if there was an issue with the updated files not being FTPed the version number should be 2.0.2 and not 2.0.

Handy, thanks for the response. However, I was referring to my company’s blog (https://blog.rawsugar.com/blog) and not the personal one linked to my username here.