Answers.Body: <p>You can also get it with:</p>
  
  <pre><code>{% set nextYear = now.year + 1 %}
  </code></pre>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-13T20:20:37.530Z
Answers.Text: It is really simplier! (best) But I won't unaccept first answer in order not to be rude.
Answers.UserDisplayName: nicael
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-13T20:26:05.087Z
Answers.Text: No arguments there! Christian’s is a good answer too – certainly more flexible, and something that could be done with “pure Twig” (the `.year` property is only actually available in Craft’s extended DateTime class).
Answers.UserDisplayName: Brandon Kelly
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-13T20:31:23.913Z
Answers.Text: Thanks for clarification! For the future: If I am not an autor of a post, I don't get notified if you comment, so you should add @nicael.
Answers.UserDisplayName: nicael
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-13T20:32:43.067Z
Answers.Text: @nicael Nice, I didn’t know SE had @ mention support.
Answers.UserDisplayName: Brandon Kelly
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-13T20:33:52.267Z
Answers.Text: Now I got notified. All right! =)
Answers.UserDisplayName: nicael
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-13T20:47:09.683Z
Answers.Text: Which makes the better answer if the question itself doesn't imply a preference for succinctness vs. flexibility?
Answers.UserDisplayName: Matt Stein
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-13T20:47:38.303Z
Answers.Text: I read somewhere that you can only notify users in the same "comments thread". Too bad, a @Brandon could come handy in deserted questions! :)
Answers.UserDisplayName: carlcs
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-13T20:50:34.250Z
Answers.Text: @ChristianSeelbach that's what bounties are for ;)
Answers.UserDisplayName: Brandon Kelly
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-13T20:16:23.950Z
Answers.LastActivityDate: 2014-06-13T20:16:23.950Z
Answers.UserDisplayName: Brandon Kelly
Answers.Body: <pre><code>{% set nextYear = now|date_modify('+1 year')|date('Y') %}
  </code></pre>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-13T19:57:58.720Z
Answers.Text: You're too fast, Christian.
Answers.UserDisplayName: Matt Stein
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-13T20:28:09.757Z
Answers.Text: Brandon's answer is great if you're only adjusting the year (as the original question asks). But if any adjustments need to be made to the month or day, this answer would work better.
Answers.UserDisplayName: Lindsey D
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-13T19:57:02.177Z
Answers.LastActivityDate: 2014-06-13T19:57:02.177Z
Answers.UserDisplayName: carlcs
Body: <p>I can get the current year in this way:</p>
  
  <pre><code>{% set currentYear = now.year %}
  </code></pre>
  
  <p>How do I get the next year?</p>
  
Tags: <templating><datetime>
Title: How do I get the next year?
ThreadText: # How do I get the next year?
  
  (Asked by: username_0 on 2014-06-13)
  
  I can get the current year in this way:
  
  ```
  {% set currentYear = now.year %}
  
  ```
  
  How do I get the next year?
  
  **Tags:** templating, datetime
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_3 on 2014-06-13. Score: 10 | Accepted answer
  
  ```
  {% set nextYear = now|date_modify('+1 year')|date('Y') %}
  
  ```
  
  > **Comments:**
  > **username_2**: You're too fast, Christian.  
  > **username_4**: username_1's answer is great if you're only adjusting the year (as the original question asks). But if any adjustments need to be made to the month or day, this answer would work better.  
  
  ---
  
  ### Answer by username_1 on 2014-06-13. Score: 11
  
  You can also get it with:
  
  ```
  {% set nextYear = now.year + 1 %}
  
  ```
  
  > **Comments:**
  > **username_0**: It is really simplier! (best) But I won't unaccept first answer in order not to be rude.  
  > **username_1**: No arguments there! Christian’s is a good answer too – certainly more flexible, and something that could be done with “pure Twig” (the `.year` property is only actually available in Craft’s extended DateTime class).  
  > **username_0**: Thanks for clarification! For the future: If I am not an autor of a post, I don't get notified if you comment, so you should add @username_0.  
  > **username_1**: @username_0 Nice, I didn’t know SE had @ mention support.  
  > **username_0**: Now I got notified. All right! =)  
  > **username_2**: Which makes the better answer if the question itself doesn't imply a preference for succinctness vs. flexibility?  
  > **username_3**: I read somewhere that you can only notify users in the same "comments thread". Too bad, a @username_1 could come handy in deserted questions! :)  
  > **username_1**: @ChristianSeelbach that's what bounties are for ;)  
  
  ---
  
  