updateTimestamp: false not working
See original GitHub issueStill the date is updated without other changes, I’m using the latest version 1.0.2
makepot: {
theme: {
options: {
cwd: '',
mainFile: 'style.css',
domainPath: 'languages/',
exclude: ['node_modules/.*'],
potFilename: '<%= x %>.pot',
potHeaders: { 'report-msgid-bugs-to': 'http://theme-homepage' },
type: 'wp-theme',
updateTimestamp: false,
}
}
};
By the way, do I need to add also ‘.svn’ to exclude ?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Spring Boot JPA @UpdateTimestamp not working with ...
UUIDGenerator" ) @Column(updatable = false, nullable = false) ... annotation to work, the call must not be self-invoking (ie. must be called ...
Read more >Panache @CreationTimestamp and @UpdateTimestamp not ...
Describe the bug Entity having colums annotated with @CreationTimestamp and @UpdateTimestamp are not automatically updated on entity persist ...
Read more >UpdateTimestamp not working with @Inheritance( strategy ...
when a field in the Customer type is updated (via a setter), there is no update of the "modifiedAt" time, and it will...
Read more >Do NOT populate @UpdateTimestamp field when entity gets ...
Is there a way to configure an @UpdateTimestamp field so it won't get populated when the entity gets created but only when the...
Read more >How to persist creation and update timestamps with Hibernate
The creation and update timestamp will therefore not be the same even if the entity was never updated. 1. 2. MyEntity e =...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I believe this should be good to go in 1.0.3. Feel free to reopen with more details if it still doesn’t work.
@av3nger Ah, thanks for sticking with me on that. I think I figured out what was going on and hopefully this commit should take care of it.