A new wiki page - a Troubleshooting FAQ for hsg-project. Comments, suggestions?

[joewiz]

Hi all @HistoryAtState/editors,

I've started a new page on the wiki, https://github.com/HistoryAtState/hsg-project/wiki/troubleshooting. It only has a few items now, but these are the tried-and-true solutions to common problems I and other hsg-project users have. Please check it out and reference it when you have problems. And if you have any comments or suggestions for new entries, please let me know.

Cheers,
Joe

[mcdanielhn]

Great idea! Thanks! I have also found that eXide does not always keep me logged in as admin even when I select "Remember me." Often in the same session, I get kicked out, which messes with the S3 cache update. Maybe a reminder to double check login? I think a reminder is in the instructions, but it would also be good to have here.

[mcdanielhn]

I also really like the trick about "Opening this repository in GitHub," because the uncommitted changes don't always show up in GitHub, and it's nice to have a reminder. Again, I think this is in the instructions, but a good note here.

[KerryHite]

Great resource. Thanks, Joe!

…

On Mon, Sep 25, 2017 at 11:13 AM, Joe Wicentowski ***@***.***> wrote: Hi all @HistoryAtState/editors <https://github.com/orgs/HistoryAtState/teams/editors>, I've started a new page on the wiki, https://github.com/ HistoryAtState/hsg-project/wiki/troubleshooting. It only has a few items now, but these are the tried-and-true solutions to common problems I and other hsg-project users have. Please check it out and reference it when you have problems. And if you have any comments or suggestions for new entries, please let me know. Cheers, Joe — You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub <#35>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AT4W31kRok_wh7cK0Z_JkosJpZqQqFrcks5sl8MggaJpZM4Pi5LW> .

[joewiz]

@mcdanielhn I've seen this before too. My suggestion is to reload the eXide window before starting the S3 cache update. After you reload, it will show the actual login status. Sometimes it is stale, showing the user as "admin" when the login session has in fact expired. Could you give this a try and let me know if it works?

And thanks to both you and @KerryHite for this feedback!