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
The stream name search tool on the add station window was not functional (i.e., the search tool was not populated with the stream names from the lookup table);
An incomplete stream layer still occasionally appears on the add station window map even after clearing my cache and reloading the page;
Selecting add station received a "token error" during 1 of my 3 attempts (see attached); and
The token error mentioned in 3 above remained present when attempting to enter new information even after cancelling the error-related entry using the cancel buttons on both the add station popup and the main page.
Method tab
1) Domain for backpack model is incorrect and shows canoe/barge and raft/boat model domains instead; and
2) Fields in canoe/barge and raft/boat equipment type tabs are populated with information previously entered in fields in the backpack tab when you toggle between these equipment tabs. The information from one tab should not carry forward to another tab. Equipment type fields should only populate when the user has entered the information into them.
Catch tab
All good.
General submission
A token error was encountered when submitting entries (see attached). No events were successfully created due to this error.
The text was updated successfully, but these errors were encountered:
Fields in canoe/barge and raft/boat equipment type tabs are populated with information previously entered in fields in the backpack tab when you toggle between these equipment tabs. The information from one tab should not carry forward to another tab. Equipment type fields should only populate when the user has entered the information into them.
This is also not related to the migration to firebase hosting. It appears exactly the same in the current production app. I've opened a new issue for it.
From Craig (9/21/2022):
The text was updated successfully, but these errors were encountered: