/me installs

Thanks for the thanks, installs, ratings, and nominations. :D

@TTG: The mod automatically deletes from its table any entry over thirty days old.

@joeychgo: The 'getnew' and 'getdaily' searches should not be recorded. When members search, they can search on Key Word(s) and/or User Name. If one of those fields is blank, then dashes appear. That might be what you are seeing. Also, the Member column is who searched; the Query column contains what was searched. The other columns are there for additional information about the search.

This is nice, and may be used to show queries from last 30 days in clouds for forums that use fulltext search

Nice.

Not if I'll use this yet, but it's a great idea so I've nominated anyway. :)

See attachment for what im talking about. It shows as 'guest' but a username is coming up under 'query'. But, if the search is not by a guest, then no username under 'query'.

thx for this hack pretty good one ^^ will help me see how cleaver my users are using the search function xD

Thanks again for the thanks, installs, ratings, and nominations. :)

@joeychgo: The Member column is who searched, and the Query column contains what was searched, i.e., the first row of your screenshot shows that Guest searched for Danny Boy, and the last two rows of your screenshot show that wenchupover searched for him/herself and then did another search for google analytics. Note that Guest could be a person or bot, and that when doing a search, it's possible to query on Key Word(s), User Name, or both.

Is it possible to restrict to only admins and/or mods?

In the recent_queries.php file find:
And afterwards add the following:
Where 5, 6, 7 represents these groups:

Thanks for this, very useful!

When I imported the product, it didn't create the table 'rq_recent_queries'. I don't know why.. when I ran the SQL from the .xml file manually I got an error from MySQL. Maybe it's an old version (4.0.25)?

Well, I created the table manually and just copied the structure from the search-table over as that's what I assumed the SQL should have done.. then reimported the product and now it works! :)