Normalize use of form security tokens in Admin modules

# Conflicts:
#	src/Module/Admin/Logs/Settings.php
This commit is contained in:
Hypolite Petovan 2020-09-08 10:42:25 -04:00
parent 2ce15cae1a
commit 9bc2c5a52e
12 changed files with 43 additions and 39 deletions

View file

@ -37,7 +37,7 @@ class Delete extends BaseAdmin
return;
}
parent::checkFormSecurityTokenRedirectOnError('/admin/item/delete', 'admin_deleteitem');
self::checkFormSecurityTokenRedirectOnError('/admin/item/delete', 'admin_deleteitem');
if (!empty($_POST['page_deleteitem_submit'])) {
$guid = trim(Strings::escapeTags($_POST['deleteitemguid']));
@ -68,7 +68,7 @@ class Delete extends BaseAdmin
'$intro1' => DI::l10n()->t('On this page you can delete an item from your node. If the item is a top level posting, the entire thread will be deleted.'),
'$intro2' => DI::l10n()->t('You need to know the GUID of the item. You can find it e.g. by looking at the display URL. The last part of http://example.com/display/123456 is the GUID, here 123456.'),
'$deleteitemguid' => ['deleteitemguid', DI::l10n()->t("GUID"), '', DI::l10n()->t("The GUID of the item you want to delete."), 'required', 'autofocus'],
'$form_security_token' => parent::getFormSecurityToken("admin_deleteitem")
'$form_security_token' => self::getFormSecurityToken("admin_deleteitem")
]);
}
}