You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the Admin website, there is a single place where the common name and alternates are entered. This information then is used in several places on the Production site, although which common name is used is inconsistent. For example for Dendrophylax lindenii:
On the Species page, both common names are displayed, Ghost Orchid and Palm Polly [listed in alphabetical order].
On the Simple Key, Palm Polly is displayed.
On the Go to Species page [click on image in Simple Key] Ghost Orchid is displayed.
Cypripedium acaule shows a similar problem.
The desired behavior is to have all Common names appear on the Species page, and the preferred Common name appear on other pages (such as the Simple Key and the Go to Species page.)
The text was updated successfully, but these errors were encountered:
The issue with the Common name is a tricky one. Some orchids have several although I try to limit it to just 3 on the site. But there generally is a preferred Common name which should be displayed in the Simple Key and the Go to Species page as well as the Species page. Under the current system, each of these pages displays a different name.
I think the change I’m looking for would be on the Admin site where there is an entry for the preferred common name then another place for other Common names.
On the Admin website, there is a single place where the common name and alternates are entered. This information then is used in several places on the Production site, although which common name is used is inconsistent. For example for Dendrophylax lindenii:
Cypripedium acaule shows a similar problem.
The desired behavior is to have all Common names appear on the Species page, and the preferred Common name appear on other pages (such as the Simple Key and the Go to Species page.)
The text was updated successfully, but these errors were encountered: