I got a DOTNETNUKE project. I am new to DOTNETNUKE. My client has given me the files and folder with Database(say abc.mdf). I was said to upgrade their developed site from version 6 to latest version v7.0. The issue when upgrading is "How to map the latest version to existing Database?" ie: when I installed v7.0 in my system, it creates new database with 137 default tables. How am I supposed to map those 137 default tables, stored procedures, etc to existing database(abc.mdf) so that up-gradation happens easily with database.
I didn't find a proper solution for that..
Can anyone help me?
Thanks in advance.
No need to map any tables OR files from new version to old version. Just follow up below steps to upgrade DNN website from old to new one. Here is the reference link.
Download 7.4.0 - Version Upgrade file from here.
Extract downloaded Zip file to root of your existing old version of DNN website. It is replacing all your old files with new one.
Run your website.
When you run your website, it will be automatically redirect to Upgrade Wizard page.
Just provide your HOST Username/Password and Click on Install button.
Now it will start process of mapping your old database tables & store procedures with new one.
After complete the process to 100%, click on Visit Website button.
Done. Your website updated.
Please let me know if you have any questions.
DNN will do all that for you.
Extract the UPGRADE package over your existing site. Hit the site, login as host, run the Upgrade.
Related
When the content is modified in the Portal , a new version is created and Published and this becomes approved Version . Yet when we restart the liferay server ,all modifications are lost in the new version. Please help me out to get this sorted.
This issue seems not solved yet after doing the below change too.
Please help me out
If you're using ressource importer, you must disable developer mode in resource importer configurations.
Go to :
src/WEB-INF/liferay-plugin-package.properties
and then update the property.
resources-importer-developer-mode-enabled=false
I am new in magneto. my store var 1.7.0.2 need to update security patch(UPEE-6285).
I read many link without with ssl or without ssl install. but can't go with any one because i can't get backup my project and i want to go for easy steps can any one tell me easy steps for update security patch in magneto. I don't know what is ssh and how it run.
Please help me
Thanks
To learn how to install a patch check this link out: https://info2.magento.com/rs/magentoenterprise/images/Installing-a-Patch-for-Magento-Community-Edition.pdf
Easy way:
First create a backup then use Magento connect and upgrade your store to the latest Magento version by check for upgrades button. The latest version contains this security patch (SUPEE 6285) and another features all together.
update:
Upgrade using Magento connect on production server is not recommended, because you have to check extensions compatibility.
I have a small solution that is composed out of 2 main projects a Mvc4 Web Api and a silverlight 5 Application. I've configured and deploy the application initially on the Azure platform and it all went great, but ever since when I deploy again the silverlight project does not get pushed and the online site has the old version.
I should mention all works great with the azure simulator on my local dev machine.
Anybody had a similar issue?
Regards,
I would suspect first (as Simon suggests) that the browser likely still has the previous client cached and loads that instead of downloading your new client.
You can use the version number in the code on your page that hosts the silverlight app to help. While it's easy for you to clear the cache - you don't really want to have to tell users to do that whenever you update.
Set the version to whatever your latest assembly version is (silverlight client project assembly), this will force the browser to download the client if the cached version is a lower number.
<param name="source" value="AppPath/App.xap?version=2.0.0.6"/>
Ok,
So after pulling my hair out, I finally figured out.
I have to change the build configuration to release in VS do a rebuild and then do publish because apparently the azure project does not do rebuild on the project when you publish it.
To solve this issue you'll need to identify the source of the problem (is it a client side problem where you have a caching issue or not). Even though you say caching isn't the problem we'll need to be sure about this first.
What I suggest is that you do the following first:
Activate Remote Desktop on your role
Connect through RDP and save this file to the role: http://support.microsoft.com/kb/841290 (fciv.exe)
Find the *.xap file (usually in E:\sitesroot) and get its checksum (using fciv.exe)
Modify the Silverlight project locally (maybe change a label or move around an element) to make sure its hash has changed.
Redeploy the application
Connect through RDP and use fciv.exe to get the checksum of the *.xap file once again
Compare both checksums
If the checksums are different, then it means that the deployment worked correctly and the Silverlight xap has been updated. If the checksum is the same, the problem lies with the deployment.
Please let us know the result so we can help you find the solution.
I am working SDL TRIDION 2011 SP1 version. Suddenly I am unable to see the Trdion site in Internet Information Services(IIS) Manager. Please tell me the procedure how to get it back again.
Remove Tridion Completely (uninstall), then run the installer again.
You won't loose any data (it's all in the database), and you're likely to get your server up and running way faster than trying to fix by hand.
As #bart suggested, your best option to get the web application back (assuming it really has gone), is to run the repair option with the installer. There are a lot of folder specific settings which would be very hard to recreate manually.
I have taken the backup of my live portal and I want to upgrade it to newer version in localhost and then move the upgraded version to my live site.
I followed the steps in the link http://www.liferay.com/community/wiki/-/wiki/Main/Upgrade+Instructions+from+5.2+to+6.0. and my stpes are :
1) I have setup the new liferay 6.0 on my localhost
(successful installation of liferay 6.0 with inbuilt Hypersonic database )
2) I have imported MySql database of live system to the local MySql Server.
3) After stopping the tomcat server, I have changed the configuration file portal-ext.properties for the MySql database details.
4) Then, I have started the start.bat file. It is showing upgrade process well but after few minutes window is closed
Can anyone help me in this regard where I have done some mistake or am I missing something during the upgration. If anyone has some idea then please share their steps.
Thanks in advance
You don't mention that you also copy your document library / image gallery folder to the new installation. This typically (unless configured otherwise) sits in your "data" folder. Just importing the MySql database isn't enough, as it contains only the metadata for doclib & image gallery.
You'll have to take this into account for backups also - ideally you'd read about backup and set up a second 5.2.3 instance (and make sure it runs) from your backup, then start upgrading. I typically forbid to call something a backup if nobody ever demonstrated, that they can use it to successfully restore in a completely new environment. This is your chance to ultimately test your backup procedure.