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.

Sign up for GitHub

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

Jump to bottom

TypeError: PhpMyAdmin\ConfigStorage\Relation::setHistory(): Argument #4 ($sqlquery) must be of type string, null given #19162

Closed
liviuconcioiu opened this issue May 14, 2024 · 1 comment
Closed

TypeError: PhpMyAdmin\ConfigStorage\Relation::setHistory(): Argument #4 ($sqlquery) must be of type string, null given #19162

liviuconcioiu opened this issue May 14, 2024 · 1 comment
Assignees
@MauricioFauth
Labels
Bug A problem or regression with an existing feature
Milestone
6.0.0

Comments

@liviuconcioiu
Copy link
Contributor

Describe the bug

TypeError: PhpMyAdmin\ConfigStorage\Relation::setHistory(): Argument #4 ($sqlquery) must be of type string, null given, called in /home/demo/.pma-demo/master-config/src/Http/Middleware/StatementHistory.php on line 44

on localhost is at line 595 Internal error in .\src\ConfigStorage\Relation.php#595

To Reproduce

Steps to reproduce the behavior:

  1. Go to https://demo.phpmyadmin.net/master-config/public/index.php?route=/server/privileges
  2. See error

Expected behavior

No error should happen.

Server configuration

  • phpMyAdmin version: 6.0.0-dev
@kamil-tekiela
Copy link
Contributor

@MauricioFauth Looks like $GLOBALS['sql_query'] can be null 5e429ff#diff-0eeb0b543c665c54c468ee73fe05a0280b5ec8ef1792ed83f84be898a7337702L175

@MauricioFauth MauricioFauth self-assigned this May 15, 2024
@MauricioFauth MauricioFauth added Bug A problem or regression with an existing feature affects/6.0 This issue or pull-request affects 6.0.x releases (and maybe further versions) confirmed/6.0 This issue is confirmed to be reproduced on 6.0 at the time this label was set labels May 15, 2024
@williamdes williamdes added this to the 6.0.0 milestone May 15, 2024
@williamdes williamdes removed affects/6.0 This issue or pull-request affects 6.0.x releases (and maybe further versions) confirmed/6.0 This issue is confirmed to be reproduced on 6.0 at the time this label was set labels May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MauricioFauth MauricioFauth

Labels
Bug A problem or regression with an existing feature
Projects
None yet
Milestone
6.0.0
Development

No branches or pull requests
4 participants
@MauricioFauth @kamil-tekiela @williamdes @liviuconcioiu