Probably the easiest way is to go into the db, remove all the www’s.
Now make sure that on the server side, any requests for www goes to domain.com. And make sure everywhere else on the web account the domain is domain.com, not http://www.domain.com
@andrea_r. Hi we meet again. Glad to know I am in good hands.
I have already trawled the db. I found references in wp_options were aimed at www for the main url, but then went a bit deeper and found references to the previous website. Changed all and bingo the permalinks page showed the website as domain.com, rather than http://www.domain.com. Thought |I had been such a clever thingy. In celebration I changed the permalink to a simple /%postname%/ and bam – there it was.
Now to final checks – openned network admin/sites. Clicked edit on a site and I got the site edit screen. Aha – so I clicked the dashboard – and I am still grinding my teeth…same problem – failed to open.
Somewhere there is a switch that needs a change. Whether that is in the main wp_… area or in the individual post I am not sure – all my looking came up with nothing obvious.
Last piece – your “Now make sure that on the server side, any requests for www goes to domain.com” leaves me in that sure location of “huh” – What is “the server side” (now you know how little I really know)
Appreciate your help.
Regards
Ken
She means to make sure that your server redirects both http://www.domain.com and domain.com to the right place. Not all servers do.
You’ve got a bunch of issues. 🙂 We did the www one. the sub sites not showing will be different. are they subdomains? do you have wildcard subdomains set up. Ca you give me a link?
Last piece – your “Now make sure that on the server side, any requests for www goes to domain.com” leaves me in that sure location of “huh” – What is “the server side” (now you know how little I really know)
Your web host control panel 🙂 On some, there is a setting /field whatever on their end where they ask your preference. If the stuff you did earlier cleaned it up, you should be okay.
Now we try and figure out the sub sites. which may be a different issues entirely.
@andrea_r – The answer to the question of subdomains is yes – I set it up for subdomains. wp-config.php entry:
define(‘WP_ALLOW_MULTISITE’, true);
define( ‘MULTISITE’, true );
define( ‘SUBDOMAIN_INSTALL’, true );
$base = ‘/’;
define( ‘DOMAIN_CURRENT_SITE’, ‘sweetblogspot.com’ );
define( ‘PATH_CURRENT_SITE’, ‘/’ );
define( ‘SITE_ID_CURRENT_SITE’, 1 );
define( ‘BLOG_ID_CURRENT_SITE’, 1 );
I have put a request to my ISP to confirm the wildcard issue.
Link is http://sweetblogspot.com – this is setup as an addon domain
In the admin area the “my sites” drop-down menu gives the same result as network admin/mysites – no access to dashboard. I am happy to send you access to admin via separate email if you require it.
@ipstenu – I will ask the question. As I understand things, WP does not need any code in the .htaccess file to redirect the http://www.domain.com to domain.com when set up for subdomains – correct me if I am wrong, please. However, it will be of interest to confirm or otherwise the sever-side issue (ha!- now I understand something of what server is 🙂 )
Regards
Ken
@andrea_r – ISP has enabled wildcards
Now I cannot go to the page on entering the url
ie: http://sportsbettingreviews.sweetblogspot.com/
but can go to a page using the tabs on the main page.
ie http://sweetblogspot.com/category/sport/
@ipstenu – ISP advises:”I believe things are set correctly for this. If not, let me know.
www. and wildcards are doing to the same location. From there,
Wordpress should do the needed redirection.”
Re the task outlined above (reply to Andrea_r) I will go back to the ISP and ask for a check on the redirection issue. I think it is working correctly as when I put the url as http://www.sweetblogspot.com the page appears with the address changed to http://sweetblogspot.com
Ho Ho Ho… I turned off ALL plugins, and logged out/in, reactivated plugins. Being a manic depressive when I can’t get anything to work – well it just seems that way – I fiddled around to see if I could manually enter the subdomain site to get a page – blimey, it works.
OK, went to site admin/sites/ and clicked view link – wow – http://fitnessandhealthreviews.sweetblogspot.com/ is looking at me (needs a lot of work 🙁
Same result for dashboard – folks I think we are alive!!
Just one last thing to do – create a new site… holding breath … aahh, I’m a happy little sandboy!
I will create a blog for this excercise
My thanks for your considerable assistance. Wishlist?
Regards
Ken
The reason you had to add them, and why your ISP kept saying they were enabled is this:
They are enabled on your MAIN domain of your web account. Not add-on domains. 😀
(you’ll see me at SP too.)
@andrea_r and @ipstenu – many thanks.
Quelle est “SP”
Lesson learned – make sure the wildcards are turned on for add-ons as well…
SP = StudioPress. You’re running a Genesis child theme on the sub site. 😉
Lesson learned – make sure the wildcards are turned on for add-ons as well…
On shared hosts you can’t. That’s the catch. On a vps yes you can.
@andrea_r Sorry, but I am puzzled does “shared host” mean add-on domains? or does it mean subdomains such as those within the WP structure?
In other words:
Is there a problem turning on wildcard for an add-on domain such as the structure I presently have? (wildcard turned on for main domain and add-on domain – which add-on is the domain we have been working on.)
My ISP says there is a looping going on, and I find the sweetblogspot takes maybe 10-12 seconds to load.
If this is the case I will have to settle sweetblogspot as the core domain – the other one can survive on panel generated subdomains.
Await your comment.
shared host means the kind of ISP you have. nothing to do with wordpress at all, or subdomains.
It means your web account is on a server with (usually) hundreds of other websites.
In other words:
Is there a problem turning on wildcard for an add-on domain such as the structure I presently have? (wildcard turned on for main domain and add-on domain – which add-on is the domain we have been working on.)
That’s what I’ve been trying to explain – on most bottom-line hosts, ou cannot have wildcard subdomains enabled for add-on domains. it has to be the cre domain.
so yes, you may have to do this:
If this is the case I will have to settle sweetblogspot as the core domain – the other one can survive on panel generated subdomains.
