muskie

I tried to make changes, I had to do some fiddling with my Subversion client, that might be the issue. Here is the error I got:

Commit failed (details follow):
access to ‘/!svn/ver/397556/simple-random-quotation/trunk/readme.txt’ forbidden

This should be the changes required:

Requires at least: 2.2.0
Tested up to: 3.2.1
Stable tag: 3.1

I remember submitting it. I had to get the rights to access some code repository. I even got a special app just to use that system. I’m not sure where it went, but I couldn’t find it by searching keywords or through my account once I reset my password. I should be able to re-upload it easy enough, but it seems to me the bigger the WordPress codebase has got, the less well it has worked, see my conditionals difficulties. That has persisted through so many updates and it isn’t consistent, some updates change the behavior, but it never behaves as per the documentation.

I ended up writing little printfs to prove I wasn’t crazy.

Thanks, I think it should work better now. Though I think my blog is running slower, I installed Page.li too. What the real problem is the is_front_page and similar conditionals always return true. I’ve had this problem before and my modular sidebar becomes not so modular…

I upgraded to WordPress 3.1.1 and this had no effect. It did fix my category archives and the sidebar conditionals issues I’ve been having on and off for several versions, apparently Simple Tags and Taxonomy are also affected by this bug, which is hopefully squashed.

Yet Another Related Post Plugin still stops DISQUS from working when I activate it and it appears the two are mutually exclusive at this time, you can’t run both.

Any thoughts?

I seem to have gotten rid of this but all my Chinese Characters and Japanese Characters were turned to gibberish. So I’m running some plugin I used in my quest to fix this last time, though I may just restore a backup of the database…

Why does this happen when I update manually, the automatic update didn’t do this. Furthermore my manual update it said the database was already up to date. Which it should have been. I don’t understand where this problem keeps coming from.

So I did a manual upgrade and the conditionals started working correctly but when I added plugins and now, pretty much every admin page throws this error and my install is useless”

Warning: Cannot modify header information – headers already sent by (output started at /home/muskie/domains/muschamp.ca/public_html/blog/wp-config.php:1) in /home/muskie/domains/muschamp.ca/public_html/blog/wp-includes/pluggable.php on line 890

I didn’t accidently blow away my wp-config.php or anything it was unchanged, I looked at what was there in the sample and added the missing arguments and it didn’t help. I’m going have to try deleting all the plugins and see if it is one of them. The first one I activated was Simple Tags and it through this error too.

Turning off Simple Tags doesn’t changes this, why are these conditionals returning weird results?

No help huh?

I wrote this and stuck it in my sidebar.php

<?php if (is_home())
			{
			echo 'is_home' ;
			}
		?>
		<?php if (is_front_page())
			{
			echo 'is_front_page' ;
			}
		?>
		<?php if (is_single())
			{
			echo 'is_single' ;
			}
		?>
		<?php if (is_category())
			{
			echo 'is_category' ;
			}
		?>
		<?php if (is_tag())
			{
			echo 'is_tag' ;
			}
		?>
		<?php if (is_date())
			{
			echo 'is_date' ;
			}
		?>
		<?php if (is_archive())
			{
			echo 'is_archive' ;
			}
		?>

For the following URL’s this is what is echo’ed on the screen:
https://blog.muschamp.ca/ is_home
https://blog.muschamp.ca/2010/09/07/now-running-wordpress-3-0-1/ is_home
This makes no sense either!
https://blog.muschamp.ca/2010/09/06/ is_date is_archive
Which makes sense, the next one is OK too
https://blog.muschamp.ca/category/internet/online-social-networks/ is_category is_archive

https://blog.muschamp.ca/tag/cambodia/ is_date is_archive

WTF. Why is a single post returning true for is_home, how come tags return true for is_date? and none of my posts or archives return true for :
is_front_page
is_single
is_tag

I left the debugging code in, but what can I do when it thinks single posts are my home page and my tag archives are date archives. I’ll try de-activating Simple Tags plugin.

This is dogging me too:

