ponolan

I’m running 3.3.3 on WordPress 3.2.1 with MistyLook 3.7.2. I noticed recently (haven’t been blogging for a while) that YARP had stopped working. I’ve no idea when it broke, sorry.

Yesterday I fixed a lot of broken links (about 80). Then, rather unexpectedly, YARP was working this morning. I then edited a post and saved it and, presto, no more related posts (nothing displayed, as if the plugin was not installed). Back to the status quo ante.

PHP is 5.2.14
MySQL is 5.1.54

Match threshold is 2, changing it to 1 doesn’t change anything. Results are displayed automatically. I will email a screen grab of the options.

clephro, sorry for any confusion, by “elsewhere” I meant on your PC so you could just FTP the files… not another site.

In case this helps with any debugging:

Trying to use the Sept 28 version of 3.0 I get:

Error loading stylesheet: A network error occured loading an XSLT stylesheet:https://mydomain/wp-content/plugins/sitemap.xsl

The plug-in is installed at /public_html/wp-content/plugins/google-sitemap-generator.

the sitemap.xml file is generated ok and placed in the root directory of the blog where it should be findable with https://domain/sitemap.xml

At first I thought I needed to make a change to .htaccess but after changing the default location for the XSL file to

domain/wp-content/plugins/google-sitemap-generator/sitemap.xsl

I was able to see a sitemap at this address https://domain/sitemap.xml

The file contents are updated but the datestamp is unchanged. There was a problem notifying Google, Yahoo and Ask. Since the files are being built ok I’m not sure if the debug function will shed any additional light.

As a footnote to the above I also ran into this PHP error, just in case anyone else runs into it. I gather that wamp packages with older versions of PHP (5.1) don’t have the problem.

I also had a problem like this. My old permalink was date and name based (https://domain/year/month/day/post) and after I imported the exported db into a local installation I got errors and the data and name based option reads

(*) https://domain/index.php/year/month/day/sample-post

where year=2007 etc.

I used a custom structure to correct it. Editing the options table via https://domain/wp-admin/options.php doesn’t resolve the problem.

I’ve no idea what’s wrong but all I want to for now is test changes on an offline copy, as well as having a backup.

Did you delete it before it was backed up? If your hosting service backs up up files at night it may be possible to get (and pay for) a restore. Otherwise you need to create a new installation elsewhere and copy the files, plus anything you uploaded (images, plugins, themes). If it’s a brand new installation it may be easier to just delete everything and start again.

I also made the same mistake (got interrupted and resumed, forgetting to disable plugins). You have to wonder how hard it would be for the upgrade process to do this or check that it had been done and if not to abort with an error message.

The actions required to recover are beyond what many are comfortable with or know how to manage.

I decided to finally do what I had planned for a long time, which was to set up a local copy of my blog and restore the last backup there, upgrade that and then compare the databases. This allowed me to identify some tables I could delete and, in the end, all was well. However, the process of installing a local copy (first on Vista, then XP) was unbelievable.

See https://www.wowwebdesigns.com/wowbb/forum12/1820.html
and the post from jedhunsaker, e.g. The problems have not been fixed.

In the end I

1. Edited my hosts file to tell my browser that my blogs domain was at 127.0.0.1 (same machine)

2. Used wampserver (https://www.wampserver.com/en/index.php) to install all the components (on XP) needed to host the blog and get it working immediately with no need for messing around with problems like that indicated above (i.e., Apache, MySQL, PHP).

3. Configured Apache to use a directory of the same name as the server hosting the blog.

I already use Webdrive from SouthRiver Technologies (an upgraded version of a tool called netdrive that can be found for free, here: and Beyond Compare from Scooter Software.

In future, I’ll do my upgrades locally first, as I should have done all along.

I was fully backed up and don’t mind in the end having been forced to do something I had planned but I am dismayed that an upgrade should break so trivially.

What I’d like to do now is have a way of posting locally and, when I’m ready, syncing the changes.

OK, I solved it. You’re right. I’d already added index.php to the list of default pages but it didn’t stick for some reason. Works ok now. Am just running WP on a PC, not a server. That will be later. For now am just getting familiar with it. Thanks

An update on this: I have found that the problem is that dirpath\index.php is not being displayed. If I click on the file manually (in the blog or wp-admin directory) all is well.

I am using Windows Vista Ultimate, MySQL 5.0.37, MySQL Administrator 1.2.10, PhpMyAdmin 2.10.0.2 and IIS 7.0.

Presumably I’ve done something wrong with IIS. Advice welcome still. Thanks.