post accesses the super-global variable $_REQUEST. Open
public function post(){
\PHPWS_Settings::set('intern','systemName',$_REQUEST['systemName']);
\PHPWS_Settings::set('intern','registrarEmail',$_REQUEST['registrarEmail']);
\PHPWS_Settings::set('intern','distanceEdEmail',$_REQUEST['distanceEdEmail']);
\PHPWS_Settings::set('intern','internationalRegEmail',$_REQUEST['internationalRegEmail']);
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
post accesses the super-global variable $_REQUEST. Open
public function post(){
\PHPWS_Settings::set('intern','systemName',$_REQUEST['systemName']);
\PHPWS_Settings::set('intern','registrarEmail',$_REQUEST['registrarEmail']);
\PHPWS_Settings::set('intern','distanceEdEmail',$_REQUEST['distanceEdEmail']);
\PHPWS_Settings::set('intern','internationalRegEmail',$_REQUEST['internationalRegEmail']);
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
post accesses the super-global variable $_REQUEST. Open
public function post(){
\PHPWS_Settings::set('intern','systemName',$_REQUEST['systemName']);
\PHPWS_Settings::set('intern','registrarEmail',$_REQUEST['registrarEmail']);
\PHPWS_Settings::set('intern','distanceEdEmail',$_REQUEST['distanceEdEmail']);
\PHPWS_Settings::set('intern','internationalRegEmail',$_REQUEST['internationalRegEmail']);
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
post accesses the super-global variable $_REQUEST. Open
public function post(){
\PHPWS_Settings::set('intern','systemName',$_REQUEST['systemName']);
\PHPWS_Settings::set('intern','registrarEmail',$_REQUEST['registrarEmail']);
\PHPWS_Settings::set('intern','distanceEdEmail',$_REQUEST['distanceEdEmail']);
\PHPWS_Settings::set('intern','internationalRegEmail',$_REQUEST['internationalRegEmail']);
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
post accesses the super-global variable $_REQUEST. Open
public function post(){
\PHPWS_Settings::set('intern','systemName',$_REQUEST['systemName']);
\PHPWS_Settings::set('intern','registrarEmail',$_REQUEST['registrarEmail']);
\PHPWS_Settings::set('intern','distanceEdEmail',$_REQUEST['distanceEdEmail']);
\PHPWS_Settings::set('intern','internationalRegEmail',$_REQUEST['internationalRegEmail']);
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
post accesses the super-global variable $_REQUEST. Open
public function post(){
\PHPWS_Settings::set('intern','systemName',$_REQUEST['systemName']);
\PHPWS_Settings::set('intern','registrarEmail',$_REQUEST['registrarEmail']);
\PHPWS_Settings::set('intern','distanceEdEmail',$_REQUEST['distanceEdEmail']);
\PHPWS_Settings::set('intern','internationalRegEmail',$_REQUEST['internationalRegEmail']);
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
post accesses the super-global variable $_REQUEST. Open
public function post(){
\PHPWS_Settings::set('intern','systemName',$_REQUEST['systemName']);
\PHPWS_Settings::set('intern','registrarEmail',$_REQUEST['registrarEmail']);
\PHPWS_Settings::set('intern','distanceEdEmail',$_REQUEST['distanceEdEmail']);
\PHPWS_Settings::set('intern','internationalRegEmail',$_REQUEST['internationalRegEmail']);
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
post accesses the super-global variable $_REQUEST. Open
public function post(){
\PHPWS_Settings::set('intern','systemName',$_REQUEST['systemName']);
\PHPWS_Settings::set('intern','registrarEmail',$_REQUEST['registrarEmail']);
\PHPWS_Settings::set('intern','distanceEdEmail',$_REQUEST['distanceEdEmail']);
\PHPWS_Settings::set('intern','internationalRegEmail',$_REQUEST['internationalRegEmail']);
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
execute accesses the super-global variable $_SERVER. Open
public function execute(){
if(!\Current_User::allow('intern', 'affiliation_agreement')){
\NQ::simple('intern', \Intern\UI\NotifyUI::WARNING, 'You do not have permission to edit admin settings.');
throw new \Intern\Exception\PermissionException('You do not have permission to edit admin settings.');
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
post accesses the super-global variable $_REQUEST. Open
public function post(){
\PHPWS_Settings::set('intern','systemName',$_REQUEST['systemName']);
\PHPWS_Settings::set('intern','registrarEmail',$_REQUEST['registrarEmail']);
\PHPWS_Settings::set('intern','distanceEdEmail',$_REQUEST['distanceEdEmail']);
\PHPWS_Settings::set('intern','internationalRegEmail',$_REQUEST['internationalRegEmail']);
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
post accesses the super-global variable $_REQUEST. Open
public function post(){
\PHPWS_Settings::set('intern','systemName',$_REQUEST['systemName']);
\PHPWS_Settings::set('intern','registrarEmail',$_REQUEST['registrarEmail']);
\PHPWS_Settings::set('intern','distanceEdEmail',$_REQUEST['distanceEdEmail']);
\PHPWS_Settings::set('intern','internationalRegEmail',$_REQUEST['internationalRegEmail']);
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
post accesses the super-global variable $_REQUEST. Open
public function post(){
\PHPWS_Settings::set('intern','systemName',$_REQUEST['systemName']);
\PHPWS_Settings::set('intern','registrarEmail',$_REQUEST['registrarEmail']);
\PHPWS_Settings::set('intern','distanceEdEmail',$_REQUEST['distanceEdEmail']);
\PHPWS_Settings::set('intern','internationalRegEmail',$_REQUEST['internationalRegEmail']);
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
post accesses the super-global variable $_REQUEST. Open
public function post(){
\PHPWS_Settings::set('intern','systemName',$_REQUEST['systemName']);
\PHPWS_Settings::set('intern','registrarEmail',$_REQUEST['registrarEmail']);
\PHPWS_Settings::set('intern','distanceEdEmail',$_REQUEST['distanceEdEmail']);
\PHPWS_Settings::set('intern','internationalRegEmail',$_REQUEST['internationalRegEmail']);
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
post accesses the super-global variable $_REQUEST. Open
public function post(){
\PHPWS_Settings::set('intern','systemName',$_REQUEST['systemName']);
\PHPWS_Settings::set('intern','registrarEmail',$_REQUEST['registrarEmail']);
\PHPWS_Settings::set('intern','distanceEdEmail',$_REQUEST['distanceEdEmail']);
\PHPWS_Settings::set('intern','internationalRegEmail',$_REQUEST['internationalRegEmail']);
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
Superglobals
Since: 0.2
Accessing a super-global variable directly is considered a bad practice. These variables should be encapsulated in objects that are provided by a framework, for instance.
Example
class Foo {
public function bar() {
$name = $_POST['foo'];
}
}
Source
Missing class import via use statement (line '11', column '23'). Open
throw new \Intern\Exception\PermissionException('You do not have permission to edit admin settings.');
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
MissingImport
Since: 2.7.0
Importing all external classes in a file through use statements makes them clearly visible.
Example
function make() {
return new \stdClass();
}
Source http://phpmd.org/rules/cleancode.html#MissingImport
Avoid using static access to class '\PHPWS_Settings' in method 'post'. Open
\PHPWS_Settings::set('intern','internationalRegEmail',$_REQUEST['internationalRegEmail']);
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
StaticAccess
Since: 1.4.0
Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.
Example
class Foo
{
public function bar()
{
Bar::baz();
}
}
Source https://phpmd.org/rules/cleancode.html#staticaccess
Avoid using static access to class '\PHPWS_Settings' in method 'post'. Open
\PHPWS_Settings::set('intern','graduateRegEmail',$_REQUEST['graduateRegEmail']);
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
StaticAccess
Since: 1.4.0
Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.
Example
class Foo
{
public function bar()
{
Bar::baz();
}
}
Source https://phpmd.org/rules/cleancode.html#staticaccess
Avoid using static access to class '\PHPWS_Settings' in method 'post'. Open
\PHPWS_Settings::set('intern','systemName',$_REQUEST['systemName']);
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
StaticAccess
Since: 1.4.0
Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.
Example
class Foo
{
public function bar()
{
Bar::baz();
}
}
Source https://phpmd.org/rules/cleancode.html#staticaccess
Avoid using static access to class '\PHPWS_Settings' in method 'get'. Open
return \PHPWS_Settings::get('intern');
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
StaticAccess
Since: 1.4.0
Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.
Example
class Foo
{
public function bar()
{
Bar::baz();
}
}
Source https://phpmd.org/rules/cleancode.html#staticaccess
Avoid using static access to class '\PHPWS_Settings' in method 'post'. Open
\PHPWS_Settings::set('intern','distanceEdEmail',$_REQUEST['distanceEdEmail']);
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
StaticAccess
Since: 1.4.0
Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.
Example
class Foo
{
public function bar()
{
Bar::baz();
}
}
Source https://phpmd.org/rules/cleancode.html#staticaccess
Avoid using static access to class '\PHPWS_Settings' in method 'post'. Open
\PHPWS_Settings::set('intern','registrarEmail',$_REQUEST['registrarEmail']);
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
StaticAccess
Since: 1.4.0
Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.
Example
class Foo
{
public function bar()
{
Bar::baz();
}
}
Source https://phpmd.org/rules/cleancode.html#staticaccess
Avoid using static access to class '\PHPWS_Settings' in method 'post'. Open
\PHPWS_Settings::set('intern','gradSchoolEmail',$_REQUEST['gradSchoolEmail']);
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
StaticAccess
Since: 1.4.0
Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.
Example
class Foo
{
public function bar()
{
Bar::baz();
}
}
Source https://phpmd.org/rules/cleancode.html#staticaccess
Avoid using static access to class '\PHPWS_Settings' in method 'post'. Open
\PHPWS_Settings::set('intern','fromEmail',$_REQUEST['fromEmail']);
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
StaticAccess
Since: 1.4.0
Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.
Example
class Foo
{
public function bar()
{
Bar::baz();
}
}
Source https://phpmd.org/rules/cleancode.html#staticaccess
Avoid using static access to class '\PHPWS_Settings' in method 'post'. Open
\PHPWS_Settings::set('intern','wsdlUri',$_REQUEST['wsdlUri']);
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
StaticAccess
Since: 1.4.0
Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.
Example
class Foo
{
public function bar()
{
Bar::baz();
}
}
Source https://phpmd.org/rules/cleancode.html#staticaccess
Avoid using static access to class '\PHPWS_Settings' in method 'post'. Open
\PHPWS_Settings::set('intern','uncaughtExceptionEmail',$_REQUEST['uncaughtExceptionEmail']);
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
StaticAccess
Since: 1.4.0
Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.
Example
class Foo
{
public function bar()
{
Bar::baz();
}
}
Source https://phpmd.org/rules/cleancode.html#staticaccess
Avoid using static access to class '\Current_User' in method 'execute'. Open
if(!\Current_User::allow('intern', 'affiliation_agreement')){
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
StaticAccess
Since: 1.4.0
Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.
Example
class Foo
{
public function bar()
{
Bar::baz();
}
}
Source https://phpmd.org/rules/cleancode.html#staticaccess
Avoid using static access to class '\NQ' in method 'execute'. Open
\NQ::simple('intern', \Intern\UI\NotifyUI::WARNING, 'You do not have permission to edit admin settings.');
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
StaticAccess
Since: 1.4.0
Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.
Example
class Foo
{
public function bar()
{
Bar::baz();
}
}
Source https://phpmd.org/rules/cleancode.html#staticaccess
Avoid using static access to class '\PHPWS_Settings' in method 'post'. Open
\PHPWS_Settings::set('intern','backgroundCheckEmail',$_REQUEST['backgroundCheckEmail']);
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
StaticAccess
Since: 1.4.0
Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.
Example
class Foo
{
public function bar()
{
Bar::baz();
}
}
Source https://phpmd.org/rules/cleancode.html#staticaccess
Avoid using static access to class '\PHPWS_Settings' in method 'post'. Open
\PHPWS_Settings::save('intern');
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
StaticAccess
Since: 1.4.0
Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.
Example
class Foo
{
public function bar()
{
Bar::baz();
}
}
Source https://phpmd.org/rules/cleancode.html#staticaccess
Avoid using static access to class '\PHPWS_Settings' in method 'post'. Open
\PHPWS_Settings::set('intern','internationalOfficeEmail',$_REQUEST['internationalOfficeEmail']);
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
StaticAccess
Since: 1.4.0
Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.
Example
class Foo
{
public function bar()
{
Bar::baz();
}
}
Source https://phpmd.org/rules/cleancode.html#staticaccess
Avoid using static access to class '\PHPWS_Settings' in method 'post'. Open
\PHPWS_Settings::set('intern','emailDomain',$_REQUEST['emailDomain']);
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
StaticAccess
Since: 1.4.0
Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.
Example
class Foo
{
public function bar()
{
Bar::baz();
}
}
Source https://phpmd.org/rules/cleancode.html#staticaccess
Avoid using static access to class '\PHPWS_Settings' in method 'post'. Open
\PHPWS_Settings::set('intern','unusualCourseEmail',$_REQUEST['unusualCourseEmail']);
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
StaticAccess
Since: 1.4.0
Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.
Example
class Foo
{
public function bar()
{
Bar::baz();
}
}
Source https://phpmd.org/rules/cleancode.html#staticaccess
The method execute() contains an exit expression. Open
exit;
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
ExitExpression
Since: 0.2
An exit-expression within regular code is untestable and therefore it should be avoided. Consider to move the exit-expression into some kind of startup script where an error/exception code is returned to the calling environment.
Example
class Foo {
public function bar($param) {
if ($param === 42) {
exit(23);
}
}
}
Source https://phpmd.org/rules/design.html#exitexpression
The method execute() contains an exit expression. Open
exit;
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
ExitExpression
Since: 0.2
An exit-expression within regular code is untestable and therefore it should be avoided. Consider to move the exit-expression into some kind of startup script where an error/exception code is returned to the calling environment.
Example
class Foo {
public function bar($param) {
if ($param === 42) {
exit(23);
}
}
}
Source https://phpmd.org/rules/design.html#exitexpression
The method execute() contains an exit expression. Open
exit;
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
ExitExpression
Since: 0.2
An exit-expression within regular code is untestable and therefore it should be avoided. Consider to move the exit-expression into some kind of startup script where an error/exception code is returned to the calling environment.
Example
class Foo {
public function bar($param) {
if ($param === 42) {
exit(23);
}
}
}
Source https://phpmd.org/rules/design.html#exitexpression
Call to method set
from undeclared class \PHPWS_Settings
Open
\PHPWS_Settings::set('intern','registrarEmail',$_REQUEST['registrarEmail']);
- Create a ticketCreate a ticket
- Exclude checks
Call to method set
from undeclared class \PHPWS_Settings
Open
\PHPWS_Settings::set('intern','fromEmail',$_REQUEST['fromEmail']);
- Create a ticketCreate a ticket
- Exclude checks
Call to method set
from undeclared class \PHPWS_Settings
Open
\PHPWS_Settings::set('intern','distanceEdEmail',$_REQUEST['distanceEdEmail']);
- Create a ticketCreate a ticket
- Exclude checks
Call to method set
from undeclared class \PHPWS_Settings
Open
\PHPWS_Settings::set('intern','backgroundCheckEmail',$_REQUEST['backgroundCheckEmail']);
- Create a ticketCreate a ticket
- Exclude checks
Call to method save
from undeclared class \PHPWS_Settings
Open
\PHPWS_Settings::save('intern');
- Create a ticketCreate a ticket
- Exclude checks
Call to method set
from undeclared class \PHPWS_Settings
Open
\PHPWS_Settings::set('intern','systemName',$_REQUEST['systemName']);
- Create a ticketCreate a ticket
- Exclude checks
Call to method set
from undeclared class \PHPWS_Settings
Open
\PHPWS_Settings::set('intern','internationalRegEmail',$_REQUEST['internationalRegEmail']);
- Create a ticketCreate a ticket
- Exclude checks
Call to method set
from undeclared class \PHPWS_Settings
Open
\PHPWS_Settings::set('intern','gradSchoolEmail',$_REQUEST['gradSchoolEmail']);
- Create a ticketCreate a ticket
- Exclude checks
Call to method allow
from undeclared class \Current_User
Open
if(!\Current_User::allow('intern', 'affiliation_agreement')){
- Create a ticketCreate a ticket
- Exclude checks
Call to method set
from undeclared class \PHPWS_Settings
Open
\PHPWS_Settings::set('intern','emailDomain',$_REQUEST['emailDomain']);
- Create a ticketCreate a ticket
- Exclude checks
Call to method set
from undeclared class \PHPWS_Settings
Open
\PHPWS_Settings::set('intern','unusualCourseEmail',$_REQUEST['unusualCourseEmail']);
- Create a ticketCreate a ticket
- Exclude checks
Call to method set
from undeclared class \PHPWS_Settings
Open
\PHPWS_Settings::set('intern','uncaughtExceptionEmail',$_REQUEST['uncaughtExceptionEmail']);
- Create a ticketCreate a ticket
- Exclude checks
Call to method set
from undeclared class \PHPWS_Settings
Open
\PHPWS_Settings::set('intern','graduateRegEmail',$_REQUEST['graduateRegEmail']);
- Create a ticketCreate a ticket
- Exclude checks
Call to method set
from undeclared class \PHPWS_Settings
Open
\PHPWS_Settings::set('intern','internationalOfficeEmail',$_REQUEST['internationalOfficeEmail']);
- Create a ticketCreate a ticket
- Exclude checks
Call to method set
from undeclared class \PHPWS_Settings
Open
\PHPWS_Settings::set('intern','wsdlUri',$_REQUEST['wsdlUri']);
- Create a ticketCreate a ticket
- Exclude checks
Call to method simple
from undeclared class \NQ
Open
\NQ::simple('intern', \Intern\UI\NotifyUI::WARNING, 'You do not have permission to edit admin settings.');
- Create a ticketCreate a ticket
- Exclude checks
Call to method get
from undeclared class \PHPWS_Settings
Open
return \PHPWS_Settings::get('intern');
- Create a ticketCreate a ticket
- Exclude checks