Title: JayEn84's Replies | WordPress.org

---

# JayEn84

  [  ](https://wordpress.org/support/users/jayen84/)

 *   [Profile](https://wordpress.org/support/users/jayen84/)
 *   [Topics Started](https://wordpress.org/support/users/jayen84/topics/)
 *   [Replies Created](https://wordpress.org/support/users/jayen84/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/jayen84/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/jayen84/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/jayen84/engagements/)
 *   [Favorites](https://wordpress.org/support/users/jayen84/favorites/)

 Search replies:

## Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)

 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [[WP Calendar] 'before' and 'after' tag](https://wordpress.org/support/topic/before-and-after-tag/)
 *  [JayEn84](https://wordpress.org/support/users/jayen84/)
 * (@jayen84)
 * [13 years, 3 months ago](https://wordpress.org/support/topic/before-and-after-tag/#post-3385159)
 * To me, it appears that the “before” and “after” short tags are only working on{
   event_endtime}, if the setting “Show end date” is set to “Always show end date”
   and not set to “Only show end date, if different from start date”. faebu, can
   you confirm?
 * In my template, I use {event_enddate; before=” bis “}. For events with different
   start and end date, the additional “bis” does only show up with the setting “
   Always show end date”.
 * Kind regards
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WP Calendar] Disabling pagination in widget](https://wordpress.org/support/topic/disabling-pagination-in-widget/)
 *  Thread Starter [JayEn84](https://wordpress.org/support/users/jayen84/)
 * (@jayen84)
 * [13 years, 3 months ago](https://wordpress.org/support/topic/disabling-pagination-in-widget/#post-3295460)
 * I have just seen that a new version containing the fix was already released. 
   Thank you very much for your support!

Viewing 2 replies - 1 through 2 (of 2 total)