muskie

Damn. I too am having problems involving comments and apparently the parsing of my comments.php file. When you try to view an individual posting which was borked under WordPress 2.0 you get the following error:

Parse error: parse error, unexpected T_ENDIF in /home/muskie/domains/muschamp.ca/public_html/blog/wp-content/themes/muschampTabs/comments.php on line 78

One side effect of this, is it messes up my .CSS I’m not sure style.css is getting loaded totally in Opear (my browser of choice) I get some formatting because my WordPress Theme is an extension of my main website so all the CSS inherrited from the main site is applied and it is contained in a file called muschampTabs.css I think. On my front page again at the very bottom of the page I get this error now:

Dave. [post_title] => Oh yeah, I ate frog [post_category] => 0 [post_excerpt] => [post_status] => publish [comment_status] => open [ping_status] => open [post_password] => [post_name] => oh-yeah-i-ate-frog [to_ping] => [pinged] => [post_modified] => 2006-02-01 08:14:48 [post_modified_gmt] => 2006-02-01 13:14:48 [post_content_filtered] => [post_parent] => 0 [guid] => https://blog.muschamp.ca/2006/02/06/oh-yeah-i-ate-frog/ [menu_order] => 0 [post_type] => [post_mime_type] => [comment_count] => 0 ) ) [queried_object] => [queried_object_id] => 0 )
SERVER

Array
(
[DOCUMENT_ROOT] => /home/muskie/domains/muschamp.ca/public_html/blog
[HTTP_ACCEPT] => text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
[HTTP_ACCEPT_CHARSET] => ISO-8859-1,utf-8;q=0.7,*;q=0.7
[HTTP_ACCEPT_ENCODING] => gzip,deflate
[HTTP_ACCEPT_LANGUAGE] => en-us,en;q=0.8,ja;q=0.5,zh-cn;q=0.3
[HTTP_CONNECTION] => keep-alive
[HTTP_COOKIE] => __utmz=217375882.1139048333.13.12.utmccn=(referral)|utmcsr=blog.muschamp.ca|utmcct=/|utmcmd=referral; MintPane1=1; MintAuth=3f56b079efd36da4e63ff364e0da8027; MintPane4=0; MintPane3=1; __utma=217375882.1392118245.1134811149.1138963284.1139048333.13; MintPane2=0; MintUnique=1; MintIgnore=true; wordpresspass_2f3cd5c3739319dd07d94510f13f9398=43ecaa3b277255605e18052510ad16d9; dbx-postmeta=grabit=3+,4+,5+,0-,1-,2-,6-&advancedstuff=0-,1-,2-; wordpressuser_2f3cd5c3739319dd07d94510f13f9398=admin; comment_author_url_2f3cd5c3739319dd07d94510f13f9398=http%3A%2F%2Fwww.muschamp.ca; comment_author_email_2f3cd5c3739319dd07d94510f13f9398=andrew%40muschamp.ca; __utmz=143861734.1134802966.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); __utma=143861734.373055463.1134802966.1138529892.1138533545.78; comment_author_2f3cd5c3739319dd07d94510f13f9398=Muskie
[HTTP_HOST] => blog.muschamp.ca
[HTTP_IF_MODIFIED_SINCE] => Sat, 11 Feb 2006 07:33:28 GMT
[HTTP_KEEP_ALIVE] => 300
[HTTP_REFERER] => https://blog.muschamp.ca/2005/10/31/baidu-chinas-search-engine/
[HTTP_USER_AGENT] => Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
[PATH] => /sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin
[REDIRECT_STATUS] => 200
[REDIRECT_URL] => /
[REMOTE_ADDR] => 61.149.142.124
[REMOTE_PORT] => 19913
[SCRIPT_FILENAME] => /home/muskie/domains/muschamp.ca/public_html/blog/index.php
[SERVER_ADDR] => 209.51.150.21
[SERVER_ADMIN] => [email protected]
[SERVER_NAME] => blog.muschamp.ca
[SERVER_PORT] => 80
[SERVER_SIGNATURE] =>
Apache/1.3.33 Server at blog.muschamp.ca Port 80