Warning: Cannot modify header information – headers already sent by (output started at /home/muskie/domains/muschamp.ca/public_html/blog/wp-config.php:1) in /home/muskie/domains/muschamp.ca/public_html/blog/wp-includes/pluggable.php on line 850

I had it fixed to displaying Chinese, but then it said my database was out of date so it upgrade it. Now I’m not sure… I’m thinking of doing a clean install of 2.7.1 I think I had that working before I upgraded…

Apparently Apache didn’t like it when I made directories 777, alas I just want my blog to work the way it did before I upgraded. Apparently testing with multi-lingual blogs wasn’t very extensive as I still have gibberish instead of Chinese…

I thought I set all the tables back to UTF8 and re-imported using the import button, but it never let me pick a file, it just had this System Error 500 hissy fit…

Try try again…

Wors now I don’t have a blog at all…
Just a 500 error…

Still not fixed, tried to import using WordPress all my comments and categories, before I was getting error about directory not being writeable by server so I went to 777 temporarily and got this:

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, [email protected] and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.

I will contact my webhost, but I still have gibberish instead of Chinese…

Trying to follow instructions on this page:

https://alexking.org/blog/2008/03/06/mysql-latin1-utf8-conversion

I now have no way to access phpMyAdmin after getting the right combination of latin1 and utf8 tables…

I tried a test post with Chinese and Japanese characters in it. It turned them into question marks. Then I tried a comment with Chinese and Japanese characters and it through an error. Who tested 2.9.1?

WordPress database error: [Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation ‘=’]
SELECT comment_ID FROM wp_comments WHERE comment_post_ID = ‘1424’ AND comment_approved != ‘trash’ AND ( comment_author = ‘Muskie’ OR comment_author_email = ‘[email protected]’ ) AND comment_content = ‘It turned my Chinese and Japanese into question marks. WTF? I know WordPress supports Japanese and I know it used to let me use Chinese too. I even had Korean somewhere on my blog. Not a happy camper right now. 美女おっぱい’ LIMIT 1

Warning: Cannot modify header information – headers already sent by (output started at /home/muskie/domains/muschamp.ca/public_html/blog/wp-includes/wp-db.php:615) in /home/muskie/domains/muschamp.ca/public_html/blog/wp-includes/pluggable.php on line 868

I never changed the encoding of my database and I used to be able to use both languages in one post. Do I have to fix my theme too? I shouldn’t have upgraded, it causes more trouble than it is worth. How am I going to get all my Asian content back if I can’t import it. Blow away the database, I don’t have a database dump other than the one I did from the WordPress Export…

Here is what I got when I tried to import my stuff from my previous version. I keep all my pictures in a Picture directory with a year so 2010 is /Pictures/2010

Not sure what it is trying to do other than it failed:

Before you can upload your import file, you will need to fix the following error:

Unable to create directory /Pictures//2010/01. Is its parent directory writable by the server?

Howdy! Upload your WordPress eXtended RSS (WXR) file and we’ll import the posts, pages, comments, custom fields, categories, and tags into this blog.

Choose a WordPress WXR file to upload, then click Upload file and import.

Warning: is_dir() [function.is-dir]: open_basedir restriction in effect. File(/) is not within the allowed path(s): (/home/muskie/:/tmp/) in /home/muskie/domains/muschamp.ca/public_html/blog/wp-includes/functions.php on line 1948

Warning: file_exists() [function.file-exists]: open_basedir restriction in effect. File(/) is not within the allowed path(s): (/home/muskie/:/tmp/) in /home/muskie/domains/muschamp.ca/public_html/blog/wp-includes/functions.php on line 1939

Warning: is_dir() [function.is-dir]: open_basedir restriction in effect. File(/) is not within the allowed path(s): (/home/muskie/:/tmp/) in /home/muskie/domains/muschamp.ca/public_html/blog/wp-includes/functions.php on line 1948

I’ll look a little closer at the directory permisions… But surely if you are just restoring the database content it shouldn’t matter the path to my images…