Esri / solutions-erg-widget

The Emergency Response Guide (ERG) widget allows users to determine potential hazards based on the type of chemical spill and user-selected location on the map.
Apache License 2.0
6 stars 4 forks source link

Publishing ERG with incorrect credentials #79

Closed adgiles closed 6 years ago

adgiles commented 6 years ago

Issues were identified with the GRG widget with errors not being caught and processed within the publishing workflow:

https://github.com/Esri/solutions-grg-widget/issues/172 https://github.com/Esri/solutions-grg-widget/issues/173

The same fixes that addressed these issues need to be made to the ERG widget

adgiles commented 6 years ago

Addressed in PR: https://github.com/Esri/solutions-erg-widget/pull/80

Check list tests need updating to test different accounts:

topowright-zz commented 6 years ago

@adgiles @dfoll @kgonzago if I understand this correctly only a user of the same Portal/Online org will be able to use the widget to publish content. To go further to make sure I am being clear the person who registers the app must only share with other users who are apart of that same org/portal. If that is the case then I am getting the correct feedback in the widget

@adgiles can we make the text populate to like this: You are currently signed in as: 'wright9739'. You do not have access to this resource: https://arcgisfordefense.maps.arcgis.com/sharing/rest/portals/selfERG- Publishing Issueswith Web AppBuilder for ArcGIS

I would like to see the first two lines without having to shift the widget to see the text: image

topowright-zz commented 6 years ago

The logic is correct I am requesting that we just shift the text in the dialog

adgiles commented 6 years ago

@topowright Correct you must be a member of the portal/org that the application is being hosted on to publish content.

I have addressed the issue of having to scroll to see the whole line in PR #82. But the only way i could do it was to wrap the line mid URL as there are not spaces to make a clean break.

It is unlikely that the user will get to see this message now due to the new publishing workflow addressed in issue #81

topowright-zz commented 6 years ago

This has been addressed and pushed to Devtopia