More reporting - duplicate entry

WebGreg · 2023-07-25 14:00:50

Hi

I got such an error:

SQL Error "1062": Duplicate entry '12-0' for key 'glpi_plugin_mreporting_profiles.profiles_id_reports' in query "INSERT INTO `glpi_plugin_mreporting_profiles` (`profiles_id`) VALUES ('12')"

I'm getting this error after installing the plugin > going to any profile > clicking on the save button (without any configuration of profile permissions).

How can I solve it?

GLPI 10.0.7

Last edited by WebGreg (2023-07-25 14:03:39)

cconard96 · 2023-07-26 03:32:47

Which version of the mreporting plugin do you have installed?

WebGreg · 2023-07-26 07:33:01

1.8.2

cconard96 · 2023-07-26 12:27:44

Do you have the full stacktrace from the files/_log/sql-errors.log log?

WebGreg · 2023-07-26 19:01:16

[2023-07-26 18:58:19] glpisqllog.ERROR: DBmysql::query() in /var/www/html/glpi/src/DBmysql.php line 370
*** MySQL query error:
SQL: INSERT INTO `glpi_plugin_mreporting_profiles` (`profiles_id`) VALUES ('12')
Error: Duplicate entry '12-0' for key 'glpi_plugin_mreporting_profiles.profiles_id_reports'
Backtrace :
src/DBmysql.php:1320
src/CommonDBTM.php:722 DBmysql->insert()
src/CommonDBTM.php:1317 CommonDBTM->addToDB()
marketplace/mreporting/inc/profile.class.php:184 CommonDBTM->add()
marketplace/mreporting/inc/profile.class.php:86 PluginMreportingProfile->createAccess()
src/CommonGLPI.php:689 PluginMreportingProfile::displayTabContentForItem()
ajax/common.tabs.php:116 CommonGLPI::displayStandardTab()
public/index.php:73 require()

cconard96 · 2023-07-27 02:21:00

I confirm the issue, although I don't really know that much about the plugin so making a fix may take a while.

WebGreg · 2023-07-27 09:33:24

Hi.

I don't know if I did the right thing, but I opened an issue on guthub, but there is only the option to report vulnerabilities.

https://github.com/pluginsGLPI/mreporti … -fjxg-gf3w

cconard96 · 2023-07-27 20:37:26

More Reporting is one of the plugins that only has community support on the forums, or support through GLPI Network, so bug reports aren't open on GitHub for it.

J2C99 · 2024-06-28 17:29:24

Sorry for the speleologic work, but the problem persists with the last version

I can give more informations.

The problem is on the mreporting tab on all profiles (https://*****/front/profile.form.php?id=21%20&formoptions=%20data-track-changes%3D%27true%27)
In the code, the problem is (for mreporting 1.8.6)

public static function displayTabContentForItem(CommonGLPI $item, $tabnum = 1, $withtemplate = 0)
{
global $CFG_GLPI;

if ($item->getType() == 'Profile' && $item->getField('interface') != 'helpdesk') {
$ID = $item->getField('id');
$prof = new self();

if (!$prof->getFromDBByProfile($item->getField('id'))) {
$prof->createAccess($item->getField('id'));
}
$prof->showForm($item->getField('id'));
} else if ($item->getType() == 'PluginMreportingConfig') {
$reportProfile = new self();
$reportProfile->showFormForManageProfile($item);
}
return true;
}

My explication for this code is the following:
With the mreporting tab , you can change the accesses for the current profile , and you can switch to an another.
But if the profile is a new, none access has been created , and you can 't change the access for the reports.
It's the role $prof->createAccess($item->getField('id')); .

The problem is the test condition.
!$prof->getFromDBByProfile($item->getField('id'))) is always true and it's problematic
The condition must be check in the glpi_plugin_mreporting_profiles if none row contains an entry for the given profile (id here)

Regards,

Forum GLPI-Project

Announcement

#1 2023-07-25 14:00:50

More reporting - duplicate entry

#2 2023-07-26 03:32:47

Re: More reporting - duplicate entry

#3 2023-07-26 07:33:01

Re: More reporting - duplicate entry

#4 2023-07-26 12:27:44

Re: More reporting - duplicate entry

#5 2023-07-26 19:01:16

Re: More reporting - duplicate entry

#6 2023-07-27 02:21:00

Re: More reporting - duplicate entry

#7 2023-07-27 09:33:24

Re: More reporting - duplicate entry

#8 2023-07-27 20:37:26

Re: More reporting - duplicate entry

#9 2024-06-28 17:29:24

Re: More reporting - duplicate entry

Board footer