Hi, I’ve been searching on the forum but I can’t find.
I upgraded from 8.0.2 after several upgrades I ended on 19.0.3
All working except the proposal edit of items. Making a proposal is ok but when Validated If I want to “edit” items dolibarr doesn’t show the “pencil” icon on each item so I can’t modifiy proposal.
Version 19.0.3
Linux Server on a hosting I think It’s a Debian 4.18.0-553.lve.el8.x86_64
PHP ver 7.4.33
click the modify button below the proposal lines
and also, your user does need permissions to edit/create/change/write a proposal and possibly other users proposals if they don’t own this proposal
Hi @jonbendtsen , Of course i checked that before. If you see my url I’m editing, this url is generated when you press “MODIFY” Button. I’m also with SuperAdmin. Anyway I logged with the user who created the proposal, try to MODIFY and same, no edit icons. I’m stuck on this.
Can you help?
okay, that is strange. What I also see is that on your modification screen it says that your proposal is still Validated.
When I validate a proposal, then modify it to edit it, it says it is in draft mode
This picture is from my production 18.0.5
And this picture is from my demo 20.0.0
in both cases after I clicked modify it showed that my proposal is in draft mode, where as yours is in validation mode?
Please go into Commerce in top menu, then list proposals in left side menu.
Limit the search fields so you only get this particular proposal and show us the status of it on that page
Hi @jonbendtsen Here you are, in Proposal list also says it’s “validated”. Could be something got from the old “8.0.2”. I upgraded from that version but the “import database didn’t worked well” so I did this: Completed a fresh install on 19.0.3 then I uploaded the database from 8.0.2 using phpmyadmin and later did the dolibarr documents upload. Seems it could be something wrong with this “upgrade proceeding”. Any solution?
I think you need to import the database for real.
usually when you start a newer version, then it wants to upgrade some data in the database, and perhaps that didn’t happen this time?
