rdsmes
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: 404 after save or publish a postThe problem also appears to be related to the ‘save and continue editing’ feature. Start a new post – halfway through, hit ‘save and continue editing’. That returns you to the post. Finish the post – hit ‘save’. Bang – 404.
Maybe that’s why some of you are seeing it with ‘longer’ posts – do you use ‘save and continue editing’?? I use it a lot, just out of a paranoid habit.
More digging required…
Forum: Fixing WordPress
In reply to: 404 after save or publish a postFor what it’s worth, I had a particular post that was being stubborn and giving me the 404 error each time I saved it, and was able to glean a little info from seeding the ‘post.php’ file with a few ‘error_log’ statements and seeing what popped up in the php error log.
The problem seems to result from the ‘$location’ for redirection in post.php being set incorrectly (duh). In this case, the path being taken through the post.php file went through the ‘editpost’ action/case, and $location was set by the
elseif (isset($_POST['referredby']) && $_POST['referredby'] != $_SERVER['HTTP_REFERER'])
{
$location = $_POST['referredby'];lines in that case (line 113-114). The location was NOT then altered by the following if statement and get_permalink () call.
You can’t tell this from the resulting address in the browser after the failure, but the entire $location seems to be set to:
<div id='error'> <p class='wpdberror'><strong>WordPress database error:</strong> [You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near ') ORDER BY post_id, meta_key' at line 1] <code>SELECT post_id, meta_key, meta_value FROM wp_postmeta WHERE post_id IN() ORDER BY post_id, meta_key</code>
</div>http://www.whateveryourblogis.com/wp-admin/post.phpThat’s the only info I’ve gotten so far – it would seem that the problem, at least in this case, was tied to that line of
$location = $_POST['referredby']on line 114 of post.php.At least that’s what my simple debug would indicate. I’m not sure where that error info comes from, or if ‘referredby’ just happens to be garbage at that point. Maybe that info from the incorrect $location will ring a bell with somebody.
Forum: Your WordPress
In reply to: Bear Mountain BullMoshu,
Thanks very much for catching the problem – and verifying the fix!Forum: Your WordPress
In reply to: Bear Mountain BullI think I fixed the IE 5.5 problem. Apparently the 5.5 CSS parser didn’t like the location of a particular comment in the CSS file.
Forum: Your WordPress
In reply to: Bear Mountain BullBeel,
It does appear that Moshu is correct – under IE5.5 SP2, the posts actually show up with a green background and white text. Thanks to Moshu for bringing it to my attention – I haven’t dug into fixing it yet, but I assume it’s some sort of CSS issue in IE5.x. I just need to find the appropriate workaround.
Now, for anyone interested in checking their sites with older versions of IE, the folk(s)at Skyzyx.com have done the web world a tremendous service by providing downloads for ‘standalone’ versions of Internet Explorer (check out http://www.skyzyx.com/downloads/ and scroll down to “Standalone Internet Explorer”. Download the zip file, unzip it into its own directory, and run the iexplore.exe file in that directory and BAM – you’re running the old version of IE. I did that with 5.5, and confirmed what Moshu reported.
One note: I had to do what was suggested in Comment #113 on that site, and that was to rename the .EXE file and its associated .local file so that IE5.5 came up instead of IE6.0. But it worked! (and exposed the problem…) And its a real easy way to check out your site with older versions…Forum: Your WordPress
In reply to: Bear Mountain BullMoshu,
I believe you. A while ago, before I really got my site running, I ran across a page (probably referred to from the WP forums somewhere!) that would generate shots of your site with different browsers so you could check for compatibility issues. Does anyone know what the URL is of that site? I’m not sure I bookmarked it, and probably should have.Forum: Your WordPress
In reply to: Bear Mountain BullWell, I’ve looked on three different machines now: on my laptop, it’s very readable because the bgcolor is a very light gray. On my wife’s laptop, you can’t even tell the bgcolor isn’t white! And on my CRT display, the gray is a little darker but still very readable.
And Beel, you’re right – the same can’t really be said for this page!
I think I’ll just dump the bgcolor and leave it at that.Forum: Your WordPress
In reply to: Bear Mountain BullProbably depends on your screen – but you’re right. It could be lighter or might not need a bgcolor at all.
Thanks!
rdsForum: Installing WordPress
In reply to: login problem when installing locallyI spent the last few days fighting this problem. I found that I had two real problems – and actually found solutions for them!
1) I was using the Foxserv setup on WinXP Home, which was running Apache 2.0.39 & PHP 4.2.2. There IS a problem in PHP 4.2.2 which I believe will prevent the login process from working correctly. The problem is that during the login process, WP attempts to generate two cookies to send to your browser. With PHP 4.2.2, only one of the two cookies (the last one generated) actually goes out in the HTTP headers on the reply to the login attempt. I do not believe there is a workaround for this problem other than to upgrade to a newer PHP version. After fighting unsuccessfully to upgrade the Foxserv PHP, I installed the latest XAMPP package and switched to PHP 4.3.8 (XAMPP was great – installed real easy). If you want to examine some PHP discussion on this cookie issue, you can check out http://bugs.php.net/bug.php?id=16626.
2) Once I got around that problem, and the server was actually sending both cookies out, I found that my browser was not returning the cookies to WP as it should. After more digging on this problem, I found that Internet Explorer, in response to security issues, will not accept cookies from servers with ‘non-compliant’ host names. I was using my machine name in the http address to access WP, and my machine name had a ‘_’ (underscore) in it. That made the machine name non-compliant, and the IE browser would not accept the cookies that WP sent at login. I changed my machine name to remove the underscore, and VOILA – I was able to login to WP.
Your mileage may vary – I just thought I’d share the info since it might help a few others to overcome this login issue.