All checks were successful
		
		
	
	continuous-integration/drone/push Build is passing
				
			
		
			
				
	
	
		
			32 lines
		
	
	
	
		
			1.3 KiB
		
	
	
	
		
			Markdown
		
	
	
	
	
	
			
		
		
	
	
			32 lines
		
	
	
	
		
			1.3 KiB
		
	
	
	
		
			Markdown
		
	
	
	
	
	
| ---
 | |
| author: einar
 | |
| categories:
 | |
| - General
 | |
| comments: true
 | |
| date: "2008-05-04T07:35:07Z"
 | |
| slug: wordpress-snafu
 | |
| tags:
 | |
| - wordpress
 | |
| title: Wordpress SNAFU
 | |
| omit_header_text: true
 | |
| disable_share: true
 | |
| wordpress_id: 399
 | |
| ---
 | |
| 
 | |
| Yesterday I updated _[The S.T.E.A.L. Saga](http://www.stealsaga.net) _to Wordpress 2.5.1. I thought the upgrade would be painless, but I was wrong. First of all, the auto plugin updater kind of confused between the various plugins, so it marked some as updateable although they weren't. Then, some plugins (albeit incompatible), **disappeared** from the plugin list (the fix was downloading a more recent version).
 | |
| 
 | |
| The biggest issue was, however, the mangling of my .htaccess file due to a wrongly-generated permalink rule that was without a trailing slash (/). Such a badly done .htaccess would cause:
 | |
| 
 | |
| 
 | |
| 
 | |
| 	
 | |
|   * Problems when loading the pages
 | |
| 
 | |
| 	
 | |
|   * Problems with admin panels (no such page errors and the like)
 | |
| 
 | |
| 	
 | |
|   * Most importantly, it would cause an enormous load on the server (and with shared hosting, it _is_ a problem)
 | |
| 
 | |
| 
 | |
| It took me at least 30 minutes to find out what the cause was. Removing .htaccess did not help, I had to remove it then change the permalink to the default value, and then change it again. Now it works, but what a bother for a seemingly "simple" upgrade.
 |