Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bugfix: Fixed "Bad Request" on "run query" in debug panel #227

Merged
merged 3 commits into from
Apr 30, 2019

Conversation

rhertogh
Copy link
Contributor

This pr fixes the "Bad Request (#400): Unable to verify your data submission." error when using the "run query" action in the debugger details panel by registering the YiiAsset in order to inject csrf token in ajax requests

Q A
Is bugfix? yes
New feature? no
Breaks BC? no
Tests pass? yes
Fixed issues -

image

rhertogh and others added 3 commits April 30, 2019 18:47
Register YiiAsset in order to inject csrf token in ajax requests
added yiisoft#227 to changelog
@samdark samdark merged commit c908e56 into yiisoft:master Apr 30, 2019
@samdark
Copy link
Member

samdark commented Apr 30, 2019

Merged. Thanks!

@samdark samdark added this to the 2.0.6 milestone Apr 30, 2019
@samdark samdark added the type:bug Bug label Apr 30, 2019
samdark added a commit that referenced this pull request May 1, 2019
* Update Query.php (#131)

* PHPUnit compatibility, provide token for github auth

* token update

* yet another update

* Fix #134 infinite query loop when the index does not exist

* improved error message for cluster auto detection

issue #137

* updated docs about cluster autodetection

fixes #137

* Elasticsearch logo added to README.md

* Composer json change

* Added alias actions to Command

* Fix for desirialization of plain response from elasticsearch

* Bring back old name for package

* Fix for php 5.4

* Added phpdocs, fixes and tests

* CHANGELOG.md

* clarify version compatibility

* Fixing broken elasticsearch doc links (#144) [skip ci]

* Fixes #149: Changed `yii\base\Object` to `yii\base\BaseObject`

* since elasticsearch 6, content type is mandatory (#150)

since elasticsearch 6, content type is mandatory. Otherwise, requests will all fail.

https://www.elastic.co/blog/strict-content-type-checking-for-elasticsearch-rest-requests

* added CHANGELOG for #150

* Reset query results after calling refresh() method

close #125

* Fixes case (#153) [skip ci]

* Fix spelling (#165) [skip ci]

* fix findAll and findOne to filter input to avoid passing manipulated condition

* release version 2.0.5

* prepare for next release

* Update README.md

* docs/guide-ja updated [ci skip] (#178)

* Removed redundant line from license [skip ci]

* guide-ja revised [ci skip]

* Fixed `count()` compatibility with PHP 7.2

do not call it on scalar values.

fixes #180

* Translate into Russian (#194) [skip ci]

* Improve Russian docs (#200) [skip ci]

* Bug #201: Fixed infinite loop

* Updated issue template [skip ci]

* Made tests running again (#210)

* Revert "Bug #201: Fixed infinite loop"

This reverts commit aa22ffd.

* Fixes #218: Comment out invalid syntax in sample [skip ci] (#219)

* docs/guide-ja/mapping-indexing.md updated [ci skip] (#221)

* Fixes #227: Fixed `Bad Request (#400): Unable to verify your data submission.` in debug details panel 'run query'

* Travis adjustments (#228)

* Use assertCount() in tests

* Add missing relations to Order test model

* Add note delete-by-query plugin (#158)

* Fixes #117: Add support for `QueryInterface::emulateExecution()`

* Specified versions that work
@rhertogh
Copy link
Contributor Author

rhertogh commented May 7, 2019

For anyone running in a Class 'yii\elasticsearch\YiiAsset' not found error, please use #235 as a workaround until merged. My apologies for any inconvenience.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants