-1

I tried to update dolibarr from 16.0.3 up to the current version 20.0.2. So far it succeeded, but I do have an error code when I want to use a custom module for time-tracking.

To me it seems that there is an invalid dolibarr internal filter-order which then may result in an invalid sql-order. At this point, I would like to highlight that there was not a problem with this module before the update. Here is the error-code:

sql=SELECT DISTINCT p.rowid, p.ref FROM llx_projet as p LEFT JOIN llx_element_contact as ec ON ec.element_id = p.rowid WHERE p.entity IN (1) AND ( p.public = 1 OR ( ec.fk_c_type_contact IN (161,160) AND ec.fk_socpeople = 7) ). 

This error message always appears above in my dolibarr

I appreciate your help Screenshot of error message

5
  • 1
    What error code? ... Seems that there should be more information to the error message than just a SQL statement with no other context, so add the entire error message. Commented yesterday
  • I just added a pic with the entire error message that pops up in my browser Commented yesterday
  • 2
    Can you please add the error as text, not as an image? Those make it harder to read, edit and search for Commented yesterday
  • @tehomas: You really have to add the text of the image to your question. Images, especially those only containing texts, are not helpful and the SO question editor does not support optical character recognition so you have to use an off-site service for that and/or just copy and paste from your source/type it from the image into the editor. This is important on SO for various reasons, please let me know if this is not clear to you why so I can offer more background information. Commented yesterday
  • Additionally what would be helpful is not only to but the SQL that likely causes the error (it's good to have it), but also which actual error/diagnostics. This currently seems to be buried in the image data which is hard to locate (and it contains a lot of data), so this should benefit your question if you make the main error information more prominent. Commented yesterday

1 Answer 1

1

You have upgraded to the wrong version. The 20.0.2 release is an update for the 20.0 branch.

But you are coming from the 16.0.3 version, so the 16.0 branch.

Please follow the upgrade instructions for that branch first, then do the upgrades from one major version to the other.

This is important because this is how the upgrades are being tested by most users. Jumping over versions can create problems with the data-base structure as for example the 20.0 line-up was only thoroughly tested with the 19.0 data-structure, and then more and more less with the other versions you skipped over: 18, 17 and 16 <- you are here.

Special rules may apply, watch out for them in version specific upgrade and installation notes.

So restore your backup to 16.0.3, then upgrade it to the latest 16.0, 16.0.5, and always follow the instructions from the release announcements.

The smaller the upgrade steps are, the more stable will be your experience.

Always relate to the documented dollibar installation and upgrade instructions and keep notes about your system and the upgrade procedure you apply to better understand in case of error which step might have introduced it.

Sign up to request clarification or add additional context in comments.

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.