That is because the visual editor only is used when the resource is named exactly WebLinks. Specify will only use app resources that define web links if they are named exactly. This is also true for DataObjFormatters and UIFormatters. Since the resource is cloned, it adds a (2), which means Specify doesn’t recognize it as a resource that can be edited visually nor will it use it as a valid source for web links.

Grant is correct.

Though, I guess we could make the process better.
Mainly:

• either disable the clone button for such resources (easy, but not ideal)
• or, when clone is pressed, show a dialog prompting the user to pick the destination location for the resource (and ensure the destination does not have a resource by this name already)
  • though I guess this dialog would be useful for most app resource types
  • OR, when creating a new app resource, give an option to select an existing app resource (or even ability to clone from a default app resource that ships with specify) - this is kind of what Form Definition creation has already

either disable the clone button for such resources (easy, but not ideal)

During today's development meeting, it was decided that this would be the solution for now.

@grantfitzsimmons,
Can yo confirm that those are the three resources we need to disable the clone button for?

• WebLinks
• DataObjFormatters
• UIFormatters

We need to disable the clone button for any app resources that are recognized by name alone, which most likely includes:

• TypeSearches
• WebLinks
• DataObjFormatters
• UIFormatters
• QueryFreqList
• QueryExtraList
• DataEntryTaskInit
• InteractionsTaskInit
• UserPreferences
• CollectionPreferences
• ExpressSearchConfig
• leaflet-layers