This looks like a hardcoded limitation in CiviCRM, and changing that would require some development work (i.e., there's no workaround or trick to it, just needs code changes).
Interestingly, there's a comment in the code that indicates a desire to add support for ACLs instead of the sledgehammerish 'view all contacts' requirement: https://github.com/civicrm/...
If you did this as a Price Set you would be able to have some info in the post-field-help, and you can set the 'label' to be different to the membership type if you want eg
and actually the Price Options do have a pre/post help options but they show inline, presumably some minor theming could address that
Currently at https://dmaster.demo.civicrm.org/...
Just sharing that we have developed and released a CiviCRM extension which solves this problem, see https://github.com/agileware/au.com.agileware.membershiprelationshiptypeeditor
Membership Relationship Type Editor for CiviCRM - edit existing Relationship Types and re-calculate inherited memberships
We hope this is useful to people using CiviCRM.
If your existing members are getting a new recurring contribution you could potentially check for a new recurring contribution instead of a new membership? I think that would solve the issue.
If you try and it does not you might try something like:
a first rule to check for relevant new memberships and add them to a group
a second rule that adds them to a ...
Yes it's intentional that there are no links if there's mixed record types in a profile.
It's been like that for a LONG time:
Also for reference:
UPDATE: Based on the comments, I think this is what is desired:
Create a profile ...
You can probably still change it via the API - specify the new end date on the existing membership, but that may have unintended consequences.
How did you do the refund? What status is the contribution? Maybe changing the end date should be part of the refund process.
Although the header and footer would allow me to put description above and below it wasn't exactly what I needed.
The best solution for me was leveraging the use of the Civicrm webform integration and adding the required mark up and form alters where I required them to achieve the required display.
The error message shows future start and join dates. Civi is attempting to the determine the status as of the time of import, but none of the default status rules cover that scenario hence the error message. 'New' only applies from the 'member since' / 'join date' so is not applicable.
One option is to change your join dates to be the current time so that ...