Can you please guide me through updating Umbraco from version 4.5.2 to version 4.11.10(or best version in 4.11.xx)..
Custom changes i currently have in my website:
Add 2 new areas to config/Dashboard.config to display custom usercontrols(these areas are displayed in content section)
Custom usercontrols, i uesd as datatype in my pages(my controls are derived from umbraco.editorControls.userControlGrapper.IUsercontrolDataEditor).
so steps i have to do to upgrade Umbraco and keep my site running normal.
I have upgraded between similar versions before by overwriting the /bin files and deleting the stuff like umbraco.config & examine indexes that get rebuilt when they are deleted.
The official site has a version specific upgrade path that seems logical enough: http://our.umbraco.org/documentation/Installation/Upgrading/version-specific
But, I'd question why you would upgrade from 4.5 to 4.11 - as Niels Hartvig has often stated, there is no real upgrade path, its just a series of overwrites and deleting what gets deprecated. I guess you're looking for razor support - but with v7 imminent I'm not sure that an upgrade within the v4 family of releases has a long enough life span to justify it. Why not stick with v4.5 until you're ready to completely rewrite in MVC in v6 or v7?
Related
What is the difference between umbraco and vanila umbraco.
i'm currently using umbraco 6.2.1 version in my website.
Any special procedure available for upgrading this version to Vanila umbraco version.
Vanilla Umbraco means a fresh clean installation of Umbraco, without any customization.
Vanilla is a general term used for software, see also on wiki
Related to upgrading, one approach is to do a new installation of Umbraco (we can called it a vanilla installation) and then deploy your code, and migrate the content. Instead of the General Umbraco upgrade instructions.
I'd say that there is no running website with a vanilla Umbraco install. Umbraco is not a typical CMS. You are customizing it as soon as you start setting up your site in it. This is partly due to a choice on the Umbraco HQ team's decision to store their settings in the same files where you change settings by using Umbraco, requiring you to merge certain files during the upgrade.
As for upgrading, I'll warn you, there are a few ways to install Umbraco (Web PI, Nuget, Zip file), and if you upgrade in a way different than you installed, it can be hell. Step one, back up your site (front-end file-system files and db)! If you did not install Umbraco via Nuget (in Visual Studio), do not upgrade via Nuget. You will regret it.
Umbraco upgrades are a problem.
If the versions are minor running the update-package umbracocms nuget might work, but it often leaves the project mismatching version assemblies elsewhere.
Upgrading Umbraco is a bit of a minefield. Soz
Umbraco is now at version 11 and have moved their code base from the .NET framework into .NET core. Newer version is offering so much more, block-list, block-grid, inline editing, so many new and improved property editors. Editing experience and working with the CMS has changed so much since version 6.
Vanilla Umbraco would a term for a non-configured, fresh install.
You can find out everything you need to know about Umbraco on their documentation pages.
https://docs.umbraco.com/getting-started
Umbraco is a free open source project so there is no cost if you want to roll your sleeves, dig in and move over to the newest version. There are some paid offerings as well that would give support if you needed it.
Now that they have moved away from the .NET framework and moved their code base over to .NET Core there is no longer a direct path to upgrade from version 8 and earlier to the most recent version 11.
I would recommend you set up a fresh install, configure and customize as desired and then move any relevant content over to your new site.
There are many articles out there detailing how others moved over to the newer version.
Good article here on how they upgraded from version 7 to the newer version 11.
https://skrift.io/issues/how-i-upgraded-my-umbraco-v7-project-to-umbraco-v11/
Worth the read if your planning on going down that path.
Good luck.
Does anyone know if DateFolders (and AlphabetFolders for that matter) is working on Umbraco 6.2 or 7.x?
AutoFolders should work in v6 (and supports alphabet folders too). I'm one of the devs that is currently maintaining the project and we have it running on various v6 instances (I haven't tested it on 6.2 yet, but nothing has changed that should break it).
Autofolders WON'T work on v7, but for v7 you could use a Container Document Type, which does away with some of the need for Date Folders.
Recently I have been working on a website using a trial version of DevExpress with the latest version of Entity Framework, but my trial has run out. Is there a free alternative anyone knows of that I could use in it's place? I'd like to keep the whole MVC flow going.
DevExpress only provides extensions for (and not the root of) MVC. As long as you can go without the extended versions of the charts, tables and other controls you'll be fine. Otherwise, if you're that dead-set on their controls or have a lot invested you may look at just purchasing the package.
Also, to be clear, EF is a freely-available library (if you have NuGet it's very easy to obtain) so anything relying on that is safe:
Install-Package Entity-Framework -Version 5.0.0
That would install the latest solid build to your project.
I have a Symfony 1.2.4 application, taken and modified from the Symfony sandbox application, there was no effort made to make sure that the Symfony engine was separated from my application, so now the Symfony engine is just a folder inside my application.
What is the best way to upgrade from Symfony 1.2.4 to 1.2.7? Any ideas?
I have found the solution.
First, one has to move the Symfony framework from sandbox application, then upgrade the Symfony framework using PEAR as detailed in this post.
The easiest way:
download new sandboxed version of symfony, take data and lib fonders from that archive and out it in your project folder (overwriting existing data and lib folders). after that clean your projects cache and rebuild model (and forms and filters).
php symfony clear:cache
php symfony propel:build-all
or if using doctrine:
php symfony clear:cache
php symfony doctrine:build-all
this will always work for minor revisions ( 1.2.3 to 1.2.9 or 1.1.2 to 1.1.5). for upgrades from 1.0 to 1.1 or 1.2 or 1.3 you will have additional steps ( you have detailed instructions for that in documentation)
You should also consider using SVN and/or installing symfony in the lib/vendor folder of your project. This will make symfony project dependant which is just useful in case of multiple symfony projects on the same server.
Symfony 1.2 is a Stable version, what does it mean?
Stable : The symfony team is commited to fix bugs and security
problems for stable releases until the
end of the maintenance. In average, we
release a bug fix version a month.
These versions never contain new
features, even small ones, but only
bug fixes. So, they are always
backward compatible, easy and safe to
upgrade to.
Like Oncle Tom said, if you're working on multiple Symfony projects, it will be easier to update them if they're sharing the same Symfony library.
Checkout the Symfony lib from the SVN Repository :
daemon#dev:/home/dev/symfony$ svn co http://svn.symfony-project.com/branches/1.2
Edit your config/ProjectConfiguration.class.php :
#require_once dirname(__FILE__).'/../lib/vendor/symfony/lib/autoload/sfCoreAutoload.class.php';
require_once '/home/dev/symfony/1.2/lib/autoload/sfCoreAutoload.class.php'; // use the shared lib instead
sfCoreAutoload::register();
class ProjectConfiguration extends sfProjectConfiguration
{
public function setup()
{
// for compatibility / remove and enable only the plugins you want
$this->enableAllPluginsExcept(array('sfPropelPlugin', 'sfCompat10Plugin'));
}
}
Then you're done. You're now using a shared and easy to update Symfony library, and you have updated your project.
To start new projects :
daemon#dev:/home/dev/sfProjects$ php
/home/dev/symfony/1.2/data/bin/symfony
generate:project Project
This is an old question, but I thought I'd add a thought. It was previously considered best practise to have a single location for symfony on a server, as one could upgrade that and magically upgrade all sites on a single server. In practise, it's not that easy. Firstly when moving sites from one server to another, one potentially has to repair symlinks or absolute paths to library folders. Also, as #deresh says, one needs to clear the cache between upgrades - which takes time on multiple projects, and may bring them down until they are all done.
So in summary, these days I embed symfony 1.x in any symfony project, rather than referencing an external location. It brings a "known good version" of symfony into version control, makes it easier to deploy, and upgrading is just a question of deleting lib/symfony and data/symfony in a development copy, and replacing them with the lib and data folders from the new tarball. These should be committed and then the project can be deployed on the server easily - svn up and `./symfony cc' if you're using Subversion on the server.
In general you don't need to rebuild your models, unless you know that the version of your ORM has changed between symfony releases.
I have a small ASP.NET MVC application developed using the latest beta version.
What would be an easy to follow step-by-step guide to upgrade to the RC released yesterday?
What key changes would I have to apply to get it working in the new version?
Read the release notes, the steps to follow are listed there.
Repeated here for your convenience.
There are not many changes between the Beta and the RC releases. However, you will need to make a few changes to your applications after installing the Beta release. Most of these changes are apparent when you try to compile your application by using the latest release, so we do not list every possible change.
The following list describes some of the changes that you must make.
Update the references to the
following assemblies to point to the
RC versions:
System.Web.Abstractions.dll
System.Web.Routing.dll
System.Web.Mvc.d
ll
Note If you are running ASP.NET 3.5 SP1, you need to update only the System.Web.Mvc assembly reference.
By default, these assemblies are located in the following folder:
%ProgramFiles%\Microsoft ASP.NET\ASP.NET MVC RC
After you have made these changes, compile your application and resolve any compilation errors. Most of the errors will be the result of one of the breaking changes listed earlier.
Update the section the Web.config file In the Views folder to match the following example. (The changed elements are in bold.)
I think the release notes has a fairly good guide.
There's some issues not mentioned in release note. Read this for more info:
http://forums.asp.net/t/1377139.aspx
You also make sure to add the following tag to your web.config file:
<system.web.extensions/>
It took me a lot of effort to figure it out since it's been nowhere documented.