I have a website live on the web. I've been working on the re-design for the site. I duplicated the entire site and database and worked on a test site. Now the test site is ready to go live. However, the current live site has been up for the last few weeks and content has been added as usual. How do I upload my new look for the site, with the changes I've made in the test database but at the same time not overwrite any content changes made in the current live database that were made over the past few weeks?
I want to keep the site content in the database but overwrite any module or theme data with the data from the test database.
My site is built on drupal
Thanks!
1) Upload new theme - this will apply themes changes and keep content in the live DB
2) If you have added any new content types, blocks, fields etc to your dev site then install the features modules. This will allow you to export your new features to a module, and then you can add this module to the live site to import your new features.
See this post for further discussion on the topic.
I used https://drupal.org/project/data_export_import it seems to be working well.
Related
I'm working on a Joomla site. I have created some overrides for blog and single article, when I checked my site on local it displayed all things exactly as I want, but when I uploaded it to live some overrides for blog and single article were not showing as well as a plugin which I added on localhost. I cant understand the reason as I have checkede every thing on live, and it's working fine on local host.
NOTE: the site was already live. I added some new overrides for blog and single article. Before i uploaded new first I deleted all the existing code on live and cleared its DB, then i uploaded all new code and DB. Almost all the old things are working fine on live but not some new changes/overrides. I am using Joomla 3.5.
You have to clean your browser cache first.
Best is to install akeeba backup in localhost and then take backup and Restore in live server.
Clear your Joomla cache - it is most likely caching the old layouts, so you must clear it in order for it to display your overrides.
I want to migrate all views from my local site to another site.
I know there is a module "Migrate" which allows you to do data migration but I don't know how to use it.
Can you give me some tips?
Thanks in advancej
Not sure what you mean with migrating views to another site. In Drupal, the migration concept is usually associated with actually migrating data - a view is actually just a way to query and display this data.
Typically moving a view to a different site, assuming data structures are the same in both can be accomplished by either exporting the view (one of the options while browsing the views on admin/structure/views) or, if it's not just a one of, by featurizing it which is a process that takes a few more steps.
It's only applicable for drupal site to drupal site
First download features module and enabled in both sites.
Go to admin-structure > features > create feature.
In that you can see General information(left side) and Components(right side). The General information provide some name in the name fields and you can see views in Components. You just select what are all views are needed for that site.Click the Download feature button.
It will downloaded!!!
After that copy the downloaded file to new drupal site which has drupalroot > sites > modules.
Go to your "new drupal site" as (Admin-Structure > feature). You can see the folder name as list in that. Enable the folder name list and click "Save settings". After the save setting finished as good then deselect the folder list, click "save settings" and delete the downloaded folder in module folder.
Note:
The folder name list should not state as conflict. If it presents, then click the recreate button.
I've a copy of DotNetNuke website on my local machine in which I've added few pages and created new modules.
I've to move these new pages to production so have copied the pages to respective folders. I know there are few database entries that are also to be made on production database to recognize these pages and modules on production.
Please tell me how I can register these pages on production website
I searched on Google but may be I'm not getting the right keywords to search. Currently I've to restore my local db to production to run those pages. I'm using version 7 of DNN
This isn't something that DNN handles very well, publishing from a local environment to production.
The most common way (Besides backup/restore of the database) is to use page Templates. You can "Export" a page in DNN, that will generate an XML document with the modules and content referenced into the portals/#/ folder (where # is the portal id)
You can upload that file to your production site (same path) and then create a new page based on that page template.
Your question implies that you are creating .aspx files and copying those to the production server. That really isn't the way that DNN works, and you probably are creating a real mess.
How did you create the pages on your local site? Did you use the DNN functionality to create new pages, add modules to those pages, etc.? Or, did you do something else?
Use the built-in funtionality to create pages on your local installation and, as Chris
To add modules - Go to your web site in production, login as super user, and install the module, then go to the page in the web site and add it. The same as you would do with 3rd party module. This will properly add the info to db.
To add pages - You could do it within the code, using the
To create DNN page (the tab):
TabController tbc = new TabController();
//...populating the page's info
tbc.AddTab(destinationTabInfo);
To create ascx control as global (meaning doesn't belong to any module) ModuleControl.
var moduleControl = new ModuleControlInfo
{
... populate the fields
};
ModuleControlController.AddModuleControl(moduleControl);
I have thousands of pages which i need to export from qa to production. I have seen the export page function but is there a way to do this in batch? I have found code to create pages but not to extract them. All permissions and settings must also be copied.
You could use the Portal Templates (export) feature found under the Host/Sites page.
That will generate a template for the site, then you could transfer that to production (that would be a couple of files) and "apply" that template to your existing site.
The other option would be to backup/restore the database, that is how most people handle changes between staging/production. Though that assumes any changes already made in Production exist in Staging.
Here is what i did;
I made a wordpress website and i wanted to copy this to another site.
I made a backup of all the files and the database.
I changed the links to the new site.
Then i imported the database to the new site.
I installed wordpress on the new site.
But it seems that the new theme and database isnt showing.
Does anybody know what im doing wrong?
Thanks in advance
I did this just recently. I downloaded a plugin which allowed a full export of the wordpress site. I then installed a clean wordpress site on the new site and then imported the old data into the clean site usingthe import function in wordpress. It asked to map old user to new users and that was it - new site up and running. It seems this is built into WordPress 3.x
I think your problem was loading the database with the data and then installing wordpress. The way I described above took just a few minutes and was foolproof.