quip-1.2.2-pl with Revolution 2.0.4

I upgraded to quip-1.2.2-pl while still using Revolultion 2.0.4. The quip installation showed some errors regarding "modAccessPolicyTemplate" but executed with a successful statement.
But quip does not work properly any more: threads are marked as closed and commenting is no longer possible. Then I’ve tried to revert back to the previous version to quip, but this doesn’t seem to be possible. This is the error message:
"...
Skipping modPluginEvent object (data object does not exist and cannot be removed): Array ( [pluginid] => 0 [event] => OnEmptyTrash )
Could not load class: modAccessPolicyTemplate from mysql.modaccesspolicytemplate.
Problem instantiating object from vehicle
Recoverable error: Object of class xPDOObjectVehicle could not be converted to string
PHP notice: Object of class xPDOObjectVehicle to string conversion
Fehler beim Deinstallieren des Package mit der Signatur "Object".
"

How can I revert back to the previous version of quip?

-Boa

Quip 1.2.2 use methods that only exist since the last Revo release (2.0.5).

It might be possible to revert back manually but it will requier some verifications to see if there are no modification on database table with the new version.
Is it a production site ?

Luckily this is my testing site.

In this case, uninstall quip 1.2.2 and reinstall the old version.

Hm, the revert-to-previous-version deinstallation did not work. Will try to other uninstall options later today.

Just to be prepared if something like this would happen in a production environment: what would be the recommended procedure in that case?

Thanks,
Boa

Since Quip 1.2.2 bring some changes, i believe that after uninstall you’d have to flush permission and then reinstall the old permission to re-flush permission again.

And just in case, Clear your cache too.

I would not update a component thnat can be critical on a prpduction website without testing testing it locally first.
You could go back manually but you’ll loose lot of times to do so.

And don’t forget to read carefully the changelog before updates.

I didn’t have the time to check Quip 1.2.2 yet, did it mentionned the changes and possible break in the changelog.
I believe that and should have not be in the update list in the first place if he’s not compatible with your old version of Revolution.
This can be a nice feature request

The update notice mentions changes in regards to the new access policies of Revolution 2.0.5, but I did not see a notice of incompatibility with 2.0.4.

I could not get the quip uninstall to work so I decided to use an intact backup of the site and the database.

Thanks for trying to help.