[ Originally suggested by geerlingguy on July 15 - http://drupal.org/node/478850#comment-1814144 and raised as feature request by moi.]

One feature I'd like to see is possible integration with the date API, so people could, depending on whether they have permission to set their own ad expiration times, click in a text field and select a date for ad expiration.

I support this suggestion, done properly it will be a good feature for the module.

Cheers,

Miles

Comments

milesgillham’s picture

milesgillham commented

Date API: Date Module

jack_ruby’s picture

jack_ruby commented

Miles,
Is it possible (in current or future releases) to have user selected expiration occur based on type of ad, or taxonomy?

I have 3 types of ad: for sale, wanted, and yard sale. I want user to select the expiration of yard sales, but not the others.
Can I do that with the current alpha release?

milesgillham’s picture

milesgillham commented

Are you saying that you want a user to be forced to use the default ad expiration for wanted and for sale, but for yard sale they can set whatever expiration they like?

If so, I can add this functionality by putting in a minimimum and maximum (instead of just a single default). That way, for yard sale you could set a minimum of 1 day and a maximum of say 365 days. The other piece to add is in the ad creation form to allow a user to enter the expiration period if the system minimum and maximum aren't the same. If the Date module was present it would be possible to autodetect it and also offer an end date (so if you wanted an ad to expire on the 24 September from today it would save you having to do the math, but other times you might just want to set a number of days).

I think if I implemented the above then it would address what you want and the original request also.

Is that what you're after?

Cheers,

Miles

jack_ruby’s picture

jack_ruby commented

Are you saying that you want a user to be forced to use the default ad expiration for wanted and for sale, but for yard sale they can set whatever expiration they like?

I believe that's exactly what I want.

For the sake of flexibility, it would be nice to choose the option of having the default date or choose expiration based on taxonomy or by user status.
For instance a 'paid' user gets two weeks but a 'authenticated' user gets one.

But that's just brainstorming.

For my purposes taxonomy-based expiration is what I need.

Thanks.
You are kicking ass and taking names on this module!

JR

muirgein’s picture

muirgein commented

Ditto for me. User-selectable expiration - within admin-set limits - would be spiff.

Also ditto on the kudos! I appreciate the work you've done!

-M

milesgillham’s picture

milesgillham commented

Apologies, have been distracted with other projects. This is going to be a good feature inclusion for alpha7 which is now due by Fri 4 Sep 2009 (this coming week). See the ed_classified project page for the other intended inclusions.

Cheers,

Miles

milesgillham’s picture

milesgillham commented

Note to self, evaluate #531738: Admin never expire override at the same time.

St4t0’s picture

St4t0 commented
Version: 6.x-2.x-dev » 6.x-3.x-dev

Bumping version.

fgm’s picture

fgm
Primary language French
Location Paris, France
commented
Issue summary: View changes
Status: Active » Closed (won't fix)

Since Drupal 6 was EOL-ed in 02/2016, no additional fixes will be added ; so closing.