I have developed a site using drupal. Now I moved from test server to live server. Now if I make changes to the test site its reflecting to live site too. I am surprised. Please could anyone tell that how should I fix above problem.
Ok, assuming you mean changes at the content level (like content types, menus, taxonomies, users, ..), then it probably means you're sharing the database between the two sites. You'll need to point the one of them to a copy of that database so you split the sites. This can be done by adjusting the sites/default/settings.php file typically.
Related
I want to set up a system where a developer can work on a separate server on a wordpress website.
My question is: If in the meantime changes are made to the live site (like plugin updates, new plugins, new posts, new comments, etc), how is one able to import a new feature (e.g. a new page) from the development server on the live site while making sure that previous changes on the live site don't get deleted?
I am looking to understand how this all works. In a sense, I would like to have some kind of version control system.
Thanks in advance :)
You can version control your own code using git. Basically we would init a new git repo and commit changes onto this repository. This can lie separately outside of the core files. i.e you only need to include the wp-content directory and ignore all the other core wordpress files.
Here is a good article on how to do a really good versioning system for a website.
http://toroid.org/git-website-howto
The posts and pages (basically content) in a wordpress site however lies in the database.Any changes made there will be permanent.
The only option is to keep taking regular backups of the content. You can do this by using an automated backup tool.
If you really want to version control your database, here is an article that helps:
https://blog.codinghorror.com/get-your-database-under-version-control/
This one is a tricky one. You cant host a single website on two servers. Just imagine a website having 2 hosted urls..!! No way.. You can never do that.
You better create a new user and give access to him. Look carefully in the settings and be a admin. You will have a chance to approve or reject what the second user changes.
Hope this helps.
This is my first time migrating a website from Joomla to Wordpress. The website: www.sfspas.com
1- I am worried that the website will not transfer well or that I will loose functionalities.
Can I duplicate the code and just transfer that version to Wordpress? (Keeping the website live via Joomla and creating in parallel a new website www.sfpsas222.com in wordpress to test things out?)
The website has to be live 24h/7 and It can't just break. How can I make sure the inventory will be uploaded correctly and the website will look as it looks now?
2- Once transferred. If I want to change the appearance of the index.php can I simply upload a newly designed index page on Wordpress? How can I go about it? Any suggestions will be highly appreciated!
Thanks!
I recently transferred one of my sites from Joomla to Wordpress and I can say, that it's not just one-click action. Both frameworks have their own structure, you can't transfer content and users directly.
In short, for transfer you need to create a simple plugin which will take all require info from Joomla (articles, users, etc.) and inject it into Wordpress database, converting prior to that, if necessary.
And no, you CAN NOT do this on 24/7 running site. Don't even think about it. Duplicate your site, convert its database to WordPress, check, that everything works properly, and only then put it online.
It's not an easy process and it requires some knowledge. Even if some kind of Joomla-Wordpress converter exists, you'll have a lot of things messed 100% guaranteed. I've made a lot of transfers in my life, so I'm pretty sure of it.
Providing you have a required knowledge of database management and PHP, just be patient and spend some time. If you don't - hire a professional. There's no easy way here, because Joomla and WordPress are like car and bike. Both are a transport, both run fast, but you can't convert one into another without any effort.
Not sure if this is the right place to ask, sorry if its not. I build a lot of Wordpress sites. My problem is, the number of them is getting big and harder to update them all when new releases come out.
I have written an app that will download the latest Wordpress release, and manually ftp the new files to all the clients, but this takes forever... need a new way.
I wanted to restructure this while I can or start a new process at least. Whats the best way to manage multiple Wordpress sites and keep them all updated? Some people have said 1 DB and modded config, others I have seen said to keep all installs separate and use plugins to automatically upgrade, but I don't know whats best to do. Ideas? Thanks :)
If these were all sites you managed on your own server, I'd recommend using a Multisite installation rather than separate instances of WordPress. This way you only have one set of themes, one set of plug-ins, and one copy of WordPress to maintain.
If these sites are on different servers (i.e. you're maintaining sites for clients remotely), I'd recommend you look in to a beta account with WP Remote. This is a service specifically built to allow you to remotely monitor and update multiple WordPress installations. It might be the best solution for you because it allows you to use the one-click update rather than manually downloading/FTP-ing the new files.
You can use this free self hosted app http://infinitewp.com
No limitation in number of sites being managed. You can update WP/plugin/themes, do backups, one click login to your WordPress admin panel.
EAMann is right, especially with the new Multi Site features in Wordpress 3.0, there is no better way to manage multiple sites under one umbrella. Being a developer myself, I know the pain of having to login to all those different accounts!
The way to set it up is create a "master domain name" that you will log into. Place this in your WP Config:
define('WP_ALLOW_MULTISITE', true);
Then login to your admin panel, navigate to TOOLS>Network.
After you've set everything up, copy/paste what it tells you to your HTAccess and WP Config file.
The next step, especially if you are putting clients on this network, is they will want their own domain name, not AIBot.com/theirname right? Thats where Domain Mapping comes in:
http://ottopress.com/2010/wordpress-3-0-multisite-domain-mapping-tutorial/
Check that out and good luck!
What you need is www.managewp.com it can do all of that for you plus a ton of other excellent features.
Is it possible to control 2 different Drupal website from 1 admin panel? 2 different domain, but on same host-server.
one of my client came up with the idea and I wasn't sure if it can be done.
Appreciate advices! Thanks a lot!
If you're just trying to have two domains point to the same Drupal installation (e.g. http://example.com/ and http://example2.com point to the same Example Drupal website), this is supported out of the box as long as you don't use a multisite setup.
That is, normally, you'd just stick your settings.php file in sites/default/. If you did that, any domain that's pointed to the Drupal directory will use the same Drupal site. You don't need to do anything else.
If you've stuck your site in sites/example.com, you could create a symbolic link with the name of the other domain; i.e. you'd have sites/example.com and a symbolic link to it called sites/example2.com.
If you're trying to run two disparate sites through the same admin panel, you can't do it per se: that is, you can't manage most aspects of Drupal through its default administration system because it's not designed to do that.
However, if you're trying to simulate something like Plesk or Cpanel—that is, you just want to easily manage Drupal deployments using one control panel—there is a project under heavy development called Aegir. I've used it on a few different occasions and it works pretty great, but it's a somewhat involved setup process.
With http://drupal.org/project/domain you can simulate two websites. Is not actually two different Drupal installation.
You can take a look http://drupal.org/node/346385 for more information about the different multi-site options.
No, not that I am aware. As well as the content, all the administration aspects of the site are stored in the site's database, so the admin area and the front end of the site are joined at the hip! 1 database per site, so 1 admin area per site.
There is Aegir http://www.aegirproject.org which is a multi-site manager dashboard system. It's more for creating and managing the site than for managing content, but it might be what you're looking for.
I want to move a drupal site to another domain and am looking for best practices, gotchas, hint, tips, etc to make sure I get through it smoothly.
Links and comments are appreciated.
You might want to give a try to the Backup And Migrate module.
There is also this handbook page that gives instructions on how to backup your drupal site.
It took me 1-2 hours. I do not have a step-by-step guide (I wish I had written everything down), but it entails updating the configuration files, updating the database (some tables have domain references, but I don't recall which - it could be that this was just for my image references in the Gallery2 database), and doing a cursory search of the content for full domain references in anchor links.
I migrated a Drupal 6 site with about 40 plug-ins, including Gallery2 and Google Maps integration, and I did not run into any major road blocks.
If you (and the authors of the contrib modules you used) did a good job by not putting absolute URL's in the code, it should be dead easy (I do it routinely when migrating the development site to a live production one, for its launch).
Of course I assume that you are doing things sensibly, and for example are not migrating a site from an apache/mySQL server to a nginx/postgres one, maybe also adding the need to prefix your DB tables in the process.
If this is the case, then you simply have to copy your entire file tree and export/reimport your DB.
If you are migrating between two similar architectures then chances are you will only have to change a few things in the settings.php file. The file is well documented. The only two things that I normally have to change are:
DB user/pass
cookies domain
In the file there are also additional configuration options like the possibility to choose the base URL manually in case of problems.
Don't forget to flush the cache once you log in the new migrated site for the first time.
EDIT: Just came to my mind: if you use any, you will also have to update your developer keys to third party API's (for example if you use google maps or google analytics) as these are domain specific.
HTH!
Basically, what mac said (+1)
In addition, I often need to adjust the .htaccess files a bit concerning the rewrite rules. For smaller sites on shared hosting environments, I usually place the drupal installations in subfolders within the document root (e.g. to allow for staging, etc.), 'hiding' the subfolder via URL rewriting. So for every 'move' of a site, I need to fix those rules.
The biggest culprit for me are sites that use modules that have to store absolute URLs in order to do their job (e.g. securepages). For those you should disable them prior to moving the site, adjusting their settings before reenabling.
If you are not sure if some of the modules you use store absolute URLs, it might pay of to extract your database dump locally and search the resulting file for occurrences of 'http://', 'https://' and the likes, as well as for your 'old' domain name (you'll need to exclude the watchdog and cache tables for this).