vkuehn2

I now have the correct syntax.

This did NOT work:

<img class="style5" src="images/twang.png" />

This DID work:

<img class="style5" src="/1-image/twang.png" />

I created a NEW FOLDER in the ROOT FOLDER:

root –> 1-image and put the graphic file there. Now when I FTP with additional graphics I am not digging down five or six levels to find the file and I don’t have the ugly LONG url in the HTML. (Note that the src folder is predeeded by a “/” which tells WordPress not to look in the default location but to start the look to the ROOT folder.

In the words attributed to fighter pilots, jet-jockeys:

WE HAVE JOY! I shall wait until tomorrow morning to mark this thread as resolved but I think we are there.

When I first installed WordPress, I was not sure how I wanted to configure the site, or how to do what I did know I wanted to do. I created a folder on the server named “blog” but when I decided everything would go in the “root” directory, blog lived on as an empty folder. Default Permalink didn’t care. Numberic Permalink declared: “Not on MY watch!” Folder deleted. Behavior of site navigation appears to be on the money.

Thanks to all who contributed suggestions.

vkuehn

Thanks, songdogtech. Let’s see if I can rule out some possibilities.

This behavior was the same when I had no .htaccess file so I am inclined to discount this suggestion. I just went and read the code/syntax of .htaccess and nothing there looked “ripe” for picking. However, I am reaching a little past my skill set so I could miss something.

I read through wp-config.php and no ripe looking language there. It does refer to ABSOLUTE SETTINGS for wp-settings.php which has possbilities, but none looked obvious.

In DASHBOARD > SETTINGS: the entries for
WordPress Address(URL) and Blog Address (URL) bother me. It says for the second blank (Blog Address) “Enter here if you want blog address different from the directory you installed WordPress.

It was filled in with identical info. Could this cause the reduntant URL when trying to reach BLOG?

I tried to blank it out. It refused to update to ‘blank’. I currently have nothing more thatn “http:” in that space but the behavior has not changed.

There is always tomorrow!

By the way…. what is a GoDaddy WIMP Setup ?

The GoDaddy HelpDesk didn’t have an answer to that question.

Thank you, people. We are making progress, but we are not quite there yet. I had a heart-to-heart with GoDaddy. I may be on a Windows servier, but I am not on “the GRID” system. They confirmed that I did not currently have a .htaccess file and if I put one there via FTP I would indeed be able to see it. They also referred me to a Word Press WIKI which listed the following link as a resource on .htaccess files.

I lifted the code/syntax out of Perishable Press, created an .htaccess file and it now lives on my server.

Once again I have changed my choice of a Permalink from default to numbers. If you go to my site you will see the problem.

https://www.yourlpfm.com

You land on the home page, you can navigate to ABOUT and LINKS and select a given post from CATEGORIES and everything is wonderful. Click on BLOG and watch it crash.

My next plan is to get up tomorrow morning and retrace my steps where I set up a frontpage to be my landing page rather than landing on the blog page and see if maybe I “fat-fingered” some code there in modifying my THEME.

I am still receptive to hints and suggestions on what may be causing this problem. In addition to being weary at the end of the day, I want to give the server and WordPress time to maybe self-heal this crash-and-burn and the new .htaccess file gets digested.

It is good to see traffic responding to my problem!

I am using a Windows hosting on GoDaddy rather than Linux.

songdogtech: your WordPress > Support link was a bit helpful and I have got to sit still long enough to digest everything there. I just did a quick effort to reach the 49thLatitude link and that is “hosed” for now so I will see if I can go into 49th Latitude from the top and work my way down to the section this link tried to reach.

Thank you for confirming that this is a situation others have run into. I have tinkered with some code in my theme but not in the last two weeks so I didn’t think this problem was code I have broken.

I’m not a newbie in the computer world, BUT I am a newbie in WordPress, PHP and deeper into website-server issues than ever before. Thanks.

Sorry. The name of the site was kind of buried in the verbiage.

https://www.yourlpfm.com