Skip to content
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

Add show_date_span parameter to channel calendar #174

Draft
wants to merge 6 commits into
base: release/5.3.0
Choose a base branch
from

Conversation

imacrayon
Copy link

@imacrayon imacrayon commented Apr 12, 2019

Overview

Added a show_date_span="yes" parameter to the {exp:channel:calendar} tag which repeats the entry across every calendar "day" cell between the entry’s publish and expiration date.

Given a single entry (My Event) with an entry_date of April 1, 2019 and an expiration_date of April 5, 2019 - setting show_date_span="yes" would display a calendar with the first week like this:

S M T W T F S
31
 
1
My Event
2
My Event
3
My Event
4
My Event
5
My Event
6
 

Entires without an expiration_date will continue to show on a single day.

When combined with show_future_entries="yes", this would be useful for anyone wanting to build a simple event calendar.

Nature of This Change

  • 🐛 Fixes a bug
  • 🚀 Implements a new feature
  • 🛁 Refactors existing code
  • 💅 Fixes coding style
  • ✅ Adds tests
  • 👽 Adds new dependency
  • 🔥 Removes unused files / code
  • 🔒 Improves security

Is this backwards compatible?

  • Yes
  • No

Documentation

ExpressionEngine/ExpressionEngine-User-Guide#41

`show_date_span` displays an entry in every calendar cell between the entry’s publish and expiration date.
@derekjones derekjones changed the base branch from stability to release/5.3.0 August 8, 2019 20:14
@derekjones derekjones added the enhancement New feature or request label Aug 8, 2019
@intoeetive intoeetive added the EE5 label Jan 6, 2021
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@intoeetive
Copy link
Contributor

@imacrayon thank you for this contribution!

Since EE5 is only receiving security updates at this point, would you be willing to update this PR for EE6, make it to be against 6.dev and also sign our updated contributor license agreement?

intoeetive pushed a commit that referenced this pull request Oct 27, 2021
Cleanup/merge 5 into 6 (EECORE-257)
@intoeetive intoeetive marked this pull request as draft December 2, 2021 14:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
EE5 enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants