| Conditions | 2 |
| Paths | 2 |
| Total Lines | 17 |
| Code Lines | 9 |
| Lines | 0 |
| Ratio | 0 % |
| Changes | 0 | ||
| 1 | <?php |
||
| 22 | public function preProcess() { |
||
| 23 | global $ID; |
||
| 24 | global $INPUT; |
||
| 25 | |||
| 26 | // when logging out during an edit session, unlock the page |
||
| 27 | $lockedby = checklock($ID); |
||
| 28 | if($lockedby == $INPUT->server->str('REMOTE_USER')) { |
||
| 29 | unlock($ID); |
||
| 30 | } |
||
| 31 | |||
| 32 | // do the logout stuff and redirect to login |
||
| 33 | auth_logoff(); |
||
| 34 | send_redirect(wl($ID, array('do' => 'login'))); |
||
| 35 | |||
| 36 | // should never be reached |
||
| 37 | throw new ActionException('login'); |
||
| 38 | } |
||
| 39 | |||
| 41 |
Adding explicit visibility (
private,protected, orpublic) is generally recommend to communicate to other developers how, and from where this method is intended to be used.