Update Drupal from non-server computer - drupal

I am working on my drupal site from the non server computer. It is outdated and needs to be updated (from drupal 6 to 7). I am an admin on this site and i have all the credentials. Can i update drupal 6 to 7 from a computer that does not have the drupal directory on it? (i.e from the drupal site on a laptop) Every time i click download on the recommended update it just downloads a .tar.gz file. Can somebody point me in the right direction?

You cannot upgrade your drupal 6 live site by simply clicking on an upgrade to D7 button.
Drupal is a modular system. If you upgrade the drupal core to version 7, all contributed and custom modules must be replaced by D7 counterparts. Even worse, Drupal 7 differs conceptionally from Drupal 6. An upgrade to D7 is possible, but not in an automatic process. You have to do the complex upgrade process by hand.
Your question suggests that you should probably stay with Drupal 6.

Related

when I update Drupal 7 to Drupal 8 what will happen for my Modules?

Currently running the 7 versions of Drupal to my website and most of the modules are the same version but recently I noticed Drupal 8 series is available. If I upgrade the code to the latest version, what will happen on the modules?

How to manage a remote Plone site from my local Plone 5.0?

My team has developed a Plone site using 4.3 and put it on a virtual server. Although I am able to manage many settings as an admin user through the Plone site over the server, when I try to install more add-on and themes to the site, I realize I don't have its buildout nor any file on my Plone5.0 folder. Is there a way for me to pull down that Plone site to my local machine, and create an identical site using Zope instance? Thanks!
Buildout is not 'managed' TTW (through the web), you must have access to the server filesystem where the Plone is hosted. The buildout automates the installation and/or configuration of Plone and their additional components (like a webserver, cache service etc.), but not only Plone, and many other softwares built with python (or not).
From buildout.org website: "Buildout is a Python-based build system for creating, assembling and deploying applications from multiple parts, some of which may be non-Python-based."
In your case, you can't simply manage a Plone instance in 4.3 through another remote one in 5.0 (not even with same version, as far I know). Well, at least, not without ZEOCluster (and the versions should match).
The unified installer from Plone.org is based on buildout and is well commented (check for files named buildout.cfg, base.cfg, develop.cfg etc.).
To upgrade your plone site from 4.3 to 5.0 you can check this link: http://docs.plone.org/manage/upgrading/, section "Upgrading Plone 4.x to 5.0" The migration should be more simple than older versions like 3.x or 2.x.
You also can use collective.transmogrify (and friends - jsonify, dexterity, filesystem etc.) to 'copy' contents from your live plone 4.3 to a local development in 4.3. In most cases, those tools are recommended for large Plone sites (less than ~100 contents can be a overkill), in my opinion. So, then you can upgrade the 4.3 instance to 5.0 locally. That's the roughly way to do so. Anyway you should have access to the buildout on both Plone instances (local/remote) and a good knowledge of the Plone ecosystem (Zope, ZoDB, Python etc.).
Check if your Plone instance contains content types developed with Archetypes (AT), because, Plone 5 uses the Dexterity content type as default, no more AT. The builtin content types in Plone (folder, file, image etc) can be upgraded by plone.app.contenttypes, but custom content (add-ons) should be migrated by a developer or their maintainer.

Updating plone addons on several sites at once

I have a plone instance containing several plone sites.
Whenever I upgrade plone (ex. from 4.2.1 to 4.2.3) there are some addons which need to be updated as well. My own local products need to be updated from time to time as well.
I usually go into the zmi quickinstaller folder reinstall them one by one. However having 18 plone sites in this particular plone instance means that now I have to update the addons for every site manually.
Is there a product or script which would automate the update of products/addons?
The addon ftw.upgrade provides a view (##manage-upgrades) which lists all addon-upgrades for this plone site (in an order based on dependencies) and you can upgrade all addons for one plone site with a single click. Scripting APIs and upgrading of multiple sites are in development. Upgrading the plone version is not supported, that's the job of the plone migration tool.
The addon collective.upgrade does a similar job and has already scripting support and I think it can also upgrade plone sites, not just addons.

Advice for upgrading of website with ASP.NET 1.1 and CGI-BIN code

I am maintaining an internal website for handling our business. The website is running on a Windows 2003 server that is five+ years old and is using both ASP.NET 1.1 and even older CGI-BIN code written in Visual Basic 6 with some other components like Crystal Reports. Also, it is using MySQL 5.0.27 as database.
As the website is hard to maintain, poorly written code, I would like to upgrade it to a modern version of .NET. I have already written some new functions in 4.0 and also tried MVC and Razor which I like. The question is then, how shall I proceed to upgrade the website?
Can I use .NET 4.0 on the old server in parallel to .NET 1.1 and then do a rewrite page by page?
Or should I do a total rewrite? (Which would be very nice but hard to do as I still would have to maintain the old site.)
My ultimate goal is to make the webpage easier to maintain and easier to move to another server before the current breaks.
Yes you can run 4.0 side by sdie with 1.1 as described here. If you have a testing server or a development machine i would load/install dot net 4 on that machine and just rebuild the site in asp.net 4.0 while still maintaining the 1.1 version once you have completed the new version then take down the old version and upload the new version.

upgrading a feature from drupal 6 to drupal 7

I need to use features created by me on a drupal 6 website over a new drupal 7 instance. Is there a way to port drupal 6 features to drupal 7.Or will upgrading the website give me d7 version of the features..??
Upgrading your site and then recreating the features will give you Drupal 7 versions of the features if Features 7.x-1.0-beta3 provides an upgrade path from Features 6.x-1.1.

Resources