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

psgdpr LoggerRepository table name #32148

Closed
2 tasks done
igorxut opened this issue Apr 13, 2023 · 3 comments
Closed
2 tasks done

psgdpr LoggerRepository table name #32148

igorxut opened this issue Apr 13, 2023 · 3 comments
Labels
Bug Type: Bug Duplicate Resolution: issue closed because already reported Invalid Resolution: issue closed because invalid

Comments

@igorxut
Copy link

igorxut commented Apr 13, 2023

Prerequisites

Describe the bug and add attachments

Hello. I think there is an error here: https://github.com/PrestaShop/psgdpr/blob/dev/src/Repository/LoggerRepository.php#L55.

$query = $queryBuilder->select('*')->from('ps_psgdpr_log', 'l');

The name of table is hardcoded! I have another db prefix, that's why I get an error when click on "Configure" module.

Expected behavior

The name of the table must use db prefix of the shop.

Steps to reproduce

  1. Open file "\modules\psgdpr\src\Repository"
  2. Look at line: $query = $queryBuilder->select('*')->from('ps_psgdpr_log', 'l');

PrestaShop version(s) where the bug happened

8.0.1

PHP version(s) where the bug happened

7.2.34

If your bug is related to a module, specify its name and its version

psgdpr 2.0.0

Your company or customer's name goes here (if applicable).

No response

@igorxut igorxut added Bug Type: Bug New New issue not yet processed by QA labels Apr 13, 2023
@igorxut
Copy link
Author

igorxut commented Apr 13, 2023

Oh, I think the problem was described here: #32138

@AureRita
Copy link
Contributor

AureRita commented Apr 13, 2023

Hi @igorxut

Thank you for your report, yes, indeed this problem is described on #32138

So I have to close your issue because it's a dupplicate
To be informed when it's fixed, please subscribe to the issue mentioned above.

Thank you

@AureRita
Copy link
Contributor

Duplicate of #32138

@AureRita AureRita marked this as a duplicate of #32138 Apr 13, 2023
@AureRita AureRita added Duplicate Resolution: issue closed because already reported Invalid Resolution: issue closed because invalid and removed New New issue not yet processed by QA labels Apr 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Type: Bug Duplicate Resolution: issue closed because already reported Invalid Resolution: issue closed because invalid
Projects
None yet
Development

No branches or pull requests

2 participants