[SERVER_SOFTWARE] => Apache/1.3.33 (Unix) mod_ssl/2.8.22 OpenSSL/0.9.7a PHP/4.3.10 mod_perl/1.29 FrontPage/5.0.2.2510
[GATEWAY_INTERFACE] => CGI/1.1
[SERVER_PROTOCOL] => HTTP/1.1
[REQUEST_METHOD] => GET
[QUERY_STRING] =>
[REQUEST_URI] => /
[SCRIPT_NAME] => /index.php
[PATH_TRANSLATED] => /home/muskie/domains/muschamp.ca/public_html/blog/index.php
[PHP_SELF] => /index.php
[argv] => Array
(
)

[argc] => 0
)

REQUEST

Array
(
[__utmz] => 143861734.1134802966.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none)
[MintPane1] => 1
[MintAuth] => 3f56b079efd36da4e63ff364e0da8027
[MintPane4] => 0
[MintPane3] => 1
[__utma] => 143861734.373055463.1134802966.1138529892.1138533545.78
[MintPane2] => 0
[MintUnique] => 1
[MintIgnore] => true
[wordpresspass_2f3cd5c3739319dd07d94510f13f9398] => 43ecaa3b277255605e18052510ad16d9
[dbx-postmeta] => grabit=3 ,4 ,5 ,0-,1-,2-,6-&advancedstuff=0-,1-,2-
[wordpressuser_2f3cd5c3739319dd07d94510f13f9398] => admin
[comment_author_url_2f3cd5c3739319dd07d94510f13f9398] => https://www.muschamp.ca
[comment_author_email_2f3cd5c3739319dd07d94510f13f9398] => [email protected]
[comment_author_2f3cd5c3739319dd07d94510f13f9398] => Muskie
)

–>

It used to have less crap, I would hyptothesize that my friend Dave tried to leave a comment about me eating frog. I never got an email confirming this comment. I’m using 2.0.1 and Ir ecently started using Spam Karma 2.0 I can totally live without it, but if I disable all my plugins my theme starts to look ugly in the sidebar. Note on my main page I get a white background which means that style.css loaded more completely.

Any suggestions. I have limited time, limited patience, and limited internet access being on my last six days in China. I just want to update my blog so I can take over the world or at least the search engine results. when I get back to Canada I’ll fix this, but the errors are getting bigger and uglier so I thought I’d post something.

https://blog.muschamp.ca/

Try any single post you want, the older the better I guess to see the first error.

Muskie

Hoozah! That did it. Now I’m sure to completely dominate Google and then the world…

Or at the very least I won’t look so incompetent with so many busted links. Here is a working permalink:

https://blog.muschamp.ca/2006/01/18/guns-germs-steel-koreans-calves-and-civilization-iii/

Note the date is last month so it is well off my front page.

Cheers,

Muskie

I’ve upgraded to WordPress 2.0.1 or at least I tried very very hard to. The internet connection is so dodgy I had to babysit my ftp program for over an hour. I ended up using a cleaner install rather than syncing.

My permalinks still don’t work nor does the date based navigation such as the previous post link on the bottom of the front page. I now get a 404. It is a pretty 404 with all my navigation and even my sidebar on it, but it isn’t what I want. I will try regenerating my permalinks again to see if that helps.

If I hack my URL to include index.php it can display my old posts. This is all well and fine but I got hundred of posts with links using my old permalinks with index.php. Surely I don’t need ‘index.php’ other blogs don’t.

https://blog.muschamp.ca/index.php/2006/01/03/dance-dance-dance/

Muskie

I went to a custom permalink as suggested by somebody somewhere starting with index.php/yadda/yadda/yadda/ and it works for the generated links, but the links inside my posts where I cut and pasted the old permalinks as static HTML links still don’t work. Plus this changed my permalinks to be something like https://blog.muschamp.ca/index.php/2005/12/05/something-or-other/ and that is no good.

I even tried to downgrade but that script doesn’t seem to work for me. I swear nothing works for me anymore.

