Steps to Reproduce the Behavior and Expected Behavior

Oct 13, 2025 by windailys.com 94 views

Introduction

Dolibarr, a popular open-source enterprise resource planning (ERP) software, has detected a technical error. This error may be useful for diagnostic purposes, and by setting the option $dolibarr_main_prod to '1', you can mask sensitive information. In this article, we will delve into the details of the bug, its impact, and the steps to reproduce the behavior.

Bug Details

Bug

Dolibarr has detected a technical error, which is as follows:

Date: 20250313163013
Dolibarr Version: 21.0.0 - https://www.dolibarr.org
Niveau de fonctionnalités: 0
Identifiant: ********
PHP Version: 8.3.17
Serveur: Apache
OS: Linux ************ 4.18.0-553.5.1.lve.1.el8.x86_64 #1 SMP Fri Jun 14 15:38:45 UTC 2024 x86_64
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36

The error occurred when accessing the following URL:

Url sollicitée: /comm/propal/card.php?id=3200&save_lastsearch_values=1
Referer: https://**************/comm/propal/list.php?leftmenu=propals
Gestionnaire de menu: eldy_menu.php

Modules/Applications

The following modules and applications are enabled:

api, syslog, user, ameliorationprojets, notification, tracking, paymentbybanktransfer, product, alertes, blockedlog, tickettotask, dav, ameliorationtiers, knowledgemanagement, stock, ameliorationtickets, productbatch, projet, qualite, fichedevie, ultimatepdf, modulebuilder, milestone, socialnetworks, categorie, fckeditor, ref, ameliorationproduits, bookmark, ameliorationnotedefrais, workflow, import, propal, export, mailing, expedition, heures, m2am, multicurrency, exports, planification, ameliorationcommandes, ameliorationfactures, accounting, agenda, bom, banque, barcode, commande, ecm, expensereport, facture, fournisseur, holiday, margin, mrp, salaries, service, societe, espaceclient, ticket, communication, mbisignature, timemaster, piecesref, produitstickets, ameliorationdevis, ameliorationutilisateurs, ameliorationexpeditions, ameliorationstats, cdav, supplier_proposal, gestionprix, reception, incoterm, stocktransfers, tax, ameliorationexports, fusion

Type gestionnaire de base de données

The database management system is mysqli.

Requête dernier accès en base en erreur

The last database access error is as follows:

SELECT s.rowid as socid, s.nom as name, s.client, t.rowid, t.titre as ref, t.total_ht FROM dolibarr_societe as s, dolibarr_facture_rec as t WHERE t.fk_soc = s.rowid AND t.fk_soc IN (1051) AND t.entity IN (1) AND t.paye < 1
Code retour dernier accès en base en erreur: DB_ERROR_NOSUCHFIELD
Information sur le dernier accès en base en erreur: Unknown column 't.paye' in 'WHERE'

Dolibarr Version

The Dolibarr version is 21.

Environment PHP

The PHP version is 8.3.

Environment Database

There is no response from the database environment.

Steps to Reproduce the Behavior and Expected Behavior

To reproduce the behavior, follow these steps:

Access a document.
View linked objects.

The expected behavior is that the linked objects should be displayed correctly.

Attached Files

There are no attached files.

Introduction

In our previous article, we discussed the technical error in Dolibarr, a popular open-source enterprise resource planning (ERP) software. The error, known as Bug V21 Linked Object, occurs when accessing a document and viewing linked objects. In this article, we will provide a Q&A section to help you better understand the issue and its impact.

Q&A

Q: What is the Bug V21 Linked Object error in Dolibarr?

A: The Bug V21 Linked Object error is a technical error in Dolibarr that occurs when accessing a document and viewing linked objects. The error is caused by an unknown column 't.paye' in the WHERE clause of the database query.

Q: What is the impact of the Bug V21 Linked Object error?

A: The impact of the Bug V21 Linked Object error is that linked objects may not be displayed correctly, leading to potential issues with data retrieval and manipulation.

Q: How can I reproduce the Bug V21 Linked Object error?

A: To reproduce the Bug V21 Linked Object error, follow these steps:

Access a document.
View linked objects.

Q: What is the expected behavior when viewing linked objects?

A: The expected behavior is that the linked objects should be displayed correctly.

Q: What are the system requirements for Dolibarr to experience the Bug V21 Linked Object error?

A: The system requirements for Dolibarr to experience the Bug V21 Linked Object error are:

Dolibarr version: 21.0.0
PHP version: 8.3.17
Database management system: mysqli
Operating system: Linux ************ 4.18.0-553.5.1.lve.1.el8.x86_64 #1 SMP Fri Jun 14 15:38:45 UTC 2024 x86_64

Q: How can I fix the Bug V21 Linked Object error?

A: To fix the Bug V21 Linked Object error, you can try the following:

Update Dolibarr to the latest version.
Check the database schema for any inconsistencies.
Verify that the column 't.paye' exists in the database table.

Q: What are the potential consequences of not fixing the Bug V21 Linked Object error?

A: The potential consequences of not fixing the Bug V21 Linked Object error are:

Data retrieval and manipulation issues.
Potential data loss or corruption.
System instability and crashes.

Q: How can I prevent the Bug V21 Linked Object error from occurring in the future?

A: To prevent the Bug V21 Linked Object error from occurring in the future, you can:

Regularly update Dolibarr to the latest version.
Monitor the database schema for any inconsistencies.
Verify that the column 't.paye' exists in the database table.

Conclusion

In conclusion, the Bug V21 Linked Object error in Dolibarr is a technical error that occurs when accessing a document and viewing linked objects. The error is caused by an unknown column 't.paye' in the WHERE clause of the database query. To reproduce the behavior, follow the steps outlined above. The expected behavior is that the linked objects should be displayed correctly. To fix the error, try updating Dolibarr to the latest version, checking the database schema for any inconsistencies, and verifying that the column 't.paye' exists in the database table.