Moderator
James Huff
(@macmanx)
Volunteer Moderator
No, that’s not the issue.
Thanks for the responses, I still have not figured it out. One thing that may cause an issue or two (though Ihave no idea if it is or why it would) is that the registered url for the site does not yet have the DNS numbers pointing to it, that should happed soon, just waiting on the person who registered the name to log into wherever they did that and update the DNS to the new ISP. I did set word press up with the url the site will be using so maybe this has something to do with that issue…???
Moderator
James Huff
(@macmanx)
Volunteer Moderator
Yes, it does. If the DNS isn’t pointed to the domain name in your area yet, then your site doesn’t exist yet (in your area). I’d give it about 24 more hours before I’d start to complain to the domain name people. One your DNS and domain name are set up, everything should work just fine.
I’m having the same problem as stated above. Without the trailing forward slash you get a page error.
1.2.2 had a trailing fs, why not 1.5? Well, doesn’t seem like too big of a deal, should be able to hack it into the code. The tricky part is making sure that it doesn’t break other functions that might actually add a forward slash. Because the admin page links contain a trailing FS.
Odd, but that’s what ya get with beta’s… Rah Rah!
Solution:
Edit the “header.php” file. Look for this text string:
<div id="header">
<div id="headerimg">
<h1><a href="<?php echo get_settings('siteurl'); ?>" title="<?php bloginfo('name'); ?>"><?php bloginfo('name'); ?></a></h1>
place a forward slash after the “greater than symbol” and before the “quote” after “get_settings site url”.
In addition to header.php (in your theme’s directory), you will need to do the same in wp-register.php and wp-login.php (in the blog’s main directory).