Exactly this problem occurred again today (still 5.67.3). Users could not find contacts using Quicksearch, running 'Cleanup Caches' fixed the problem.
Yes, that problem the include_path was me
No, no memory of that at all. I can't test as the latest (5.72 or 5.73 nightly) crashes on install after the tarball is extracted. I'm assuming for now that I'm too early into testing the tarball extraction as from I gather so far this isn't supported. I could be wrong but I certainly can't get it to work anyway.
Speaking as a likely migrator from D7, we might not be the target market but there will be IMHO a very significant number of D7 installs that will think about moving to Standalone. The attraction is obvious - no CMS to battle with. So a simple install, not requiring Composer or SSH access, would be great - and would also be great for those entirely new users as well.
@wmortada agreed re. composer, thanks
Agreed, that's why I'm trying to make the case for implementers of Civi that aren't as expert as most folks on here.
PS. You may be thinking - so why not use Wordpress instead of D7. To be honest, I think I might be allergic to WP...and it would be so good to install & support Civi without having to bone up on some CMS.
Re managing deployments without shell access - last week I met a user who wanted another instance of Civi in addition to the one they have. I implemented it the following day - I used Softaculous to install another D7 (10 minutes) using a subdomain that I created and then installed Civi 5.67.3. Adding the usual extensions and then persuading it to go straight to Civi when logging in took maybe an hour or so. Then I added daily backups ( I don't trust other people's backups). All done using cPanel, no shell access. Upgrades are really easy in this environment as I mentioned above. Part of the problem in this discussion - and I mean this with great respect (and indeed awe) to the techys who work on Civi - is that when you are familiar with stuff like Composer and shell access it's easy to think others are also OK with it. I used to be a similar sort of techy many years ago, but most of my IT skills (PL/1, JCL, Smalltalk) are out of date/unused today - but can still help using tools like cPanel and really don't want to get into messing about with something like Composer and using shell access. I'm probably in a very small minority of people who give IT help pro bono, since as I guess most Civi installs are handled by IT companies with much greater skills then I have. I was really hoping that Standalone would succeed Civi with D7 but from this discussion I'm less certain.
Sure - the problem was (is) that 5.70 beta didn't work when I downloaded it - the problem with it was repeatable so I concentrated on 5.69.2 which did work.
In 5.69.2 I can update contact 1 through the contact summary screen - but can't through the link provided by the system status, so it sounds like it's the breadcrumbs problem. I'll check this when I can get 5.70 working.
There is a lack of room in drop downs to display field names, so that in some cases it's hard to know what the field name is. For example, selecting the phone type for a contact shows only the first letter of the phone type - only 'M' for mobile. Or 'Website Type' which is undecipherable. Tested on both Firefox and Chrome browsers. This is using the 5.69.2 Standalone release.
Here's the problem: 1. Create the group 2) 'Add to group' screen appears - enter contact name & search 3) select contacts found and click 'Add contact to whatever-you-called-the-group' 4) then 'Add to group' appears but when you click it error message 'Select Group is a required field.' appears but there is no group to select. In fact I couldn't find a way to add a contact to a group at all as the actions for a contact are restricted to just a few actions. This is caused by permissions so not actually a problem so close. Using the 5.69.2 version of Standalone
Here's the problem: 1. Create the group 2) 'Add to group' screen appears - enter contact name & search 3) select contacts found and click 'Add contact to whatever-you-called-the-group' 4) then 'Add to group' appears but when you click it error message 'Select Group is a required field.' appears but there is no group to select. In fact I couldn't find a way to add a contact to a group at all as the actions for a contact are restricted to just a few actions. This is caused by permissions so not actually a problem so close. Using the 5.69.2 version of Standalone
Messages from Civi don't appear as expected e.g. when testing outbound email, check the mail() button and click 'Send and Save email' and no message will appear. This is 100% reproducible. Sometimes messages will appear a couple of screens after they have been created, but not always. Using the 5.69.2 version of Standalone.
That's funny, I'll remove it before anyone spots it!
Yes, clearing caches fixed the problem. I will try to reproduce on dmaster. The only recipe I can give is to have 25-30 people all accessing Civi using contact id as the primary search which is not practical of course.
Yeah, exactly my thoughts too when I wrote it. This is a system where contact info is confidential and clients are referred to by their contact id, so users tend to use Quicksearch a lot. The only clues i can give is that it was 100% solid for the user, and me too when I used masquerade - but I could see the contacts when I was not masquerading. And 'Cleanup caches' fixed it. The ACLs are simple - the 'standard' users have access to 10 groups (this user was 'standard') and the user was in the correct group. I provided users with an SK based contact id search as a standby - it will be interesting to see if this still works when quicksearch doesn't.
Contact id quicksearch has broken in 5.67.3, albeit occasionally. User cannot locate any contacts by id at all, and using Drupal 'masquerade I verified this to be the case. The fix was to run the 'Cleanup Caches' option. What may be a clue is that this system uses ACLs and although this user would have been restricted by ACLs she would have had access to the contacts she was searching for. As an administrator I could see the contacts when she couldn't which does seem to point to ACLs as the problem.