questions4wp

Forum Replies Created

Viewing 15 replies - 1 through 15 (of 55 total)
  • Thread Starter questions4wp

    (@questions4wordpress)

    Wow that’s…actually very weird, I have no idea why the developer added remove_actions for a ton of things. I removed it and it solved all of the issues – thank you very much @jamesosborne !!!

    Thread Starter questions4wp

    (@questions4wordpress)

    @jamesosborne I have just submitted a new response to the Site Health Information form, this time the site URL is a link to a GitHub profile containing the current version of my custom theme. Thank you very much for your help so far!

    Thread Starter questions4wp

    (@questions4wordpress)

    I don’t have a public version available, but I’m happy to make it available to you via whatever means you’d prefer!

    Thread Starter questions4wp

    (@questions4wordpress)

    I have added this line immediately after the opening of the <body> tag of my custom theme, which remains active:

    <body>
<?php wp_body_open(); ?>

    CloudFlare remains paused. I do not yet see the Site Kit tag though!

    Thread Starter questions4wp

    (@questions4wordpress)

    (I have switched back to my primary, custom theme)

    My custom theme does not contain wp_body_open anywhere – although, I searched the Twenty Twenty-Three theme as well so I could use it as an example, and I don’t see a reference to it there either

    Thread Starter questions4wp

    (@questions4wordpress)

    I do indeed see the Site Kit snippet now! So what should I do to bring my theme in line?

    Thread Starter questions4wp

    (@questions4wordpress)

    Hello @jamesosborne , CloudFlare is paused and the Twenty Twenty-Three theme is active

    Thread Starter questions4wp

    (@questions4wordpress)

    Thank so much for your reply @jamesosborne – I will try to follow your instructions and put the results below.

    Regarding UA, I totally understand that it’s been deprecated, my point with it was just that SiteKit worked for me until UA was deprecated for GA4 – meaning, whatever hooks were in my custom theme triggered SiteKit correctly. I haven’t modified my theme since then, but perhaps the plugin has been updated in some way that makes it incompatible.

    Per your instructions:

    Steps 1, 2, and 3: Complete

    4. From the same screen click on the “Available Plugins” tab at the top right and then click on the “Enable” option next to “Site Kit by Google“.

    Done! Now there are 2 enabled plugins in troubleshooting mode – Health Check and Site Kit by Google. In addition, I installed the Twenty Twenty-Three theme as the default theme for troubleshooting.

    5. From the same screen click on the “Available Plugins” tab at the top right and then click on the “Enable” option next to “Site Kit by Google“.

    Done! Now there are 2 enabled plugins in troubleshooting mode – Health Check and Site Kit by Google. In addition, I installed the Twenty Twenty-Three theme as the default theme for troubleshooting.

    6. Check your sites source code and see can you identity any Site Kit placed Analytics snippet (as per this guide). If you need help with this let me know.

    Using the same Chrome incognito browser that I am logged in as an admin to, I do not see the following line from the guide you linked to, or any of the subsequent lines:

    <!-- Google Analytics snippet added by Site Kit -->

    Instead, I see the following lines, which seems to have some relevance to Google Analytics/Tag Manager, within <head>:

    <script type="text/javascript">
window["ga-disable-UA-198#####-1"] = true;
</script>
<script type="text/javascript">
window["ga-disable-G-0GF#######"] = true;
</script>
...

<link rel="dns-prefetch"  />
...
<meta name="generator" content="Site Kit by Google 1.108.0" /><style type="text/css" media="print">#wpadminbar { display:none; }</style>
<style type="text/css" media="screen">
	html { margin-top: 32px !important; }
	@media screen and ( max-width: 782px ) {
		html { margin-top: 46px !important; }
	}
