deank

Fixed now … thankfully same day. ManageWP also reached out to me and responded quickly (via FB) which was very reassuring.

They claim “it just works” … but it is not right now. Just to add — the sites in question have the exact same server spec, same version of WordPress etc. Even deleting the ManageWP plugin didn’t help. And for the one with Wordfence, I added the ManageWP management IP and made sure ManageWP was in the allowed list (and also tried reconnecting with the firewall completely disabled). Nothing fixes it. Hours lost. Much frustration!

I found this:

https://tonykwon.com/2010/09/can-we-capture-http-referer-information-upon-form-submission-using-contact-form-7/

PS: I used these instructions to help me install this plugin today:

https://www.arnebrachhold.de/2006/04/07/google-sitemaps-faq-sitemap-issues-errors-and-problems/?utm_source=wp-wm&utm_medium=install&utm_content=help-files#P28_gen_files

My two files site in the domain root directory — where my index.php and .htaccess files live — WordPress files are separately in their own directory (which I have in my settings section of the Dashboard).

Can you go to … https://www.yourdomainname.com/sitemap.xml and see there is a file, even though it is empty? Same for the zipped file?

To fix it, I followed the instructions here:

plugin help

I created two blank text files, named them sitemap.xml and sitemap.xml.gz, put them in my root folder, chmod/changed permissions to make them writable — then I went back into the Plugin page and clicked the link to manually re-generate the sitemap — worked fine, stopped the infinite looping.

You should be able to do that and not have your host want to have a cow ??

To fix it, I followed the instructions here:

plugin help

I created two blank text files, named them sitemap.xml and sitemap.xml.gz, put them in my root folder, chmod/changed permissions to make them writable — then I went back into the Plugin page and clicked the link to manually re-generate the sitemap — worked fine, stopped the infinite looping.

Is anyone able to advise about doing this?

I tried using automatic upgrade today on a site from 2.8.1 to 2.8.2 … but after 4 HOURS in progress, the webpage just stopped and the upgrade didn’t work. Seems strange a huge ISP cannot handle this — that’s why I’d love some help knowing what do do.

No problems here with the new version — installed October 24 (Australian daylight saving time).

Thankfully this fixed resolved the issue for me too, without having to change the structure of my permalinks or the name of my static post page.

And finally I understand why it is happening, with my static post page (“blog”) matching the opening subfolder of my permalink structure (/blog/%postname%/).

At least they now co-exist without having to change either setting, until the issue is fully resolved without manual editing of rewrite.php!

Thanks to all above in this thread for sorting it out, posting solutions and making it easier for me. I’ve had this issue in the past and never got it resolved until now.

Below the two thumbnails used for last/next navigation (in image.php), I also added:

<p align="center">Return to the post: <a href="<?php echo get_permalink($post->post_parent); ?>" rev="attachment"><?php echo get_the_title($post->post_parent); ?></a>

(which I basically took straight from the heading code, plus adding the “Return to the post: ” wording) — that always shows an obvious link for visitors to return to the post (without having to guess that the heading does the same thing).

Maybe that’ll help anyone else reading this page.

Nevermind — I solved it. I could NOT solve it in the same way, but I found a good workaround here:

Using WordPress As A CMS For Small Business Websites

It’s not the same as the other setup, but at least it works!

I just also noticed … on another site I have, this same problem occurs — I had always just had blog posts as home page, but when I tried static page, the https://www.domain.com/blog/ option gave me a 404 error too.

I wish I knew why it worked for https://www.dmk.com.au/blog/ and not for the others. >:|

Depending on the theme you’re using, this code is usually in a file like sidebar.php in the theme folder. You can edit it directly there, with a little bit of HTML knowledge it’s pretty easy to do.

See Using Themes in the docs: https://codex.www.ads-software.com/Using_Themes

If you have correct permission settings, you can edit the theme through the admin login — click on Presentation then Theme Editor. Careful though — once you update there’s no undo.

When I do this, what I do is cut-and-paste the whole sidebar.php (if that’s the right file for your theme) into a plain text file (you could use Notepad — I prefer UltraEdit). Then, I do my edits within the browser, and if I make any mistakes, I can always restore from the version I have kept aside.

>> I still want people to be able to subscribe to my blog – I wont remove that through removing the links, right?

You’re not removing files like your feed when you do this, just the link to it. It’s only a link you’re changing — the feed links should still be in your <head> code for the page, so the feeds are still there (to be recognised by Firefox etc) — but I’m not an expert on Feeds so someone else may have better info on that for you!

To do this, I do what you do tagesk — just edit the theme and remove the comments code.

However, with one site, I think it’s time for comments to re-appear, so if you do it this way, I’d suggest making sure you keep a copy of the original code on hand.

I don’t like to just comment out code (no pun intended!) as it still runs through and processes, and just doesn’t get displayed.