Esempio n. 1
0
 /**
  * Install the MUBoard application.
  *
  * @return boolean True on success, or false.
  */
 public function install()
 {
     parent::install();
     $uid = UserUtil::getVar('uid');
     MUBoard_Util_View::actualUser($uid, 1);
     // update successful
     return true;
 }
Esempio n. 2
0
 /**
  * Listener for the `module.users.ui.login.succeeded` event.
  *
  * Occurs right after a successful attempt to log in, and just prior to redirecting the user to the desired page.
  * All handlers are notified.
  *
  * The event subject contains the user's user record (from `UserUtil::getVars($event['uid'])`).
  * The arguments of the event are as follows:
  *     `'authentication_module'` an array containing the authenticating module name (`'modname'`) and method (`'method'`)
  *       used to log the user in.
  *     `'redirecturl'` will contain the value of the 'returnurl' parameter, if one was supplied, or an empty
  *       string. This can be modified to change where the user is redirected following the login.
  *
  * __The `'redirecturl'` argument__ controls where the user will be directed at the end of the log-in process.
  * Initially, it will be the value of the returnurl parameter provided to the log-in process, or blank if none was provided.
  *
  * The action following login depends on whether WCAG compliant log-in is enabled in the Users module or not. If it is enabled,
  * then the user is redirected to the returnurl immediately. If not, then the user is first displayed a log-in landing page,
  * and then meta refresh is used to redirect the user to the returnurl.
  *
  * If a `'redirecturl'` is specified by any entity intercepting and processing the `module.users.ui.login.succeeded` event, then
  * the URL provided replaces the one provided by the returnurl parameter to the login process. If it is set to an empty
  * string, then the user is redirected to the site's home page. An event handler should carefully consider whether
  * changing the `'redirecturl'` argument is appropriate. First, the user may be expecting to return to the page where
  * he was when he initiated the log-in process. Being redirected to a different page might be disorienting to the user.
  * Second, all event handlers are being notified of this event. This is not a `notify()` event. An event handler
  * that was notified prior to the current handler may already have changed the `'redirecturl'`.
  *
  * Finally, this event only fires in the event of a "normal" UI-oriented log-in attempt. A module attempting to log in
  * programmatically by directly calling the core functions will not see this event fired.
  */
 public static function succeeded(Zikula_Event $event)
 {
     $user = $event->getSubject();
     $uid = $user['uid'];
     MUBoard_Util_View::actualUser($uid, 1);
     MUBoard_Util_View::actualPostings($uid);
 }
Esempio n. 3
0
 /**
  * Post-Process the data after an insert operation.
  *
  * @ORM\PostPersist
  * @see MUBoard_Entity_Base_Posting::performPostPersistCallback()
  * @return void.
  */
 public function postPersistCallback()
 {
     $createdUserId = $this->getCreatedUserId();
     MUBoard_Util_View::actualUser($createdUserId, 2);
     $args['id'] = $this->getId();
     $parent = $this->getParent();
     // does not work bug in MOST TODO
     if (isset($parent)) {
         $args['parent'] = $parent->getId();
         $args['title'] = $parent->getTitle();
     } else {
         $args['title'] = $this->getTitle();
     }
     $args['text'] = $this->getText();
     MUBoard_Util_Base_Abonnements::aboMailing($args);
     $args['text'] = str_replace('\\n', '<br />', $args['text']);
     $this->setText($args['text']);
     $this->performPostPersistCallback();
 }