Filter by types

tired that though Im getting an error as follow

user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND t.type IN ("image", "weblink", "blurb") n.status = 1' at line 1 query: SELECT MIN(n.created) AS min_date, MAX(n.created) AS max_date FROM node n JOIN node_type t ON t.type = n.type WHERE AND t.type IN ("image", "weblink", "blurb") n.status = 1 in C:\SERVER\xampp\htdocs\*********\database.mysql.inc on line 172.

though i am using a custom node type ie blurb

any ideas

Looks more like an SQL calling error as I removed the custom type and still getting a similar syntax error

- This code includes generated pieces like t('Describes what the settings generally do.') as a description...
- The archive_page_path setting seems to be insane to me. Why duplicate path alias functionality?
- The patch does not conform to Drupal coding styles... Lines like the following violate code style rules in every possible place
}else if($date->days[$date->day] > 0){ // Otherwise redirect the user to the same day viewing all node types
- Other parts of the code, like archive_node_types() and _archive_validate_type() even use tabs.
- You also have a lot of date related changes included in the patch, which are not related to type handling.

By the way issue #75543 (http://drupal.org/node/75543) is an interesting prior art.

A big +1 to these patches. I've add them to the site and it is very nice to be able to eliminate the 'admin' content-types from the archives (frankly the module is a bit useless for some sites without this feature).

A small nit - somewhere it needs to be documented that the path to the configuration page is /admin/settings/archive

Setting to rtbc to encourage things along...

Nevermind about the forementioned nit - I see that the link to the archive settings does indeed appear on admin/settings.

What's the status on it? Is it in fact ready to be committed (and has been for a month)? Has it been committed (so this should be set to fixed)? Or does it still need work (and should be set accordingly)? Just wondering because a RTBC patch has been untouched for more than a month...

Unfortunately the Archive module maintainer (namely myself) is very busy with final Drupal 6 core feature patches (being one of the Drupal 6 committers too). I tried to find people to take over (among other modules) the Archive module from me, so it can be properly maintained. Until this happens, unfortunately there is a big lag in responses to Archive module issues.

susurrus, you don't seem like having a CVS account at all, so you effectively cannot get maintainership of this module just yet.

Would love to use this module with this patch. However I do not have shell access to run this on my server. Can someone send me the updated compiled files for this module?

Thanks, I really appreciate you taking on this module. This module will allow a lot of power to allow users to easily archive nodes by date and in the next few days by date and/or node type. I also just posted a new request that hopefully we can work on, filtering by taxonomy term (and/or). Thanks again...