search

Copyleaks / moodle-plagiarism_copyleaks

Copyleaks Plagiarism plugin for Moodle
GNU General Public License v3.0
3 stars 3 forks source link

Wrong column XML type #45

Closed Arvaloez closed 6 months ago

Arvaloez commented 6 months ago

Hello, I'm integrating the last version of Copyleaks and I got the following error:

plagiarism_copyleaks_files

The possible solution is to change on the upgrade file, line 472, the XMLDB_TYPE_NUMBER to XMLDB_TYPE_INTEGER.

Could you help us with this change?

Thank you.

CL-BayanAbuawad commented 6 months ago

@Arvaloez thank you for reporting this; a fix was applied here and merged here

A new version was deployed to the Moodle marketplace: https://moodle.org/plugins/plagiarism_copyleaks

Arvaloez commented 6 months ago

Hi @CL-BayanAbuawad,

Firstly, thank you for addressing the issue. Your assistance is greatly appreciated.

While most aspects seem to be functioning correctly now, there's still an issue persisting. It appears that when you altered the field type, you overlooked the necessity of adjusting the default option for null values. It's imperative to set the field default to '0' after the type change.

Upon integration, we received the following response:

plagiarism_copyleaks_files

To rectify this, on the upgrade file, at line 471, requires an amendment. The default parameter must be set to '0'.

Once again, thank you for your invaluable support.

CL-BayanAbuawad commented 6 months ago

@Arvaloez Thank you! We somehow missed this. We are not getting this issue on our side, and we are working on understanding why.

A fix was applied to the new issue here

A new version was deployed to the Moodle marketplace: https://moodle.org/plugins/plagiarism_copyleaks

Arvaloez commented 6 months ago

Hi @CL-BayanAbuawad, Thank you for your support. I'm in the process of uploading the changes. Once I have the results, I'll be sure to provide you with an update.

It appears that the issue is related to the DB manager. While I've achieved successful results with PostgreSQL, is with MySQL when I got this issue. Perhaps this info could help you to find the issue. Thank you again for your help.