CacCan
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Replacing corrupted WordPress filesAgain, I spoke too soon…
I have just discovered another undesirable side-effect of the Search Unleashed plug-in.
Clicking on a link in the list of Categories – e.g. WordPress (10) – returns a page that has more Post entries on it than the 10 that should be displayed.
This happens even after running a re-index in Search Unleashed.
Disable the plug-in and the correct Posts are shown for the Category that was clicked on.
Looks like I’ll be deleting this one.
Forum: Fixing WordPress
In reply to: Replacing corrupted WordPress filesYou were right — a plug-in again.
This time the culprit was Search Unleashed.
However forcing a manual re-index in the settings of Search Unleashed solved the problem.
Forum: Fixing WordPress
In reply to: Replacing corrupted WordPress filesIncidentally, I’ve just had a look with my FTP client and there is no /wordPress folder at http://blogname.com/blog/category/wordpress/.
Forum: Fixing WordPress
In reply to: Replacing corrupted WordPress filesLooks like I spoke too soon, as I just discovered an unpleasant side-effect.
I have WordPress configured to show Categories in one of the two sidebars.
It shows a list of category names just as I would expect, and each category name has a number after it in brackets indicating the number of posts for that category.
EXAMPLE: I have one category that shows in the list as “WordPress (10)”, and its link is http://blogname.com/blog/category/wordpress/.
PROBLEM: Clicking that category (or any other) in the list opens a new blog page which is headed with the category name (WordPress in this example), but there is no list of relevant posts/articles displayed on the page.
The exact same thing applies to the “Popular Tags” list (Tag Cloud), also in a sidebar.
Both lists are formed by the built-in Widgets.
Any idea what’s gone wrong and how to fix it?
Forum: Fixing WordPress
In reply to: Replacing corrupted WordPress filesWell, I don’t know what to make of this.
I decided to tackle plug-ins first because that seemed to be the easiest path to take. I had a lot of deactivated plug-ins, so the first thing I did was delete all those. Then I bulk deactivated all of the remaining plug-ins.
Much to my surprise (because I really didn’t think a plug-in could be causing the problem) I was now able to add new posts!
So then I activated all the plug-ins again in batches of three or four at a time, testing after each activation.
Eventually all plug-ins were activated again and I could still add new posts. In other words, all the same plug-ins activated again and the problem has disappeared.
What do you make of that?
Forum: Installing WordPress
In reply to: Moving from Windows to Linux/ApacheOops!
Thanks for the try guys, but I just realized that Windows Servers don’t have a public_html folder.
I had to drop this matter for a while to go put out some fires elsewhere. Just came back to this and when I inspected the original blog location (Windows 2008 Server) with my FTP program it hit me straight away that there was no public_html folder to copy.
WordPress was installed into a folder called /blog off the root (wwwroot) of the Windows server.
Also, Windows does not use an .htaccess file.
Anyone got any more information specifically on moving a WordPress installation from a Windows 2000 server to a Linux/Apache server?
Forum: Fixing WordPress
In reply to: Replacing corrupted WordPress filesBy the way, I can EDIT existing posts.
Forum: Fixing WordPress
In reply to: Replacing corrupted WordPress filesAlso…
Obviously before I do anything else I need to do a backup.
Is WP-DBManager a good choice for that task?
Forum: Installing WordPress
In reply to: Moving from Windows to Linux/ApacheHi ipstenu.
So what do you suggest should be the procedure? Here’s my guess based on your reply…
1. Backup the database from the original installation and download to local PC.
2. Copy public_HTML folder from original installation to local PC.
3. Install WordPress on the Linux/Apache server.
4. Copy all of the original public_HTML folder to the Linux server.
5. Import the database backup to the new installation on the Linux server.Close?