-
Notifications
You must be signed in to change notification settings - Fork 88
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
"modified" and "creationDate" config properties not working #642
Comments
Hello, |
Well, having specified
I would expect the output to look as follows: Release: 13 Nov, 2022 |
And what is it that you are getting now? I am confused, sorry |
Ohhh I see now.
El vie., 20 oct. 2023 2:14 p. m., Piotr Gorczyca ***@***.***>
escribió:
… I am getting:
Release: Creation date
Modified on: Modified date
(screenshot below)
[image: Screenshot from 2023-10-20 14-13-34]
<https://user-images.githubusercontent.com/43420734/276926612-de29d52e-f6ee-470d-b301-3a39097476ed.png>
—
Reply to this email directly, view it on GitHub
<#642 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALTIGRHFRO3YDI5EAPCYYTYAJTKFAVCNFSM6AAAAAA6I4D5C2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZSGYZTAOJQGM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Hi, I just wanted to mention that I am also having the same problem with the latest version of Widoco: widoco-1.4.20-jar-with-dependencies_JDK-17.jar. I managed to find a workaround by using the following keys:
It seems to be a problem in the documentation. |
Now fixed in doc (a similar thing happened with |
In my
config.properties
file I have bothcreationDate
andmodified
precisely as in described in the guide. However, when generated I get:Release: Creation date
Modified on: Modified date
The text was updated successfully, but these errors were encountered: