Quote by: cordiste
I was thinking to new users (geeklog 1.6 and higher) who need to downgrade (I never needed this feature ) and he do not known nothing about manual upgrade or downgrade.
But after all, maybe the plugin manager can downgrade a plugin with the upgrade function if we choose an older version?
The problem is the plugin writes all the code to do upgrades. You aren't going to find a plugin author who is going to spend time writing downgrade functions. For one thing they are guaranteed to be buggy because it is not something you'll be testing very often or very rigorously. Again, this is not something simple for the repository/upgrade code to handle. How would it store a snapshot of the system before the upgrade? Some plugin upgrades involve row level changes to entire tables. How do you reverse that? What if a field is dropped? What could be done to recreate the data in the dropped field?
All I'm saying is this is not going to be a problem 99% of the time. I don't think finding an automated solution for this is proportional to the amount of usage it would see. When those post-1.6 only users have this kind of problem, they will have to learn about Geeklog under the hood.