Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fields vanish on the config screen in some situations #20

Closed
vingle opened this issue Apr 2, 2020 · 10 comments
Closed

Fields vanish on the config screen in some situations #20

vingle opened this issue Apr 2, 2020 · 10 comments
Labels
question Further information is requested
Milestone

Comments

@vingle
Copy link
Contributor

vingle commented Apr 2, 2020

Sorry this bug isn't more detailed - this is a behaviour I experienced once - and you can currently see it on the demo at: https://corona.civicrm.jaapjansma.nl/. Here it's the fields from Prefix until Lattitude (including address & name) that are missing ->

image

@bjendres bjendres added the bug Something isn't working label Apr 3, 2020
@bjendres bjendres added this to the 1.1 milestone Apr 3, 2020
@bjendres
Copy link
Member

bjendres commented Apr 3, 2020

@jensschuppe does this make sense to you?

@jensschuppe
Copy link
Contributor

From the Covid-19 channel on chat.civicrm.org (which I suppose is the same issue as described here)

The extension determines which fields are available when the settings cache is generated. That is, changing individual or address field configuration at civicrm/admin/setting/preferences/display?reset=1 requires a cache clear for the mutualaid settings to take up these changes. Does clearing the cache solve the issue?

That's fixed it - tho not sure if it was the clearing caches or the upgrade that fixed it?

@vingle Can you confirm that there's nothing else wrong with the fields after clearing caches?

@vingle
Copy link
Contributor Author

vingle commented Apr 3, 2020

From the Covid-19 channel on chat.civicrm.org (which I suppose is the same issue as described here)

The extension determines which fields are available when the settings cache is generated. That is, changing individual or address field configuration at civicrm/admin/setting/preferences/display?reset=1 requires a cache clear for the mutualaid settings to take up these changes. Does clearing the cache solve the issue?

That's fixed it - tho not sure if it was the clearing caches or the upgrade that fixed it?

@vingle Can you confirm that there's nothing else wrong with the fields after clearing caches?

After Jaap both cleared caches and updated his demo site from 1.1-dev to latest, it was fixed. Presumably that was the caching.

@jensschuppe
Copy link
Contributor

Thanks for the prompt feedback @vingle!

@jensschuppe jensschuppe added question Further information is requested and removed bug Something isn't working labels Apr 3, 2020
@vingle
Copy link
Contributor Author

vingle commented Apr 3, 2020

As flushing CiviCRM caches isn't straightforward - would it be viable to either flush caches on page save, or add a flush cache button? My understanding (which could be wrong) is that you can only flush CiviCRM caches thru SSH or ftp, unless something like https://www.drupal.org/project/civicrm_clear_all_caches is installed.

@jensschuppe
Copy link
Contributor

Flushing caches is possible on the Drupal admin UI (not sure about WordPress and Joomla) and also by calling civicrm/menu/rebuild.

There's only a need for flushing caches when you change something on the civicrm/admin/setting/preferences/display settings page. So this should be a quite administrative task which is usually not done that often. Maybe this behavior can be mentioned in the docs of this extension.

@vingle
Copy link
Contributor Author

vingle commented Apr 3, 2020

by calling civicrm/menu/rebuild

Ah, that's the one - thanks. I tried flushing cache's on Jaap's demo via admin/config/development/performance - but it didn't make any difference. I normally use flush-all from the admin menu drop down but it's not installed. Not sure if that's the same process - or if either of these methods clears tempaltes_c files & civi-specific cache.

There's only a need for flushing caches when you change something on the civicrm/admin/setting/preferences/display page

That's strange – when this bug emerged for me earlier in the week when I noticed the country field wasn't in config - I hadn't touched that page (I had maybe disabled some profiles/custom field sets?). But the issue was resolved before I could document it so don't have more information I'm afraid.

@bjendres
Copy link
Member

bjendres commented Apr 3, 2020

@jensschuppe Couldn't we just show a popup when changing the configuration saying: "if you have changed anything in the form layout, please press here to clear the CiviCRM cache"?

@jensschuppe
Copy link
Contributor

The cache will have to be cleared when making changes to CiviCRM core display settings, not the extension settings. So the popup will have to be shown after submitting the core display settings form.

@bjendres
Copy link
Member

bjendres commented Apr 3, 2020

Ah, ok, I misunderstood. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants