zabadac

Thankfully I had installed an Avada child theme, so doing this in the child theme’s functions.php file presents no problems with theme upgrades.

This worked very well, thank you, I really appreciate the help.

Problem solved.

You are welcome, I appreciate the support and trust you can find a solution.

Kindest regards

Thank you for your reply.

I did the update to 4.0.7 via the WordPress admin backend, plugin updates.

I have re-tested, and the error occurs for:

/wp-login.php
/wp-admin/

The does does not occur for:

/wp-admin.php
/wp-login/

You may find this discussion (written a few years ago) about relative links in WordPress interesting: For the original question, we are talking about ‘absolute relative’ links, where really only the domain name is ommitted from the link.

https://mathiasbynens.be/archive/2005/02/relative-links

It includes a plugin that works well:
https://plugins.trac.www.ads-software.com/browser/relative-links/

I believe it may not necessarily with other plugins although it can be made to work.

Also, there is a possible performance issue. I’ve tried it on some ‘post and page’ images, and I think for a modest WP site the performance question is not an issue.

A live example is on https://avondaleaudio.com
I placed the images in a directory called ‘webimages’ under the main public_html directory for the website, not for any technical reason, just preference.
In the post/page, the link is simply:
/webimages/imagefilename.extension

The original question has been poorly answered in my opinion.

WordPress either supports the use of relative URLs, or it doesn’t.
I agree with ‘jderosa3 that for porting sites it would be useful, when you generally need to prepare the site before switching DNS setting. Th same is true for development, prior to deployment in a live environment.

Such sites in preparation do not need to point to another server location defined by live DNS settings. It makes the process of testing the site being ported difficult and incomplete, and forces a ‘live’ test before you can besure everything has been done properly. This is irregular practice. Indeed it IS good practice to ‘wrap’ a site as a self contained entity, for reliable running, ease of updates and maintenance.

If relative links are not supported, then a solution is, as suggested, to simply host the images elsewhere and use the absolute links. However, this is not always ideal, it’s a compromise.

The Feed Reader argument is not a case against the support for relative links, just a case that the Feed Reader situation needs to be looked at.

best regards, Peter