@KirkM,
Yep, your post is really off-topic.
In general, Odin Team gets bug reports, proposed bug fixes and so on. It takes time to implement them and, moreover, there is a development policy that can hinder implementation.
No disappointment on my side there, it is just a normal process.
Nevertheless, I am "angry" about the fact that basic errors are still introduced in new packages and/or new releases,
if these errors already have been fixed in the past.
As you know by now, Plesk Customers do report issues with specific packages, including the packages with unnecessary bugs.
As a result, three things occur:
a) the Plesk Customers are mentioning issues or alleged issues AND Odin Team investigates most or even all of them, in order to improve Plesk by micro-updates and/or new packages,
In essence, Odin Team becomes focussed on a lot of issues at the same time, which require investigation.
The simple result is that more emphasis is on bug identification than on bug fixing, as such a natural effect of this forum.
b) the Plesk Customers are communicating with Product Experts and/or Odin Team, as such not always the best method to get bugs fixed directly.
In essence, it is a one-sided communication and that is not the best practice to get micro-updates fast.
c) the Plesk Customers are inclined to return to the last Plesk installations that worked for them: in your case the upgrade to 12.5.30 was postponed.
In essence, this inclination of customers results in the problem that many bugs in new Plesk releases are not identified or not identified fast enough, making it even more acceptable that new Plesk releases are not adopted by Plesk customers, which in turn aggravates the problem of bugs not being identified.
In conclusion, it is a precarious balance of development, customer feedback, bug investigation and bug fixing.
In the current situation, the precarious balance is not in favour of either Odin (Team) or the Plesk Customer.
That is a shame, that is the part that I am "angry" about, since improvements to the whole process can be made easily.
Now we can turn to your explicit questions of "why did I not report the solution?".
A simple answer suffices: the solution I found is not a solution, but a work-around.
The actual solution has to be implemented within the Plesk core code and that is really the task of Odin Team.
Why did I not mention the work-around?
Really, if I have to say that in most cases the worst-case scenario of "migrating per domain, several times, in between adjusting IP addresses and repeating the process many times for each domain" has to be implemented, than this "work-around" is not a solution that I want to bother Plesk Customers with.
Remember, it is the task of Odin Team to prevent this beforehand, not resolving the issue afterwards (and in the meantime relying on Product Experts/Plesk Customers to provide temporary "solutions").
Also, remember that you yourself have chosen to not use the migration manager, making the whole "work-around" (and mentioning thereof) really obsolete.
You know, I also do not get one thing about your statement.
Due to some minor issues with migration (in a migration process that is far from practical and/or adviceable, moving a 12.0.18 instance to a 12.5.30 instance), you are now not using the Plesk 12.5.30 version, even though you have paid for a license that allows this upgrade and, moreover, even though the upgrade is really adding value to hosting services.
You are paying for Plesk components, such as the migration manager, that does work for across-platform migrations and many other types of migration,
with the exception of the types of migrations that entail Plesk-to-Plesk migrations.
And you are not bothered about that?
Please note that the Plesk Migrator was originated as an extension to Plesk 12.0.18 and intended to be a cross-platform migration tool, functioning
alongside the Plesk migration manager in the Plesk 12.0.18 version.
Also, please note that the before mentioned extension was already buggy.
Finally note that the Plesk migration manager and the Plesk Migrator extension have (apparently) been combined in Plesk 12.5.30, as such a strange move, since most of the intended functionality of the Plesk Migrator extension is not very valuable for Plesk-to-Plesk migrations and, in the current situation, these (non-valuable) functionalities and/or a poor integration seem to be the root cause of migrations not being executed properly.
Can you imagine that I am somewhat bothered about the whole new migration manager, certainly when taking into account that an (not properly tested) extension is included and, in essence, is breaking a perfectly "good" migration manager, as has been included in Plesk 12.0.18?
By the way, note that the old and new versions of the migration manager are, in fact, intended to facilitate small migrations (not bulk migrations) and are therefore primarily aiming at the Plesk Customers that do not have the experience to perform migrations with the plesk command line tools and/or other command line tools, such as rsync.
Can you also imagine that I am little bit bothered about the new migration manager in general, given the fact that specific Plesk Customers do need and/or want a Plesk GUI based migration tool, that has not been working properly for many months now?
Really, it is up to you determine what you think about all of the above.
As for me, I sincerely hope that Odin Team gets things right as fast as possible, with respect to the migration manager (and many other reported issues and/or bugs).
After all, customer satisfaction and/or the future of Plesk 12.5.30 depends on it.
Regards.....
Facebook
Twitter