Muskie

I’ve tried all the stuff in the posting and other suggestions and my permalinks don’t work. I was using option 2 under WordPress 1.5.2 I guess. I also use a subdirectory https://blog.muschamp.ca

I often linked to my old posts from my newer posts, none of these links work. I don’t get a 404, I just get the default front page with a different URI in the browser window.

Any suggestions?

Muskie

I’ve tried it with and without the BEGIN # WordPress stuff and using the second option and the custom option which for me now is the second option and nothing has worked. I’ve regenerated my permalinks multiple times, I’ve tried Firefox and Opera, still no love.

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php
</IfModule>
# END WordPress

That is my current WordPress generated .htaccess file with the # BEGIN and # END additions

Nooo. I did that, it didn’t recreate the file, but I cut and pasted in the text it generated and upload it and it didn’t change anything. I click on a link to an old posting and it changes the URL but it just reloads my main blog page, the most recent 10 postings. That is only thing anyone can read right now, unless they can edit old posts through admin which only I can.

Muskie

Decent, I think this might be it, I had to do something like this before. The other huge issue for me is I’m in China and am reliant on WiFi so I don’t have the internet access you want. Anything that takes over 15 minutes is hard to find time for, just keeping up on email and updating my blog is weekly struggle. I spend a lot on various foods and drinks just to use the internet.

Muskie

Anyone Beuler?

My blog has been blatantly busted ever since I upgraded that has been several days now…

Muskie

Could it be do to the .htaccess file? The permalink structure is correct, WordPress has taken it upon itself to change it from custom to choice 2 (Date and name base). The one on the server has this:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php
</IfModule>

# END WordPress

I think that is what it has always have, the one that came with the distribution is blank… Any suggestions?

PS Note I use a subdomain this cause lots of problems at first, but everything was working prior to upgrading to 2.0

I changed the permalinks to be customer /year/month/day/title/ which was option number three. This didn’t seem to fix the problem. My website/blog is https://blog.muschamp.ca/ I’m giving up for the day.

Muskie

I too am experiencing this. I just upgraded to WordPress 2.0 My links now no longer work, I don’t get an error, I just get the main page reloaded. This happens when I try to post a comment too.

I looked at the options it has the third one down selected for Permalinks for me, this is Date plus title. I think I used a pretty standard permalink before, I certainly didn’t change it, but the intall may have… I’ll look at an old posting and see what permalink style I was using from inside the Admin interface.

I tried that, but I’m on a Mac so I can’t see IE on Windows. I tried using IE 5.2 for Mac OS X as a proxy but I couldn’t quickly get it to work. This is what I have now:


#blogContent
{
padding: 0px;
margin: 0px;
width: 69%;
float: left;
}



#sidebar
{
width: 27%;
margin-left: 71%;
padding: 4px;
}


The padding shouldn’t affect it in a correctly working box model. 27 + 69 is well under a 100 now so there is plenty of fudge factor. I made the left margin bigger to try and creat a gap, no dice. I don’t know if it will even render correctly in IE 5.2 on the Mac so I will give up until I can get a windows machine to work side by side. I already asked a classmate to do this for me, maybe tomorrow.

Muskie

Wow a lot of responses. I’ve been busy and ah… distracted…

BoInG I know my problem comes from a float: left. I followed the Urban Giraffe tutorial to a degree, but mainly I relied on my past experience and trial and error. I’ve actually added in a bunch of plugins and visual nicities, but I haven’t fixed the problem in IE.

This is how things are:

#blogContent
{
padding: 0px;
margin: 0px;
width: 70%;
float: left;
}


and here is the sidebar:

#sidebar
{
width: 28%;
margin-left: 70%;
padding: 4px;
}


Of course there is a lot of other things going on, getting all the tabs at the top working and the logo was largely the work of another, but I’ve heavily modified his original sample code and will continue to do so. I added gravatars and borders around some images, but I still have to upload a lot of fixes to the static stuff. Many, many, many things to do, so little motivation.

Thanks for the help.

Muskie