</style>

    Not really sure if that helps you to diagnose what’s happening here, but hopefully it does!

    • This reply was modified 1 year, 6 months ago by questions4wp.
    • This reply was modified 1 year, 6 months ago by questions4wp.
    questions4wp

    (@questions4wordpress)

    @marius I also was able to solve my problem – I went to Settings -> General and changed both the WordPress Address (URL) and the Site Address (URL) to be all lower case (it was in camel case before), and the permalinks are back in working order. All of the pages are now running properly.

    My site is now exactly as it was – 4.4.1, permalinks involving %postname% (as opposed to the default, which is the post ID), same plugins installed, no new code in functions.php, no changes to mod_security. The only thing that was really changed was making the URLs lowercase in the settings.

    Thank you everyone for your help!

    questions4wp

    (@questions4wordpress)

    Sure, very happy to help. I’m running the site (and several others, which are not affected) on a VPS with InMotion Hosting. I also have a non-VPS shared server with them, and none of the WordPress sites on that server have been affected.

    My .htaccess has that exact same text in it – previously there was a linebreak at the beginning, but then I deleted it and let WordPress re-generate it, and now it has that exact text with no linebreak. I doubt the linebreak has any actual bearing on the functionality, just thought I’d report all the details.

    Below is the dump from the Send System Info plugin – I’ve had to remove some of the identifying information, as this is a client’s site and they’d prefer not to have it posted on the forum – however, all of the technical information is the same. I’ve noted where I’ve removed any information. Hope this helps, please let me know if there’s anything else I can provide.

    Also, regarding the plugins listed, they’re all active at the moment, but aren’t all active during the normal use of the site. As I said in a previous post, disabling all of them doesn’t fix the issue.

    // Generated by the Send System Info Plugin //

    Multisite: No

    SITE_URL: https://MySite.com (REMOVED)
    HOME_URL: https://MySite.com (REMOVED)

    WordPress Version: 4.4.1
    Permalink Structure: /%category%/%postname%/
    Active Theme: Custom Theme for Client MySite.com (REMOVED)

    Registered Post Stati: publish, future, draft, pending, private, trash, auto-draft, inherit

    Platform: Windows
    Browser Name: Chrome
    Browser Version: 47.0.2526.106
    User Agent String: Mozilla/5.0 (Windows NT 10.0; WO
    W64) AppleWebKit/537.36 (KHTML,
    like Gecko) Chrome/47.0.2526.106
    Safari/537.36

    PHP Version: 5.4.33
    MySQL Version: 5.6.28
    Web Server Info: Apache

    WordPress Memory Limit: 40MB
    PHP Safe Mode: No
    PHP Memory Limit: 256M
    PHP Upload Max Size: 128M
    PHP Post Max Size: 128M
    PHP Upload Max Filesize: 128M
    PHP Time Limit: 30
    PHP Max Input Vars: 1000
    PHP Arg Separator: &
    PHP Allow URL File Open: Yes
    WP_DEBUG: Disabled

    WP Table Prefix: Length: 3 Status: Acceptable

    Show On Front: page
    Page On Front: Home (#5)
    Page For Posts: (#0)

    WP Remote Post: wp_remote_post() works

    Session: Disabled
    Session Name: PHPSESSID
    Cookie Path: /
    Save Path: /tmp
    Use Cookies: On
    Use Only Cookies: On

    DISPLAY ERRORS: On (1)
    FSOCKOPEN: Your server supports fsockopen.
    cURL: Your server supports cURL.
    SOAP Client: Your server has the SOAP Client enabled.
    SUHOSIN: Your server does not have SUHOSIN installed.

    ACTIVE PLUGINS:

    Akismet: 3.1.7
    Google Analytics by Yoast: 5.4.6
    Infinite Scroll: 2.6.2
    Insert PHP: 1.3
    Jetpack by WordPress.com: 3.8.2
    Require Post Category: 1.0.4
    Send System Info: 1.2
    SEO Redirection: 3.4
    Wordfence Security: 6.0.22
    Yoast SEO: 3.0.7

    questions4wp

    (@questions4wordpress)

    @marius, I’ve just tested the code by placing it in the functions.php file for an affected site (like other commenters, just one of my sites was affected). It did not solve the problem for me.

    To list out what others have said –

    Apparent Causes:

    • Permalinks set to something other than the default (mine is /%category%/%postname%/)
    • Static home page

    Symptoms:

    • “Too Many Redirects” error on home page (other pages and posts work, even through their permalinks)

    Changing either of the settings in the “Apparent Causes” list fixes the problem for me, although obviously it’s a temporary solution since that’s how I want my links.

    I’ve also tried removing all of the plugins to see if any of them were the issue, but it didn’t help. I may have to downgrade to 4.4.0 tonight if I can’t find a solution, but I’m happy to try different suggestions on my site in the mean time.

    A suggestion in a different forum thread said to change your permalinks to the default, delete your .htaccess file, then change it back, allowing WordPress to recreate the .htaccess file. Unfortunately, this did not work for me either – other than a line break at the beginning of the file, the newly generated file was identical to the old file, and did not solve the issue.

    questions4wp

    (@questions4wordpress)

    I’m having the same issue since the 4.4.1 update – I had my permalinks set to /%category%/%postname%/, which worked fine for a few months’ worth of previous WordPress versions. Since the 4.4.1 update, the site’s home page became unreachable, throwing a “too many redirects” loop. Interestingly, other pages and posts on the site were still reachable – just not the home page.

    Setting the permalinks to their default, the post ID, allows me to reach the home page. I tried deleting the .htaccess file, then setting the permalinks back the way they were, but this did not solve the issue for me – pages and posts are still accessible, but the home page still is not. I looked at the old and the new .htaccess files – besides a linebreak at the beginning, they’re identical anyway.

    I also deactivated all of my plugins to get a cleaner test base, but still have not found a solution, unfortunately. I have about a dozen other WordPress sites, all of which work fine – I’m not sure what’s unique about this particular site. I’m going to continue to investigate and will make another post if I find a solution – but if anyone has other advice, I’d really appreciate it!

    Thread Starter questions4wp

    (@questions4wordpress)

    I figured it out! Well, really, the tech support people figured it out =)

    After confirming all file permissions were correct, .htaccess looked normal (similar if not identical to bemdesign’s post), that all the files were on the server and were their most updated versions, and that all the plugins were fine (or even disabled/deleted), I contacted my host for support (I prefer not to contact them for WordPress-related issues, since it’s an external application).

    I use InMotionHosting, but the solution might be relevant for others. WordPress 3.7 requires PHP version 5.3. The cPanel on my host shows that it is indeed running a 5.3.* release, so I didn’t think anything of it. It turns out that there are multiple versions available for different applications. To force that domain to use PHP 5.3, the tech person added the following line to the top of my .htaccess file:

    AddHandler application/x-httpd-php5 .php

    It now works fine. I can confirm that all pages are accessible (both administrative and content), and I can update everything. I have gone around making this change to all of my domains, and they all seem to work.

    Thread Starter questions4wp

    (@questions4wordpress)

    I am sure that I turned off all the plugins (I renamed the plugin folder plugins-old), and I renamed the .htaccess file located in my site root as well. Renaming the plugins folder did nothing, although renaming the .htaccess file made mydomain.com/wp-admin/update-core.php return a 500 error instead of a 404. The 500 error was handled by my server (as opposed to the 404, which was handled by WordPress).

    Interestingly, I can edit pages just fine, and the URL for the page editor is mydomain.com/wp-admin/edit.php?post_type=page

    Thread Starter questions4wp

    (@questions4wordpress)

    None, unfortunately

Viewing 15 replies - 1 through 15 (of 55 total)