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
I have added a Documenter entry and attached it to every available Datasource page (new, edit, info, and root) and I still cannot get it to show for custom datasources. I would like to explain when someone lands on the page of a datasource that cannot be edited with the GUI, that they need to go into the files and edit the code. I thought this page would be the "info" page since that is what shows in the URL, but adding documentation to that doesn't seem to work.
Is it just me this doesn't work for? Is there a secret item in the select list I need to choose? Is this kind of page out of reach of Documenter?
Thanks for reading.
The text was updated successfully, but these errors were encountered:
My guess is that Documenter is just not aware of these pages. Actually, I'm not sure right now how their URL differ from the other data sources. Could you post an example URL, please?
An uneditable DS looks like http://site.name/symphony/blueprints/datasources/info/ds_name/ while an editable one looks like http://site.name/symphony/blueprints/datasources/edit/ds_name/ so it is distinct.
Thanks for the link, I will try to look at it today.
I have added a Documenter entry and attached it to every available Datasource page (new, edit, info, and root) and I still cannot get it to show for custom datasources. I would like to explain when someone lands on the page of a datasource that cannot be edited with the GUI, that they need to go into the files and edit the code. I thought this page would be the "info" page since that is what shows in the URL, but adding documentation to that doesn't seem to work.
Is it just me this doesn't work for? Is there a secret item in the select list I need to choose? Is this kind of page out of reach of Documenter?
Thanks for reading.
The text was updated successfully, but these errors were encountered: