That would be absolutely great!


I'm looking forward to it...

Cheers,
Jan

Hi all..

Release 1.2.0 (build 1201) is available from the first post. This now includes a 'Migrate' tab and will allow you to migrate settings from any version to any version. I don't think there's a need for an explanation on how to do it.. but if there are any queries, please don't hesitate to ask.

Please, export your settings before running a migration. I have tested this multiple times, with multiple scenarios.. but just to be safe

Enjoy another hopefully useful release



Cheers..

Ian

Great, I'll download and install it now, then I can upgrade to PhpED 10 without having any reservations.

Thank you very much again for your helpful tool!

Cheers,
Jan

It's four months ago that I last exported my settings. Is it normal that there's a confirmation dialog showing the path to the templates?

Apart from that the export worked fine.

Cheers,
Jan

Hi Jan..

I fixed that in the previous build IIRC (certainly not in the latest release). It was a debugging message I'd forgotten to remove. As you say, the export will work just fine.. it just displays an (annoying) message to the templates path.

You should be good with the new version



Cheers..

Ian

Well, this happened while using the new version... But no problem, the main thing is, it works.

Cheers,
Jan

Argh! You're right, of course Jan... I must have re-introduced this. I'll get it fixed tonight once at home and release a minor patch as it's not right.

Glad it all worked just fine though



Cheers..

Ian

Take your time - it's just a little "optical" glitch everyone can live with for a while, I guess.

Cheers,
Jan

1.2.1 1202 released.

This removes the debugging messagebox when exporting now.. apologies about that.



Cheers..

Ian

Hi Ian,

It looks like there's a bug migrating HKEY_CURRENT_USER\Software\NuSphere\PhpED9.0\Toolbar\LastChk key from v9 to v10.

In v9 its type is REG_QWORD, and it gets imported into v10 as REG_DWORD. As a result, each time PHPEd tries to check the new version, there's a modal popup complaining about LastChk value/type.

Thanks,
Temuri

Hi Temuri..




Thanks for reporting this bug. I've fixed this now and released 1.2.2.1203.

Running the migration from 9.x to 10.x again will import the registry data types correctly (although I think this is the only one that failed, looking at the other reg types).

Apologies about this... ironically, I have a 'Toolbar' key outside of my version keys too which has my lastchk value in it (not the toolbar keys within the versioned keys), and as this doesn't get migrated as it's not part of a particular version is probably how I missed this. Anyway, the whole reg data type is now much more robust, so it shouldn't matter what they might be in the future.



Cheers..

Ian

Love it ! great work, thanks!

and in case anyone is wondering i watched for any outgoing network packets from the program and there was none, its safe and not trying to steal any of your data =)