Project

General

Profile

Actions

Feature proposal #2989

closed

registration triggers not executed

Feature proposal #2989: registration triggers not executed

Added by beat about 14 years ago. Updated about 14 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
15 November 2011
Due date:
% Done:

100%

Estimated time:

Updated by krileon about 14 years ago Actions #1

  • Tracker changed from Bug to Feature proposal
  • Subject changed from Facebook-logins do not propagate to JFusion to registration triggers not executed

That and anything else that uses registration triggers will do nothing as CB Connect doesn't fire a single trigger during registration. This is to be implemented with a later release. Latest changes added support for approval/confirmation workflows, but no trigger usage has been implemented yet.

Updated by krileon about 14 years ago Actions #2

  • Estimated time changed from 3:00 h to 0:00 h

Updated by krileon about 14 years ago Actions #3

  • Estimated time deleted (0:00 h)

Updated by krileon about 14 years ago Actions #4

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Also added triggers for update user in the update user function.

Updated by krileon about 14 years ago Actions #5

  • Target version set to 2.0.0

Updated by krileon about 14 years ago Actions #6

  • Status changed from Resolved to Closed
Actions

Also available in: PDF Atom