mroulston
Forum Replies Created
-
Thanks @corrinarusso and @bcworkz for responding and helping me out.
I will try your suggestions and hopefully get this working.
- This reply was modified 4 years, 8 months ago by mroulston.
Update: After spending way more time than I’d like to admit trying to solve this mystery, I decided to just upgrade to PHP 7.4 and let it remain a mystery.
Thanks @corrinarusso for responding and helping me out.
Yeah, I’m just trying to solve this because I’m very curious about it, not because it’s an actual problem. Anyway, both PHP info files report the correct version (7.3.19), the same as what WordPress is detecting.
It seems to me that both sites are detecting the correct version of PHP, but one site is being told by the API at https://api.www.ads-software.com/core/serve-happy/1.0/ that PHP 7.3 is the minimum recommended version of WordPress, while the other site is being told by the same API that 7.4 is the minimum recommended version.
Sorry, yes, I should have also mentioned that. Both sites have the exact same plugins installed, and are running nearly the same theme (some very minor HTML changes between the two themes, but the themes are nearly identical, including the templates and functions.php file).
I’ve located the file on the server that appears to be testing the PHP version and delivering the alert (/wp-admin/includes/class-wp-site-health.php), and I confirmed that both files are identical in both installations of WordPress.
I then saw that it looks like the function performing the check is wp_check_php_version();, which is located in the /wp-admin/includes/misc.php file, and I confirmed that again, both files in both installations are identical.
So I find this very curious and I would love to pin down exactly what’s causing two sites to report different minimum recommended versions of WordPress when nearly everything between the two sites (from what I can see) is identical.
- This reply was modified 4 years, 8 months ago by mroulston.
Forum: Fixing WordPress
In reply to: Endless redirects on blog pageI figured out that the problem had something to do with the fact that I had WordPress installed in the /blog directory on my server. I think Apache was confused because WordPress was telling it to remove the trailing slash from /blog, but Apache wanted the slash there because /blog was a real directory on my server. I decided to move my WordPress install into the root of my server, delete the /blog directory, and that fixed the endless redirect problem.
Forum: Fixing WordPress
In reply to: Endless redirects on blog pageWorks fine with /%postname%/.
Forum: Fixing WordPress
In reply to: Endless redirects on blog pageThe problem still exists with the 2012 theme and all plugins deactivated.
Forum: Hacks
In reply to: Dynamic body id to show current page in navigation menuAll figured out. I just needed to change the 1 to a 0. I guess WordPress starts the page count from 0 instead of 1. Thanks for your help, bcworkz. I really appreciate it.
Forum: Hacks
In reply to: Dynamic body id to show current page in navigation menuThanks! I updated the code with the changes you suggested, but I think I might have made a mistake. Can you take a look and let me know what I’ve done wrong? Here’s the code I’ve got now:
<?php function page_bodyid() { // add id to <body> tag global $wp_query; global $paged; $page = ''; if (is_front_page() && $paged == 1 ) { $page = 'home'; } elseif (is_page()) { $page = $wp_query->query_vars["pagename"]; } if ($page) echo ' id="'. $page. '"'; } ?>Forum: Fixing WordPress
In reply to: Problem 2.5.1 post_new.php and post.phpThank you, thank you, thank you ZeusII. I followed your instructions and all seems to be working normal now.
I spend the better part of the afternoon today trying fruitlessly to fix this, so I REALLY appreciate the detailed instructions!
Forum: Fixing WordPress
In reply to: Problem w/ 2.5.1 and Safari 3.1.1 (post_new.php)Yep, that’s exactly what I did, and no joy.
First time I tried it, I just cleared the cookies that were from blog site, but I just went so far as to delete every cookie in Safari (first clear cache, then delete all cookies, then quit and relaunch), just to see if that might help, but no joy.
What puzzles me is that I installed a fresh version of 2.5.1 on the same server and tested it and it doesn’t do this problem, so my thinking about my main blog is that something got messed up iduring the upgrade process.
Forum: Fixing WordPress
In reply to: Problem 2.5.1 post_new.php and post.phpWhat puzzles me is I installed a fresh version of 2.5.1 on my server and it doesn’t do this problem with Safari. So as far as I can tell, this is not a blanket problem with 2.5.1 and Safari, but rather something going wonky during the upgrade progress.
Forum: Fixing WordPress
In reply to: Problem w/ 2.5.1 and Safari 3.1.1 (post_new.php)Thanks for the suggestion, Sam. I tried that, but no joy.
Forum: Fixing WordPress
In reply to: Problem 2.5.1 post_new.php and post.phpI’ve having the exact same problem with 2.5.1 in Safari. I created my own thread about it earlier but still haven’t gotten a resolution.
As a test, I installed a fresh version of 2.5.1 on my server and it does not exhibit this problem in Safari. If worse comes to worse, I will try to export my blog from the upgraded installation to a new installation and see if that fixes the problem, but I’d rather not have to go through all that trouble, so I’m hoping someone might suggest an easier fix.