- π«π·France fgm Paris, France
With this module end of life approaching along with Drupal 7 EOL, this issue is now moot.
Users are finding this confusing.
When creating new ads they see "Define expiration date automatically, based on the ad category." with one radio button. And when editing an ad they see the same line of text as an option. Their immediate assumption is that there is something missing in the node/add form with only one radio button. Plus the statement seems to imply that action is required. If no action is taken below then at the very least this should probably be reworded. Something like "Expiration date set automatically based on the ad category." But, definitely hide the radio button.
I think it would be more ideal to display "Reset expiration" as the text on the edit nodes instead of "Define expiration date automatically, based on the ad category." And on the create node display something like "This ad will be set to expire automatically based on the ad category." preferably with a "hidden" radio button, and maybe scratch the fieldset, too.
Lastly, on the edit node under "This ad is currently due to expire on 19/01/2014." add additional context that explains to the user what each option will do. For example:
--------------------------------------------------------
This ad is currently due to expire on 19/01/2014.
If you select "Keep current expiration date" your ad will expire and will be kept, unpublished, for 7 days. If you republish the ad after it has expired, and before the 7 day grace period, your ad will appear again at the top of the results page.
If you select "Reset expiration" your ad's expiration will be reset, however it will remain in its current position in the results page.
-----------------------------------------------------------
Thanks again for this module and all the work you put into it!
Closed: won't fix
3.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
With this module end of life approaching along with Drupal 7 EOL, this issue is now moot.