-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BeerXML Import Not Working #65
Comments
Thanks for reporting the issue. Could you attach the file you are trying to import here? |
The path issue has been resolved and you can upload the xml file now. Thanks agains! |
Hey Matt. Import XML did indeed process the XML so I could see it formatted in my browser, but on submit browser timed out. Can’t get back to the website now. Did site go down?
——
***@***.***
… On Apr 14, 2021, at 8:58 PM, Matthew Kris ***@***.***> wrote:
The path issue has been resolved and you can upload the xml file now. Thanks agains!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#65 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATVC7AVOJNCVPHQMIV2DF3LTIY22LANCNFSM423MJVUA>.
|
disregard previous note. no longer seeing site timeout error. was able to import my xml. thanks.
——
***@***.***
… On Apr 14, 2021, at 8:58 PM, Matthew Kris ***@***.***> wrote:
The path issue has been resolved and you can upload the xml file now. Thanks agains!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#65 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATVC7AVOJNCVPHQMIV2DF3LTIY22LANCNFSM423MJVUA>.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The beerxml import fails with an invalid path message to my client's xml. I tried both Windows and Mac OS, Safari and Chrome and same result. I cannot manually alter the path information after selecting the file on my client.
The text was updated successfully, but these errors were encountered: