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

CRM-20180 - Documentation URLs should contain "stable" *or* "current", not both #9897

Merged
merged 1 commit into from
Feb 25, 2017

Conversation

totten
Copy link
Member

@totten totten commented Feb 25, 2017

Examples:

Both examples include the redundant formulation "user/en/stable/current" and
point to non-existent pages. Use either "stable" or "current". It would be
silly for one installation to contain a mix of links for "stable" and
"current". It appears that formatDocUrl() aims to normalize these.


…, not both

Examples:

 * In "Administer => Communications => Scheduled Reminders", the green box has
   a link to "learn more". This links to "https://docs.civicrm.org/user/en/stable/current/email/scheduled-reminders/"
 * In "Search =>= Advanced Search", view the help for "Views for Display Contacts".
   The help message includes a link to "https://docs.civicrm.org/user/en/stable/current/organising-your-data/profiles"

Both examples include the redundant formulation "user/en/stable/current" and
point to non-existent pages.  Use either "stable" or "current".  It would be
silly for one installation to contain a mix of links for "stable" and
"current".  It appears that `formatDocUrl()` aims to normalize these.
@colemanw colemanw merged commit e887e8e into civicrm:master Feb 25, 2017
@totten totten deleted the master-doclink branch February 25, 2017 04:11
monishdeb pushed a commit to monishdeb/civicrm-core that referenced this pull request May 2, 2017
CRM-20180 - Documentation URLs should contain "stable" *or* "current", not both
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants