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

Jump to bottom

Trying to access array offset on value o type null [ReplicationGui.php#270] #15636

Closed
r0073rr0r opened this issue Dec 10, 2019 · 2 comments
Closed

Trying to access array offset on value o type null [ReplicationGui.php#270] #15636

r0073rr0r opened this issue Dec 10, 2019 · 2 comments
Assignees
@williamdes
Labels
Bug A problem or regression with an existing feature
Projects
issues
Milestone
4.9.3

Comments

@r0073rr0r
Copy link
Contributor

r0073rr0r commented Dec 10, 2019 •
edited

Describe the bug

Trying to access array offset on value o type null in file ReplicationGui.php#270

To Reproduce

Steps to reproduce the behavior:

  1. Go to 'Home'
  2. Click on 'Status'
  3. See error

Expected behavior

In older versions of PHP this will not break code (just brings exception) but in 7.4 it breaks.

Screenshots

https://prnt.sc/q8svsc
https://prnt.sc/q8szls
https://prnt.sc/q8szqo

Server configuration

  • Operating system: Ubuntu 16.04
  • Web server: Apache
  • Database version:
  • PHP version: 7.4
  • phpMyAdmin version: 5.1.0-dev, latest stable version: 4.9.2

Server: Localhost via UNIX socket
Server type: MariaDB
Server connection: SSL is not being used Documentation
Server version: 10.0.38-MariaDB-0ubuntu0.16.04.1 - Ubuntu 16.04
Protocol version: 10
Server charset: UTF-8 Unicode (utf8mb4)

Client configuration

  • Browser: Chrome
  • Operating system: Windows
@r0073rr0r
Copy link
Contributor Author

This will be a fix:
image

@williamdes williamdes added this to the 5.1.0 milestone Dec 10, 2019
@williamdes williamdes added the Bug A problem or regression with an existing feature label Dec 10, 2019
@williamdes williamdes added this to Needs triage in issues via automation Dec 10, 2019
@williamdes williamdes moved this from Needs triage to to be fixed soon in issues Dec 10, 2019
williamdes added a commit that referenced this issue Dec 24, 2019
@williamdes
Add ChangeLog entry for #15636
0faa43a 
Signed-off-by: William Desportes <williamdes@wdes.fr>
issues automation moved this from to be fixed soon to Closed Dec 24, 2019
@williamdes williamdes self-assigned this Dec 24, 2019
@williamdes williamdes modified the milestones: 5.1.0, 4.9.3 Dec 24, 2019
@williamdes
Copy link
Member

@r0073rr0r I closed the issue on 4.9,5.0,5.1 versions with 54e202a and ee6b388

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@williamdes williamdes

Labels
Bug A problem or regression with an existing feature
Projects
issues
  
Closed
Milestone
4.9.3
Development

No branches or pull requests
2 participants
@williamdes @r0073rr0r