Hide old projects

eloib · April 17, 2024, 9:37am

Hello.

When I’m placing an order with a supplier, I can link it to the corresponding project. But the list of projects shows all projects (opened and closed several years ago).

Is there any way or solution to hide the closed projects?

I have tried using the PROJECT_HIDE_UNSELECTABLES and PROJECT_ALWAYS_DISCARD_CLOSED_PROJECTS_IN_SELECT variables in “configuration/other configurations” without success.

Thanks in advance.

jonbendtsen · April 17, 2024, 3:57pm

I think this warrants a bug report on Issues · Dolibarr/dolibarr · GitHub

eloib · April 17, 2024, 5:50pm

Ok. I have done it. Thank you

jonbendtsen · May 14, 2026, 5:52am

@Polvaris is it the very same as described here that you experience?

github.com/Dolibarr/dolibarr

`supplier_proposal`: Project assignment not saved – neither on creation nor after

opened 10:19PM - 08 Apr 26 UTC

glu000

Bug

### Bug The project field in supplier proposals (`supplier_proposal/card.php`) …is visible in both the creation form and the edit view, but the selected project is **never saved to the database** — neither on creation nor when changed afterwards. This is inconsistent with supplier orders (`fourn/commande/card.php`), where project assignment works correctly in both cases. ## Root Cause Analysis ### 1. Creation form ignores `PROJECT_CAN_ALWAYS_LINK_TO_ALL_SUPPLIERS` `supplier_proposal/card.php` line ~1415: ```php $formproject->select_projects(($soc->id > 0 ? $soc->id : -1), ...) ``` The project dropdown is always filtered by the supplier's `socid`. The global setting `PROJECT_CAN_ALWAYS_LINK_TO_ALL_SUPPLIERS`, which allows showing all projects regardless of the linked supplier, is **not evaluated**. This means: if no project is explicitly linked to the supplier, the dropdown is empty, `GETPOSTINT('projectid')` returns 0, and `NULL` is written to `fk_projet`. In contrast, `fourn/commande/card.php` correctly applies this setting: ```php $formproject->select_projects((!getDolGlobalString('PROJECT_CAN_ALWAYS_LINK_TO_ALL_SUPPLIERS') ? $societe->id : -1), ...) ``` ### 2. Edit view has inverted logic for the same setting `supplier_proposal/card.php` line ~1658: ```php $form->form_project(..., (getDolGlobalString('PROJECT_CAN_ALWAYS_LINK_TO_ALL_SUPPLIERS') ? $object->socid : -1), ...) ``` The condition is **inverted** compared to the purchase order. When the flag **is set**, supplier proposals filter by socid (restricting the list), while purchase orders show all projects. The intended behavior is the opposite. ### 3. `$fields` array does not declare `fk_project` `supplier_proposal/class/supplier_proposal.class.php` line ~245: ```php public $fields = array( 'ref' => [...], 'note_public' => [...], ); ``` `fk_project` is missing from the `$fields` declaration. While `CommonObject` declares `public $fk_project`, the missing `$fields` entry affects internal framework behavior (e.g. `setProject()` in `CommonObject` checks `$this->fields['fk_project']` to select the correct SQL branch — though it falls back to the legacy `fk_projet` column, which happens to be correct for this table). ## Affected Files - `htdocs/supplier_proposal/card.php` - `htdocs/supplier_proposal/class/supplier_proposal.class.php` ## Reference `fourn/commande/card.php` and `fourn/class/fournisseur.commande.class.php` serve as the working reference implementation. ### Dolibarr Version 22.0 ### Environment PHP n/a ### Environment Database n/a ### Steps to reproduce the behavior and expected behavior **On creation:** 1. Go to *Supplier proposals* → *New supplier proposal* 2. Select a project from the project dropdown 3. Save the proposal 4. **Expected:** project is saved. **Actual:** project field is empty in the saved record **After creation:** 1. Open an existing supplier proposal 2. Click the edit icon next to the project field 3. Select a project and confirm 4. **Expected:** project is updated. **Actual:** project field remains empty ### Attached files _No response_

Polvaris · May 14, 2026, 12:06pm

Yes, the same issue that I had described yesterday 13/05/2026

When I’m placing an order with a supplier, I can’t link it to the corresponding project; OR

When I create order under a project and insert a supplier - the project tab goes blank and no projects are listed
I configure all my projects as customer specific - I have no “generic” or “unassigned” projects

Background: I recently upgraded from 19 to 23 because I changed server from CentOS 7 (EOL June 2024) to Ubuntu 24. I did not experience this problem in Dolibarr 19.

Gemini AI tells me that I have run into “a confirmed hardcoded JavaScript refresh limitation in Dolibarr. When a form undergoes a core AJAX reload (triggered by changing a Third Party), Dolibarr’s client-side script purges uncommitted dependent selections, completely ignoring backend database override constants. To bypass this JavaScript issue entirely, you must use a workflow where the vendor and the project never interact on the same creation screen.”

Gemini suggests the following:
Fix 1: The Draft Bypassing Method (Easiest)
Fix 2: Change Project to “Universal” (Zero Code Required)
Fix 3: Direct Assignment from the Project Management Panel

How I managed:
I have to use Fix 1 - but it is slow and tedious
Fix 2 - is no the way I configure my projects - since all are tied to a Primary Customer
Fix 3 - is the specific problem that I am experiencing.

Thanks in advance

Polvaris · May 14, 2026, 12:11pm

Yes, it is - the same issue that I had described yesterday 13/05/2026