Don Pobanz

Are we closer to getting a solution to this? Is a newer release than 1.3.0 going to be available for this? My server is running Ubuntu 16.04 and I would like to move to Ubuntu 18.04 but churchinfo needs to continue to function.

We have used the "Run a Free-Text Query" from the reports, query menu to get a couple of custom reports. This probably does not give you the flexibility you might need, but is an option. I wish I had an answer. This whole reports area needs attention.

Fixed! I had to go to phpMyAdmin and select both records ('usr_LastLogin' and 'usr_ShowSince') so they could be updated at the same time. This worked as expected. Thanks Michael Wilt!

Michael Wilt, thanks for getting me pointed in the right direction. However, the dates for both 'usr_LastLogin' and 'usr_showSince' are currently set by default to 0000-00-00. When trying to update one, it tells me the other one is invalid and phpMyAdmin won't save the table. I am suspecting that I can't use phpMyAdmin to do this and so have been trying to see how to change the default values by going to the database via the mysql command line.

I am trying to set up a new user 'judy' with churchinfo 1.3 but get the following error: Cannot execute query. INSERT INTO user_usr (usr_per_ID, usr_Password, usr_NeedPasswordChange, usr_LastLogin, usr_AddRecords, usr_EditRecords, usr_DeleteRecords, usr_MenuOptions, usr_ManageGroups, usr_Finance, usr_Notes, usr_Communication, usr_Admin, usr_Style, usr_SearchLimit, usr_defaultFY, usr_UserName, usr_EditSelf, usr_Canvasser) VALUES (407,'5f4dcc3b5aa765d61d8327deb882cf99',1,'2018-02-22 23:36:21', 0, 0,...

Is there an estimate of how many churches/organizations are actively using chruchinfo?

Edwin Mulder, thank you for posting this. It worked for me with Ubuntu 16.04. I didn't reboot but restarted the mysql server with: sudo /etc/init.d/mysql restart I can now combine members once more when creating a directory. Thanks!

I ran into the same problem when updating to Ubuntu 16.04. Here is the response Michael Wilt gave me: Yeah some of the newer installations of MySQL have only_full_group_by turned on. I have started fixing this but it is obviously not yet finished in 1.3.0. In most cases this can be fixed by adding the selected columns which are missing to the group by clause. The brute-force fix is to turn off only_full_group_by in the MySQL configuration settings. This should be fixed in the next release. Mike