hi,

I'm looking for the fastest method to upgrade PHPEd without losing my existing work-spaces and projects already setup in the old version. I also have ftp sites setup and many other settings - is there a way to upgrade and have all your settings (made over many years) applied to the new install.

Thanks in Advance ....

I have only been a user of phped since about version 9.x, and have since upgraded through the v10, v11, and now v12 versions with success each time. All of my projects, site settings, code snippets, etc have been retained along the way. There was one glitch with custom shortcuts within the v11 series but that was quickly resolved.

Of course nothing beats retaining a backup though prior to upgrading.

@probc1 :
Hoped that was the case - though as you state "nothing beats retaining a backup" ( Windows restore-points rock!! ) though ill probably backup the entire PHPEd directory from app data etc ....
cheers

Have a look here.

As above, PhpED handles most of it itself now, especially now that it migrates previous version data to the latest installed version (so any custom colours etc will also make the transition)... but the above link will provide an easy way to (maintain) backup(s) for your PhpED install(s) and will also help if you wanted to copy your settings between multiple boxes.



Cheers..

Ian

We do our best to support upgrades as smooth as possible. It means that new version preserves settings and data. Some people call it backward compatibility -- each new version can be installed on top of the previous, that's the case with PhpED.
But it's almost impossible to preserve FC (forward compatibility). For example, if we change format and/or structure of the files, new version supporting it, is aware of the old format and it can upgrade the file(s) as a part of the installation process. At the same time, previous version can't be aware of the future changes and therefore it can't downgrade the format of the files. If you install new version and run it, all files are already converted. If after that you attempt to run previous version, it will most definitely fail if such changes in format(s) are made. If old version can't load config files, it will either terminate with fatal error or just drop the file(s) that it can't load to the defaults. So, it's always good idea to make backup of settings in
%APPDATA%\nusphere\config
and cleanup two temporary data directories. Unfortuantely their path can't be directly accessed from the environment like %APPDATA%, but you can take it from the registry:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
copy value from "Local AppData", and append first \NuSphere\PhpED\, then \Mozilla Embedded Browser\ to get these two directories respectively.

hi,

Yes i backed up the Nusphere directory in %APPDATA% and thats all, taking the opportunity to get rid of some old, defunct workspaces and projects still loitering about. The install process found everything and as 'probc1' said all setting were saved and restored (thankfully).

@Ian.H - Ill give your solution a look for the next upgrade - thanks for your link.


BTW:
[1] Is there a way to delete all of those old unused Workspace and Project references - it would be a good idea if we could remove them from within the IDE.
[2] Id really like to see phpEd remember the current open files in the IDE when working on an FTP remote site. Simply remember the open documents so they are opened automatically the next session without specifying WorkSets.


thanks all