OK, this may be silly, but, I haven't found an answer yet. I have a client that wants to take 14 existing live domains and convert them to WordPress. Sounds like WP multisite would be perfect. They all will have the same look and feel and pages for the most part.
But, my question, where do I install it? I don't want to use any of the existing domains as they are live. Do I just make up a master domain, like example.com, and use Plesk's IP default domain to preview?
Any suggestions?
if your sites data is related to each other you can use one wordpress installation on example.com and develop it to support all.
else you can convert each site to wordpress and place each one in a separate directory
for example : example.com/site1 , example.com/site2 ...
then do permanent redirect for each one to it's directory like bellow:
site1.com permanent redirect to example.com/site1
site2.com permanent redirect to example.com/site2
.
.
Related
I'm trying to change the URL for my site, by going to settings in wp-admin and changing both site url and wp url.
All seems well after I save changes, I'm able to navigate around my blog using the new url. However when I try accessing wp-admin I'm getting a redirect loop. I can still access the wp-admin login page with the old url admin site. In order to access my admin page again I have to login to my DB and reset both urls.
I've also tried to add this code with my urls to my wp-config file
define('WP_HOME','http://www.sample.com');
define('WP_SITEURL','http://www.sample.com');
Other information about my setup:
Openshift is hosting wordpress with the quick start app and proper alias have been added to my app.
Cloudflare is managing my DNS
I wouldn't think either of these factors would be the issue because the site wouldn't work at all if one of these were misconfigured, but at this point I'm drawing a blank. Was thinking maybe it might have something to do with wordpress forcing SSL for wp-admin?
Found It!
I love how when you gather all the information to ask a proper question it seems to line you up for the solution.
I'm also using http://wwwizer.com/naked-domain-redirect to redirect naked domain request to www using an A record in my DNS. All I had to do was turn off cloudflare's protection to this DNS entry.
I have my wordpress installation at /var/www/html/wordpress2 and there's a totally separate wordpress installation at /var/www/html/html/wordpress.
When running the worpdress2 installation, I get errors saying it can't find /var/www/html/wordpress/wp-content/theme/.... How do I change it to look for these things in wordpress2 and not wordpress?
Did you transfer wordpress to Wordpress 2? If so you need two separate databases, one for Wordpress and the other for Wordpress 2. Then you need to check the wp_options table to have their correct subfolder in the site URL and home URL.
Follow these steps in order to transfer your WordPress site from one location to another.
Change the option_value(your root url of current wordpress site) corresponding to id(value 1) and option_name(value site_url).
Access your wp-admin(siteurl/wp-adimn). Go to general-setting panel and change Site Address (URL), same as WordPress Address (URL).
Hope this will work for you. Same process you can follow to move WordPress site from local to server or one server to another.
I have WordPress installed and running on GAE and have added my own custom domain via Google Apps. This is great but my appspot.com url is still publicly accessible and searchable.
How would I go about blocking this and redirecting to my custom domain?
I imagine it involves adding a url handler in the app.yaml file that points to a php file. I have no idea what would go inside though.
Also, how would I then go about setting up a 301 redirect for website canonisation and SEO that accounts for SSL and cron entries?
Any help is appreciated, thanks!
The appspot.com URL is always accessible and there is no way to turn it off. You can't do much in the app.yaml since it's not aware of the custom domain. I'm not really a PHP guy but you should do is to write manually the redirect based on the host URL if you really want to do that. Since you're using WordPress you might need to do quite some work if you don't want to redirect only from the root, but from any page.
Personally I think you should just leave it there and do nothing, even Khan Academy is not redirecting (http://khan-academy.appspot.com) and I'm pretty sure that very few are actually doing that.
We built a website for a client using Wordpress. We used a testing server which always works well. Wordpress was hosted as a subdomain, i.e. http://wordpress.ourcompany.com. I have direct and full access to the server. In the etc/apache2/sites-available directory the file describing the site in question uses the final name http://clientsite.com as ServerName, our temporary subdomain (under which we have been building) is a ServerAlias.
When we were almost ready, we of course asked the client (who already had a website) for their domain login. We changed the DNS like always. It resolved, the site worked well. Although Wordpress kept redirecting (of course) to the subdomain-variant, we could enter the site with the full domain.
Now comes the culprit. I changed the Wordpress settings (siteurl and home) to match the new site. The front-end works brilliantly. However, the back-end is unreachable as long as the settings are in this way. The login page shows up, but just redirects back to itself. If I simply change the Wordpress settings (in the options table) I can log back in, but we want to rid the subdomain necessity (of course).
Things I've already tried (I'm not one to easily ask of your time):
Clear .htaccess
Clear my cache & cookies
Different computer, different browser etc.
Change only the home and not the blogurl value. Sadly, this corrupts some plug-ins
Remove all plugins
Comment some lines as instructed in the wp-login file
Naturally, everything I could find on codex.wordpress
Set the admin cookie path
So, brilliant collective mind that is Stack Overflow, what did I do wrong? DNS? Wordpress settings? Thank you in advance.
You need to go into the settings on the live server and change the URL's to the current site. You'll have to do this by accessing the database directly. It's the wp-options table, and there are 2 entries where the url's are the value. Update those. That should fix the looping.
I found an answer today : the user in the database didn't had the right permissions. You can look up in the error log if there are lines that indicates this.
I also had tried before : removing all content from htacess, reinstalling wordpress etc.
I build a client website and business system using html+php+mysql and both runs on same domain.
Recently, I feel like it would be better to separate the website and use wordpress so that the client can update their own contents instead of me doing this everytime they need to change something.
As, my client is in low budget, I was thinking whether it would be possible to run both the wordpress and business solution on same domain. If I run the business solution under sub-domain will it solve the issue or wordpress’s front controller will pickup any request related to that domain?
Is it possible at all? My suggestion would be appreciated.
many thanks,
Mahbub
It's absolutely possible, yes. And there are many scenarios you can use depending on what you want to do:
Subdomains — install everything in different subdomains, or install one thing at the root and the others in different subdomains. The subdomains normally just map into directories on the same account, so you use the same FTP credentials and so on to transfer files.
Directories — like http://www.example.com/blog. Very easy to deploy a blog this way, and just put your other stuff in the root.
Intermingling — you can actually put files (.php, .html, etc.) in the same directory as WordPress, just as long as there are no name conflicts. The default redirection rules in .htaccess will ensure that those files will get served as usual without interfering with WordPress.
Not knowing anything about your code, if it's simple enough another approach would be to create custom page templates in WordPress that invoke your code. The nice thing about this is that your pages will always have the same look and feel as the other pages in the blog, i.e. if you change/update the theme. This may or may not matter to you.
Its possible. We have implemented it for multiple sites in the following ways
Elgg as Master
FluxBB / PhpBB for forum
Wordpress for blogs
You can then share the sessions between these systems. Just process your login/ registration through only one system.
Sure, you can set the wordpress site in for example: http://blog.example.com and the website in http://www.example.com without any problem. Just need to setup that in the web server.
I did it by putting the wordpress blog in a separate directory inside the large domain. wordpress do not interfere with other php sites on the same domain.
Yes, it's possible.
We'd used Drupal for main website, ELGG for social networking, PHPBB3 for forums and Wordpress for blogging on the same domain name. We did it by using different subdomains for each site.