-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
When searching for messages the result cannot be opened #79
Comments
Hi @oers I can't reproduce it locally, following the same steps appears to work as expected. Could you give a bit more info, e.g. how many messages MailHog was storing, which page you were on, are you running a single MailHog binary or separate Server/UI binaries, or anything else you can think of that may be relevant! |
also happens for me. From the main page, at http://localhost:8025/, type something in search, hit enter, results are shown. On clicking, this appears in the js console
obviously ids and content change, but the same happens clicking on any message in the search results. |
This is still an issue as far as I can see. With a very brief glance at the markup, it looks like the ng-if="searching" condition needs to pay attention to the preview flag also |
This is still an issue for us. We are running MailHog v1.0.0 with mongodb as the storage backend. We have thousands of messages. If I make a search, I might get back dozens or hundreds of messages. It doesn't seem to matter whether all the search results fit on one page or multiple pages. I looked into the response from the API call to the search function. The Content body is empty. Here is a snippet from the Chrome console:
|
We are having this issue in our mailhog instance. Whenever we search and try to open an email from the search result we can't see the body of the email. |
Same here |
The text was updated successfully, but these errors were encountered: