I have an application which loads some external data based on gremlin.
I want to use it to load the data into a Neo4j database.
I saw that there was partial support for gremlin in previous versions but couldn't find any solution for latest version.
I'll be happy to hear if it is still possible and how can it be done.
At this point, TinkerPop expects to support 3.4.11 in its future 3.5.0 release (here) which is yet several months away. For TinkerPop to support 4.0 it would need a fresh release of the neo4j-tinkerpop-api-impl to be released with that version. It seems an issue has been created for that here.
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.
I have an umbraco WebForms projects built on 4.11.10 that we need to upgrade to 7.3.8.
We have tools such as RedGate Data Compare and RedGate Structure Compare, but without firsthand knowledge of the new structure and how that has affected the way that data is stored we're finding it impossible to upgrade the database.
Does anyone know of a SQL script or tool that will upgrade just the database to the new format?
Thanks in advance for your time.
dotdev
Recent changes in 7.3 greatly improved the experience (and success) of upgrading from older versions.
Incredible engineering by the Umbraco core team, the new installer
just upgraded a 4,5 year old v4.7.1 db to v7.3 flawlessly #h5yr
https://twitter.com/umbraco/status/643721449295974401
This blog post contains some more details on performing an upgrade from 4.7.1 to 7.3.
I'm just trying to understand the factors that are considered to decide that an application written in a lower version needs to be upgraded.
I would like to think it comes down to these factors:
The Rails team is pretty active and they remedy Rails core security issues as soon as they come across one. It would be nice to have your Rails version always updated which means your have all the security issues of the past addressed as well as open to further updates if they come along. You would not want an older version of Rails get in the way of a security update.
There are always performance improvements in almost every new version of Rails and optimization is an area to work in for Rails apps. You should take advantage of them by keeping your Rails version updated.
Its not only the Rails version, the underlying Ruby version also receives updates and performance improvements. The updated version of Rails makes use of these.
There is also the gem dependency issue. Gems also receive updates and security patches and at times, newer versions of these gems are not compatible with an older version of Rails.
It is easier to upgrade a Rails application to its next version than to its next|next|next|next version. Blog posts and migration guides are always online but if you are coming from a very very old Rails version, they will become very hard to follow.
Newer versions of Rails provide functionality that is not available in the older versions of Rails. It is always nice to have this functionality at your disposal. You never know you may need it in your project.
I made an example project in grails 2.3.8. How to upgrade to the newest version? No way to downgrade from version too?
It really depends on the differences between the versions. In a lot of cases you will get away with simply editing the version number in the application.properties file at the top of the project. There used to be a grails upgrade command which attempted to do some of the work for you but that approach proved to be problematic for a number of reasons so it was removed in Grails 2.4. The normal upgrade procedure now is to edit the version number, which can be done using the grails set-version command (which just updates application.properties, see http://grails.org/doc/latest/ref/Command%20Line/set-grails-version.html) and then reading release notes for any other particulars related to that release. Often the release notes suggest updating some specific plugins to specific version numbers for compatibility.
Downgrading generally could be done with the same approach. Depending on what is in your application you might run into problems going backwards in versions.
I hope that helps.