Error approving new entry

[effer89]

Description

I've got Request missing required body param when approving a entry (new/old)
URL of approval: domain.com/admin/entries/artigos/1687581-fernando-teste-1

And thanks for the support :D

Stack Trace

yii\web\BadRequestHttpException: Request missing required body param in /opt/bitnami/apache2/htdocs/cms/vendor/craftcms/cms/src/web/Request.php:661 Stack trace: #0 /opt/bitnami/apache2/htdocs/cms/vendor/craftcms/cms/src/controllers/EntryRevisionsController.php(321): craft\web\Request->getRequiredBodyParam('draftId') #1 [internal function]: craft\controllers\EntryRevisionsController->actionPublishDraft() #2 /opt/bitnami/apache2/htdocs/cms/vendor/yiisoft/yii2/base/InlineAction.php(57): call_user_func_array(Array, Array) #3 /opt/bitnami/apache2/htdocs/cms/vendor/yiisoft/yii2/base/Controller.php(157): yii\base\InlineAction->runWithParams(Array) #4 /opt/bitnami/apache2/htdocs/cms/vendor/craftcms/cms/src/web/Controller.php(187): yii\base\Controller->runAction('publish-draft', Array) #5 /opt/bitnami/apache2/htdocs/cms/vendor/yiisoft/yii2/base/Module.php(528): craft\web\Controller->runAction('publish-draft', Array) #6 /opt/bitnami/apache2/htdocs/cms/vendor/craftcms/cms/src/web/Application.php(299): yii\base\Module->runAction('entry-revisions...', Array) #7 /opt/bitnami/apache2/htdocs/cms/vendor/craftcms/cms/src/web/Application.php(566): craft\web\Application->runAction('entry-revisions...', Array) #8 /opt/bitnami/apache2/htdocs/cms/vendor/craftcms/cms/src/web/Application.php(278): craft\web\Application->_processActionRequest(Object(craft\web\Request)) #9 /opt/bitnami/apache2/htdocs/cms/vendor/yiisoft/yii2/base/Application.php(386): craft\web\Application->handleRequest(Object(craft\web\Request)) #10 /opt/bitnami/apache2/htdocs/cms/web/index.php(33): yii\base\Application->run() #11 {main}

Steps to reproduce

1. New entry
2. Approve it

Additional info

• Plugin version: 1.2.3
• Craft version: Craft Pro 3.2.10

[effer89]

Hi, any news on this?

[engram-design]

We've updated some behaviour in 1.3.0 to fix this!