The string doesn't match the expected date/time/date-time format. The string to parse was: "lun, 17 ago 2020 00:00:00 +0000". The expected format was: "EEE, dd MMM yyyy HH:mm:ss Z".
The nested reason given follows:
Unparseable date: "lun, 17 ago 2020 00:00:00 +0000"

----
FTL stack trace ("~" means nesting-related):
	- Failed at: #assign parsedPublishDate = rawPublis...  [in template "48478917202330#20121#713300" at line 4, column 1]
----

1<#assign rawPublishDate = .vars["reserved-article-display-date"].data> 

2<#assign currentLang = locale.getLanguage()> 

3<#setting locale=currentLang> 

4<#assign parsedPublishDate = rawPublishDate?datetime("EEE, dd MMM yyyy HH:mm:ss Z")> 

5<#setting time_zone="Europe/Madrid"> 

6${parsedPublishDate?string("yyyy-MM-dd'T'HH:mm:ssZZ")} 

The string doesn't match the expected date/time/date-time format. The string to parse was: "jue, 30 oct 2025 01:55:36 +0000". The expected format was: "EEE, dd MMM yyyy HH:mm:ss Z".
The nested reason given follows:
Unparseable date: "jue, 30 oct 2025 01:55:36 +0000"

----
FTL stack trace ("~" means nesting-related):
	- Failed at: #assign parsedDate = rawDate?datetime...  [in template "48478917202330#20121#713304" at line 4, column 1]
----

1<#assign rawDate = .vars["reserved-article-modified-date"].data> 

2<#assign currentLang = locale.getLanguage()> 

3<#setting locale=currentLang> 

4<#assign parsedDate = rawDate?datetime("EEE, dd MMM yyyy HH:mm:ss Z")> 

5<#setting time_zone="Europe/Madrid"> 

6${parsedDate?string("yyyy-MM-dd'T'HH:mm:ssZZ")}