-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Event Managment/Close dates for posts #8
Comments
Hello - The basic |
I have noticed a call to a close function in the code, but I have never really found out how to set it in the entry. |
You are right, actually. We don't have a great way to retrieve posts by less than or greater than comparisons. For == comparisons, you can add the field name and value right into the We will add a close date for posts in the future that will automatically close them. |
I have a fix for this in my fork. I made all content types with standard fields include an unpublish date. The db holds that date and the status of the content type. Once the unpublish date is encountered, the item is then Disabled. You can still see it in the admin section but the users on the front end will no longer see it. I used a cron hook for that part. Items the have a pub date after the current date will also be Disabled initially, and then enabled once the publish date/time occurs. |
This has been worked on in the forms but we need a better solution. I need event management where I can post pages of events on future dates (which is accessible to the public), and the events will automatically remove themselves from the listings after the event date has passed. This can also be managed via a "close date" function for posts. Some of my clients run a ton of events and they have not been able to manually close everything out, which is the only working solution as of now, so this would be an awesome feature for Hero :D Thanks
The text was updated successfully, but these errors were encountered: