Seems like there's some data access problem. The only history visible are the times I viewed pdfs in browser. I disabled the extension, and regular history works fine, so it's definitely an issue with the way extended history interfaces with chrome.

Is it possible to support such grammar:

helloworld site:github.com

search history items, with github.com domain, and helloworld keyword

I'm done it for a firefox extension:
Christoph-Wagner/firefox-better-history-ng#4

Enhancement propose:
Export history links - useful for links from devices.

Workaround for now is simple jQuery expression to generate each link in new line:

$('div.content ol.visits').first().find('li.visit a.item.site dd.location').map((i, e) => e.innerText).toArray().join('\n')

and then copy&paste from console to text file.

Uncaught ReferenceError: google is not defined
at child.render (VM97 app.js:5050)
at Cache.statisticView (VM97 app.js:3724)
at Cache.view (VM97 app.js:3669)
at child.statistic (VM97 app.js:5741)
at child.execute (VM97 app.js:2116)
at Object.callback (VM97 app.js:2104)
at VM97 app.js:2387
at Function.h.some.h.any (VM97 app.js:596)
at Backbone.History.loadUrl (VM97 app.js:2385)
at Backbone.History.start (VM97 app.js:2327)

I've summarized a few suggestions and issues identified relating to searching history with Enhanced History extension for Chrome below:

Summarized Issues & Requests:

1. Use "h" keyword (instead of "history") and/or allow this to be easily customized from within extension settings, as it's impossible to change this under
2. Make possible for users to create their own search engine keyword (like "h") and even bookmark common search pages by:
   • Having the search keyword shown in URL in address bar, changing based on what the user enters into the Search box (like is the case for standard History page, so that users know what URL to use).
3. Make it clear that this extension registers a new search engine with the "history" keyword, stating this in Extension (Store) description page and Search Tips.
   • Needed as this capability is unknown for many, and that can prevent others spending much time trying to identify the URL (despite issues preventing that, detailed further below) to add it themselves (eg for "h" keyword)
4. Support the same non-enhanced history URL pattern of chrome://history/all?q=%22%s%22 so
   • Needed so existing search engine entries (eg. if adding for default History page earlier) will still work as expected, vs. just breaking that as is currently the case.
5. Have the search query (even if entered via address bar) auto populated into the Search box in the resulting page.
6. Middle click to open links for Enhanced History search result pages opens a broken search page searching for "p2" for 2nd page of results, for example.
7. Add support for title: and url: search keywords to limit searching to title or url only (and show these in Search Tips)
8. Consistently show either endless results (with "Search deeper" button) or Paged results, instead of randomly showing Paged vs. Endless in different cases as occurs now (possibly sometimes shows pages if click on Search side tab and/or in other cases? Unsure as even then very inconsistent)
9. Often "Search deeper" does not show up
   • Such as even when I search for the same thing a 2nd time (after searching for something different in between) without closing and reopening the history page (like seen in screenshot further below)
10. Regex search results in HTML markup showing in title at top of page like:
    Searching <ul class="tags"><li>{What you searched for}<li><ul>
11. If you middle-click a page number (with paged results) to open in a new tab like for the following for Page 2 when searching for Google, which results in an invalid page (searches for "Google/p2" instead of just "Google")
    • chrome-extension://blpnkmdkoapbdhpmemnaikpbhajknmdb/index.html#search/Google/p2
    • Combined with lack of search term shown in URL (like native Search) this makes it nearly impossible for users to figure out what the URL should be to add their own search engine keyword

Workaround for just 1 Issue (adding "h" search engine keyword)

I did discover a temporary workaround that users can use to add Enhanced History search as a Search Engine in Chromium-based browsers using the following search engine URL pattern:

chrome-extension://blpnkmdkoapbdhpmemnaikpbhajknmdb/index.html#search/%s

Though without looking at search code or much trial and error others likely won't be able to identify this, due to issues with lack of showing URL or even invalid page URLs as detailed above.

Note that even for Chromium-based Edge (Developer channel) you must still use chrome-extension:// even though the browser shows it as extension://, otherwise redirection errors occur resulting in extension://extension:// or similar invalid URLs.

You can add this for "h" keyword (for Chrome or Edge Chrome) at:

chrome://settings/searchEngines
edge://settings/searchEngines

Auto registered search engines like Enhanced History cannot have there search keyword edited, making this even more important that it's possible to easily figure out what this URL is and/or allow editing the keyword via extension settings.

However, there is no way for users to determine that other than looking through the code or many random guessing attempts, since, unlike basic history and many search engines the URL shown in address bar doesn't change after performing a search.

Also, even that fails to show what was searched via keyword in the "Search title or url" box for easy tweaking or clarity.

Screenshots of Issues

Sometimes shows Search deeper / endless loading history search results:

Paged results being shown instead

Middle click on result page number opens invalid search page:

URL for Search in Standard History:

Search Deeper shown after first search

Search deeper fails to show after I search a 2nd time after (for something different, then same search again) once history page is already open

Regex results in HTML markup showing in title at top of page like:
Searching

• {What you searched for}
• 
  

The page is blank:

app.js:3534 Uncaught SyntaxError: Unexpected identifier

Edit: column 467: unescaped '

v2 will be deprecated in 2023

Just opening a new issue as this was back on the store from #12 but now removed again

Was trying to install the extension but met error below. So I renamed the _config.yml file and was able to successfully install the extension afterwards. Is this the recommended approach? If yes, I can submit a PR to master to rename the _config.yml file to config.yml file so future non-tech savvy users can avoid this issue. Kindly advise, thanks!!

Error

Cannot load extension with file or directory name _config.yml. Filenames starting with "_" are reserved for use by the system.
Could not load manifest.

Note: the Chrome Version used on the computer was: Version 84.0.4147.89 (Official Build) (64-bit)

Workaround

Renamed _config.yml file to config.yml and the extension installed successfully on Chrome.

I have an extension that log extensions events (enable/disable/updated/...). It warned me that it has noticed that chrome automatically disabled "Enhanced History" today 10/10/2018 at 15:28 GMT+2
Chrome still allows me to re-enable "EH".

Chrome says "This extension violates the Chrome Web Store policy."

Edit 23-11-2018: has not been disabled since then (5 days ago)
Edit end

Just a heads-up.
I don't know what is going on. A chrome bug perhaps, but it has disabled EH for the same reason as previously. But this time the extension is still visible on the web store.

This summer I have developped an extension that monitors all the extension installed in my profiles (I was fed up not knowing when extensions or chrome are updated. Plus, I needed a working solution to keep track of uninstalled extensions). It warned me immediately when it noticed the disabling:

My timezone is GMT+1

I regularly test one of my own extensions, and one of it capabilities is to bulk-download crx packages of extensions that I have currently installed.
"Enhanced History" isn't available anymore (2020/06/04).
The last time I made the test, May 27 2020, it was downloaded.

Chromium users can sideload .crx directly without "Load Unpacked Extensions":
https://ungoogled-software.github.io/ungoogled-chromium-wiki/faq#can-i-install-extensions-or-themes-from-the-chrome-webstore
https://chromium.woolyss.com/#external-extension-installation

Following these instructions will allow auto-updating using the Chromium Web Store extension

This is a workaround around the Chrome Web Store extension removal problem.