Hello guys,
Thanks for this app. Any chance to upgrade Dolibarr to v17? v16 is almost deprecated in terms of updates.
Thanks,
1 Like
I agree, dolibarr 17 would be greatly appreciated !
1 Like
Hello everyone.
Sorry for my absence to keep the project up to date.
At the moment I donāt have the time to do it and wonāt for a few more months.
As an idea for the person who will take over until I return, to overcome the problem of migration and PHP8, we must manage to load PHP7 for updates of version < 17.
2 Likes
I was trying to manually update from 16 to 17 with the dolibarr update script and procedure, so this is why it did not workā¦
Thanks anyway for your kind reply, i hope that you find the necessary time or that someone takes on and manages to maintain this project !
Tks very much to anybody has packaged Dolibarr v18.0.1. To tell the truth I have not yet installed it as I am somewhat afraid of the 2 versions (from v16) jump and itās usually safer to wait for 0.2 version for production use.
Do people have upgraded with success, or any difficulties ?
Hi, there.
Iām trying to find help to import a DB in Dolibarr on a Yunohost server.
Where can I go?
thanks
1 Like
Hello, we have one it yesterday. It seems working, I am waiting for feedbacks of the principal user.
The upgrade have ended with some warnings like this:
Warning: PHP Warning: Undefined property: stdClass::$LDAP_FIELD_LOGIN_SAMBA in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 70
Warning: PHP Warning: Undefined property: stdClass::$LDAP_FIELD_PASSWORD in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 71
Warning: PHP Warning: Undefined property: stdClass::$LDAP_FIELD_PASSWORD_CRYPTED in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 72
Warning: PHP Warning: Undefined property: stdClass::$LDAP_FIELD_TITLE in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 81
Warning: PHP Warning: Undefined property: stdClass::$LDAP_FIELD_DESCRIPTION in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 82
Warning: PHP Warning: Undefined property: stdClass::$LDAP_FIELD_SID in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 83
Warning: PHP Warning: Undefined property: stdClass::$LDAP_ADMIN_DN in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 115
Warning: PHP Warning: Undefined property: stdClass::$LDAP_ADMIN_PASS in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 116
Warning: PHP Warning: Undefined array key "telephonenumber" in /var/www/dolibarr/htdocs/core/class/ldap.class.php on line 1100
Warning: PHP Warning: Trying to access array offset on value of type null in /var/www/dolibarr/htdocs/core/class/ldap.class.php on line 1100
Warning: PHP Warning: Undefined array key "facsimiletelephonenumber" in /var/www/dolibarr/htdocs/core/class/ldap.class.php on line 1100
Warning: PHP Warning: Trying to access array offset on value of type null in /var/www/dolibarr/htdocs/core/class/ldap.class.php on line 1100
Warning: PHP Warning: Undefined array key "mobile" in /var/www/dolibarr/htdocs/core/class/ldap.class.php on line 1100
Warning: PHP Warning: Trying to access array offset on value of type null in /var/www/dolibarr/htdocs/core/class/ldap.class.php on line 1100
Warning: PHP Warning: Undefined property: stdClass::$LDAP_FIELD_SID in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 194
Warning: PHP Warning: Undefined property: stdClass::$LDAP_FIELD_PASSWORD in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 204
Warning: PHP Warning: Undefined array key "" in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 204
Warning: PHP Warning: Undefined property: stdClass::$LDAP_FIELD_PASSWORD_CRYPTED in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 205
Warning: PHP Warning: Undefined array key "" in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 205
Warning: PHP Warning: Undefined property: stdClass::$LDAP_FIELD_SID in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 221
Warning: PHP Warning: Undefined array key "" in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 221
Warning: PHP Warning: Undefined property: stdClass::$LDAP_FIELD_TITLE in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 223
Warning: PHP Warning: Undefined array key "" in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 223
Warning: PHP Warning: Undefined property: stdClass::$LDAP_FIELD_DESCRIPTION in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 224
Warning: PHP Warning: Undefined array key "" in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 224
Warning: PHP Warning: Undefined property: stdClass::$LDAP_FIELD_SID in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 194
Warning: PHP Warning: Undefined property: stdClass::$LDAP_FIELD_PASSWORD in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 204
Warning: PHP Warning: Undefined array key "" in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 204
Warning: PHP Warning: Undefined property: stdClass::$LDAP_FIELD_PASSWORD_CRYPTED in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 205
Warning: PHP Warning: Undefined array key "" in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 205
Warning: PHP Warning: Undefined property: stdClass::$LDAP_FIELD_SID in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 221
Warning: PHP Warning: Undefined array key "" in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 221
Warning: PHP Warning: Undefined property: stdClass::$LDAP_FIELD_TITLE in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 223
Warning: PHP Warning: Undefined array key "" in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 223
Warning: PHP Warning: Undefined property: stdClass::$LDAP_FIELD_DESCRIPTION in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 2
24
Warning: PHP Warning: Undefined array key "" in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 224
Warning: PHP Warning: Undefined property: stdClass::$LDAP_FIELD_SID in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 194
Warning: PHP Warning: Undefined property: stdClass::$LDAP_FIELD_PASSWORD in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 204
Warning: PHP Warning: Undefined array key "" in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 204
Warning: PHP Warning: Undefined property: stdClass::$LDAP_FIELD_PASSWORD_CRYPTED in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on l
ine 205
Warning: PHP Warning: Undefined array key "" in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 205
Warning: PHP Warning: Undefined property: stdClass::$LDAP_FIELD_SID in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 221
Warning: PHP Warning: Undefined array key "" in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 221
Warning: PHP Warning: Undefined property: stdClass::$LDAP_FIELD_TITLE in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 223
Warning: PHP Warning: Undefined array key "" in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 223
Warning: PHP Warning: Undefined property: stdClass::$LDAP_FIELD_DESCRIPTION in /var/www/dolibarr/scripts/user/sync_users_ldap2dolibarr.php on line 224
Info: LDAP user update ended with error
But we can login, so I am not sure if it is very relevantā¦
Hi ! Iām planning on migrating our workās dolibarr to a yunohost instance pretty soon, problem is our prod is 18.0.4 and yunohost package is 18.0.3 so migration breaks it allā¦ Is there any way i can circumvent this, or any plan to package dolibarr to a more recent version soon ? Thanks
V19, default/normal install from yunohost, can login with ldap, but if one uses other users created in dolibarr those users canĀ“t login through dolibarr login page when password is defined as āHTTPBasicPasswordā defined as $dolibarr_main_authentication='http'; on htdocs/conf/conf.php.
defining $dolibarr_main_authentication='ldap,dolibarr'; , doesnāt work, it premoves ldap user login ability from yunohost portal and all logins from dollibar page too.
so i tried v20, āyunohost testing branchā, and ldap works too out of the box but created users on dolibarr couldnāt login neither by login page or android app. the solution for both ways to work tested on v20 and working is to place $dolibarr_main_authentication='http,dolibarr'; on htdocs/conf/conf.php this way the superadmin can login by yunohost host portal, and users created in dolibarr can login via dolibarr login page or via dolidroid the app for android.
v20 also works very well didnāt find any problems, maybe the team can bump it up because v21 is the current stable by dolibarr.
1 Like
+1 your suggestion.
Application only users shouldnāt totally depend on LDAP. It should be done independently without creating new users in yunohost.
Thank you for your solution @spiritwalker.
With your tweak are you able to log out properly ?
I opened an issue about that here if you need more detailsā¦
Iām sorry for my late response my bees take me a lot of time when spring comes.
Yes i confirm your error, usually i donāt care as iām the only one administrator, and the other users are just for POS. on dolidroid, the android app, log out is done right, but from the pc and yunohost portal i do receive your error, iām going to try some tests as soon as i possibly can either to verify the situation our maybe find a solution.
iām not pro programmer but i manage around, iāll see to it.
p.s. but i remember having that issue before changing anything.
1 Like
No worries, beekeeping is the priority !
And it is not a critical bug as logout is (unpractical but still) manageable : deleting cookies and loggging out from YNH usually does the trick.
Hello,
there is a project to add a config panel to the app dollibar very usefull for associations.
Does some of you may be interested to do some tests and give us feedbacks ??
WARNING
Be aware about security-wise with this code. Running yunohost user group add with arbitrary group means that dolibarr would be able to add any yunohost user as admin and therefore become root in like 2 commands. For now it need adding a significant security weakness.
- This PR introduces the necessary logic/hooks to bridge Dolibarrās membership events with YunoHostās user system.
- When a new member is added in Dolibarr with a valid subscription (adhĆ©sion Ć jour), a corresponding YunoHost user is created using:
sudo yunohost user create USERNAME -F FULLNAME -p PASSWORD -d DOMAIN
sudo yunohost user update USERNAME --add-mailforward MAIL sudo yunohost user group add ADHERENTS USERNAME
If the membership ends, the user is removed from the group ADHERENTS.
If the user is deleted in Dolibarr, it runs:
sudo yunohost user delete USERNAME
Support for additional group management (e.g. COMMUNICATION) is also included:
Add user to communication group:
sudo yunohost user group add COMMUNICATION USERNAME
Remove user from communication group:
sudo yunohost user group remove COMMUNICATION USERNAME
Can be tested using :
yunohost app install https://github.com/Shervin-QZ/dolibarr_ynh/tree/testing_yunosync
yunohost app upgrade dolibarr -u https://github.com/Shervin-QZ/dolibarr_ynh/tree/testing_yunosync --debug
Hello, for all users using Dolibarr. We have recently debug the testing branch.
The problem was:
- Dolibarr need upgrade step by step new major versions, so the code was working well if installing a fresh Dolibarr from testing branch, but upgrading from 19* to 21* get issues with the LDAP.
we now rollback the branch testing to version 20* and the upgrade works fine- we could adjust some code
Whatās next ? We gonna soon push this new PR to master branch and the testing branch should be for the next version 21* of Dolibarr.
Sorry in fact the upgrade will upgrade do step by step the migrations needed to get the version 21*
2 Likes
Sorry, but is it still broken or ok now ?
Thanks for your work on it.
It must be ok with the last version 21.0.1~ynh4 which is on stable branchā¦
2 Likes
Hello @rodinux,
I am having a problem with upgrading the Dolibarr from 21.0.1~ynh4 to 21.0.2~ynh2. It looks like it is caused by a Yunohost script. Iāve tried upgrading it 5 times at least, but end up with the same result. Could you give me a tip on how to fix this please? Thank you! The upgrade log is at below:
PS: By the way, the Share with Yunopaste buttons didnāt work for this log and I had to create that hastebin manually.
Hello, someone have got the same issue here Sauvegarde Dolibarr par yunohost impossible
The script backup must have a misconfiguration on the precedent version, I am really sorry.
You can fix it editing the file manually, connected with ssh using nano editor
sudo nano /etc/yunohost/apps/dolibarr/scripts/backup
this line here must be edited
# Check if the group is set
if [ -z "${syncyunohost_main_group}" ]; then
Change it like this
# Check if the group is set
if [ -z "${syncyunohost_main_group:-}" ]; then
To quit the editor nano Ctrl + x and said yes to keep the changes before closing the editor.
Then the backup and so the upgrade should works.
2 Likes
No need to be sorry my friend, it was just a little inconvenience. Your suggestion fixed the problem and it got upgraded successfully. Thank you for your kind help!
Iād also like to mention a warning that appears after the first installation and then each update:
Warning, your config file (htdocs/conf/conf.php ) can be overwritten by the web server. This is a serious security hole. Modify permissions on file to be in read only mode for operating system user used by Web server. If you use Windows and FAT format for your disk, you must know that this file system does not allow to add permissions on file, so canāt be completely safe. This security warning will remain active as long as the vulnerability is present.
That file comes with 0640 permissions at the installation. To fix this, I change the permissions of the mentioned file to 0444 manually and that warning then disappears. Or maybe 0440 would be more secure. Maybe you consider fixing the permissions of that file on the next update.
Thanks again and have a lovely weekend.
1 Like