BurningFlipside /
Profiles
These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
| 1 | <?php |
||
| 2 | ini_set('display_errors', 1); |
||
| 3 | error_reporting(E_ALL); |
||
| 4 | require_once('class.ProfilesPage.php'); |
||
| 5 | $page = new ProfilesPage('Burning Flipside Profiles'); |
||
| 6 | $page->addWellKnownJS(JS_CHEET, false); |
||
|
0 ignored issues
–
show
|
|||
| 7 | |||
| 8 | $page->body .= ' |
||
| 9 | <div id="content"> |
||
| 10 | <h1>Welcome to the Burning Flipside Profile System</h1> |
||
| 11 | <p>This system allows you to login to the new and improved Burning Flipside website systems.</p> |
||
| 12 | <p>This system will contain all your private data seperately so as to help prevent unwanted display of your data on www.burningflipside.com. |
||
| 13 | Additionally, completing your profile on this site will enable you to complete ticket requests and sign up for volunteer shifts even faster than before.</p>'; |
||
| 14 | |||
| 15 | if($page->user !== null) |
||
| 16 | { |
||
| 17 | if(!$page->user->isProfileComplete()) |
||
| 18 | { |
||
| 19 | $page->addNotification('Your profile is not yet complete. Click <a href="profile.php" class="alert-link">here</a> to complete your profile.', $page::NOTIFICATION_WARNING); |
||
|
0 ignored issues
–
show
The method
addNotification() does not seem to exist on object<ProfilesPage>.
This check looks for calls to methods that do not seem to exist on a given type. It looks for the method on the type itself as well as in inherited classes or implemented interfaces. This is most likely a typographical error or the method has been renamed. Loading history...
|
|||
| 20 | } |
||
| 21 | $page->body .= '<h1>Need to reset your password?</h1> |
||
| 22 | <p>You can reset your password <a href="'.$page->resetUrl.'">here.</a></p> |
||
| 23 | </div>'; |
||
| 24 | } |
||
| 25 | else |
||
| 26 | { |
||
| 27 | $page->body .= ' |
||
| 28 | <h1>Need to register for the first time?</h1> |
||
| 29 | <p>You can sign up for an account <a href="'.$page->registerUrl.'">here</a>. |
||
| 30 | <h1>Forgot your username or password?</h1> |
||
| 31 | <p>You can lookup a forgotten username or reset your password <a href="'.$page->resetUrl.'">here.</a></p> |
||
| 32 | </div>'; |
||
| 33 | } |
||
| 34 | |||
| 35 | $page->printPage(); |
||
| 36 | /* vim: set tabstop=4 shiftwidth=4 expandtab: */ |
||
| 37 |
This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.
If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.
In this case you can add the
@ignorePhpDoc annotation to the duplicate definition and it will be ignored.