It looks like the subscription/unsubscription requests are sent with the newest first and the oldest last rather than the other way around. This causes issues when, for example, a user subscribes and then immediately unsubscribes within a short period of time. The unsubscription will be processed before the subscription resulting in errors and an incorrect subscription status for the user.

A fix should be relatively easy. Just change the ORDER BY in emf_db_get_requests() to ASC.

Comments

davyvdb’s picture

Status: Active » Fixed

thx. fixed in cvs.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.