-
-
Notifications
You must be signed in to change notification settings - Fork 825
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
Display public title and description on profiles and unsubscribe/subs… #18645
Conversation
(Standard links)
|
@seamuslee001 let me be the first to say, thank you very much for listening to user feedback This is a welcome improvement and I have tasked an Agileware team member to review this next week. Agileware Ref: CIVICRM-1577 |
@seamuslee001 I have tried to test this using CiviCRM 5.30.beta1 but it looks like the new fields were not created and there's no updates pending. Here's the error. Any tips how to resolve?
|
@agileware-justin so the fields were only added for 5.31.alpha1 not 5.30.beta1 https://github.com/civicrm/civicrm-core/blob/master/CRM/Upgrade/Incremental/php/FiveThirtyOne.php#L62 |
Thanks @seamuslee001 I did try first using civicrm-NIGHTLY-wordpress.zip ( 5.31.alpha1-202010080530 ) from https://download.civicrm.org/latest/ But there's something wrong with that one, site was completely cactus after installing. Will try again using 5.31.alpha1 - built a different way and see if that works. |
@seamuslee001 thanks again for this PR. Here is some feedback on the Group Settings Form:
Other comments, may or may not want to tackle in this PR:
|
Tested using CiviCRM 5.31.beta1 |
…cribe forms as appropriate if set Ensure that front end fields are shown correctly on the mailing subscribe form Re-arrange form as per Justin's comment
32d1f14
to
be44418
Compare
@agileware-justin I have sorted the mailing subscription page now and also I have re-ordered the group edit form to be a bit more sensible I would say. |
@jusfreeman are you able to re-review (against the now wp-friendly tarball :-) - there are new fixes |
Thanks @seamuslee001 @eileenmcnaughton reviewing now, will provide an update shortly. |
@seamuslee001 and @eileenmcnaughton results of my testing are detailed below. Items 4 and 5 need action.
|
Ok - those seem non-blocking & this is an improvement as it stands then so I will merge. You might like to do a follow up patch on those places.... |
…cribe forms as appropriate if set
Overview
This starts to make use of the new frontend title and description fields if on unsubscribe / subscribe / user dashboard pages
Before
Internal / Private group title & description fields would be used all the time
After
Public title or description or both fields used if set otherwise fall back on the internal fields
ping @artfulrobot @agileware-justin @demeritcowboy