#wp_date search results
we have `wp_timezone()` in core!!! core.trac.wordpress.org/changeset/45853 I don’t call much in WP a game changer, this is a game changer for Date/Time component! 🎉😊 #wp_date
Date/Time component improvements in WordPress 5.3 make.wordpress.org/core/2019/09/2… #wp_date ⌛
all of the planned #wp_date ⏳ API merged for WP 5.3! github.com/Rarst/wp-date/… 🎉
this was ported from a reliable 100% unit tested library I am very confident in excuse me I just found another bug be right back #timezones #wp_date ⏳
after more than a year of work finally submitted the patch for titular `wp_date()` function (real timestamps! any time zone!), reducing `date_i18n()` to a legacy wrapper core.trac.wordpress.org/attachment/tic… #wp_date ⏳
submitted the wp_timezone() patch for unified time zone retrieval, a few lines of code, a giant leap for Date/Time in WP core core.trac.wordpress.org/attachment/tic… #wp_date ⏳
いつも忘れるからメモ #WordPress #wp_date WordPressでは日時関係はwp_date()を使う blog.tanoshikudays.net/wordpress_wpda…
“Typical date/time inputs accepted by a WordPress function are ISO8601, date without time, time without timezone, and rotten fish.” this is how I summarize #wp_date ⏳ to PHP devs.
development with outsized anxiety response: “DID WE SHIP INHERENTLY CRIPPLED YEAR OF WORK AND NEED TO ROLLBACK IN RELEASE CANDIDATE OF A MAJOR VERSION never mind, a trivial regression with an easy fix.” #wp_date ⌛
and that’s a wrap with #wp_date ⌛✔ for me! I am staying on as Date/Time component maintainer and will poke lingering issues at leisure. ping if you want to pay me a lot of money to fix Rewrite in core. 🤙 #wp_route 🏁
I unarchived and renamed my #wp_date fork of wordpress-develop back to that, to use it for core dev, which worked out kinda clunky, but it is what it is, soz if anyone confused by notifications or anything :)
this starts to sniff for Date/Time stuff! hopefully will build up more of it over time and then eye formal deprecations in core in future. #wp_date ⌛
WordPressCS 2.2.0 is out! This release is ready for #WP 5.3, brings you five brand new sniffs, documentation on the command-line for 20 sniffs and lots of other improvements and bug fixes. #WPCS #WordPress Run `composer update` now or download at: github.com/WordPress/Word…
look at your code now look at patch core.trac.wordpress.org/changeset/45887 now at your code now back at mine sadly your code isn't like mine but if you stopped using PHP 5.2 it could smell like mine look down, back up you are on trac there are years old tickets fixed I’m on a horse #wp_date ⏳
👏👏👏 #WordPress #wp_date a team of🦸♂️ heroes solved it!
all of the planned #wp_date ⏳ API merged for WP 5.3! github.com/Rarst/wp-date/… 🎉
`current_datetime()` is a small new helper function in WP 5.3 for much more reliable and flexible to manipulate representation of current point in time as `DateTimeImmutable` object core.trac.wordpress.org/changeset/45883 #wp_date ⏳
HOURS/MINUTES OFFSET AS VALID INPUT FOR TIME ZONE CONSTRUCTOR #nextlevel #wp_date ⏳
yeah, I need a hard specific line where I can start targeting 5.6 because I need it in #wp_date ⏳ so should's are not that :)
`date_i18n()` gets a ground up rewrite in WP 5.3 (way better than _I_ could have managed) which solves untold number of bugs. I plan to move implementation to a new `wp_date()` function later and ~deprecate `date_i18n()` as legacy wrapper core.trac.wordpress.org/changeset/45882 #wp_date ⏳
いつも忘れるからメモ #WordPress #wp_date WordPressでは日時関係はwp_date()を使う blog.tanoshikudays.net/wordpress_wpda…
I unarchived and renamed my #wp_date fork of wordpress-develop back to that, to use it for core dev, which worked out kinda clunky, but it is what it is, soz if anyone confused by notifications or anything :)
this starts to sniff for Date/Time stuff! hopefully will build up more of it over time and then eye formal deprecations in core in future. #wp_date ⌛
WordPressCS 2.2.0 is out! This release is ready for #WP 5.3, brings you five brand new sniffs, documentation on the command-line for 20 sniffs and lots of other improvements and bug fixes. #WPCS #WordPress Run `composer update` now or download at: github.com/WordPress/Word…
development with outsized anxiety response: “DID WE SHIP INHERENTLY CRIPPLED YEAR OF WORK AND NEED TO ROLLBACK IN RELEASE CANDIDATE OF A MAJOR VERSION never mind, a trivial regression with an easy fix.” #wp_date ⌛
and that’s a wrap with #wp_date ⌛✔ for me! I am staying on as Date/Time component maintainer and will poke lingering issues at leisure. ping if you want to pay me a lot of money to fix Rewrite in core. 🤙 #wp_route 🏁
Date/Time component improvements in WordPress 5.3 make.wordpress.org/core/2019/09/2… #wp_date ⌛
👏👏👏 #WordPress #wp_date a team of🦸♂️ heroes solved it!
all of the planned #wp_date ⏳ API merged for WP 5.3! github.com/Rarst/wp-date/… 🎉
all of the planned #wp_date ⏳ API merged for WP 5.3! github.com/Rarst/wp-date/… 🎉
after more than a year of work finally submitted the patch for titular `wp_date()` function (real timestamps! any time zone!), reducing `date_i18n()` to a legacy wrapper core.trac.wordpress.org/attachment/tic… #wp_date ⏳
look at your code now look at patch core.trac.wordpress.org/changeset/45887 now at your code now back at mine sadly your code isn't like mine but if you stopped using PHP 5.2 it could smell like mine look down, back up you are on trac there are years old tickets fixed I’m on a horse #wp_date ⏳
`date_i18n()` gets a ground up rewrite in WP 5.3 (way better than _I_ could have managed) which solves untold number of bugs. I plan to move implementation to a new `wp_date()` function later and ~deprecate `date_i18n()` as legacy wrapper core.trac.wordpress.org/changeset/45882 #wp_date ⏳
`current_datetime()` is a small new helper function in WP 5.3 for much more reliable and flexible to manipulate representation of current point in time as `DateTimeImmutable` object core.trac.wordpress.org/changeset/45883 #wp_date ⏳
we have `wp_timezone()` in core!!! core.trac.wordpress.org/changeset/45853 I don’t call much in WP a game changer, this is a game changer for Date/Time component! 🎉😊 #wp_date
behold! date_i18n() that is not a total nightmare and works more often than not! with the power of not *as* obsolete PHP and major props to @remcotolsma for the refactoring! core.trac.wordpress.org/attachment/tic… #wp_date ⏳
“Typical date/time inputs accepted by a WordPress function are ISO8601, date without time, time without timezone, and rotten fish.” this is how I summarize #wp_date ⏳ to PHP devs.
submitted the wp_timezone() patch for unified time zone retrieval, a few lines of code, a giant leap for Date/Time in WP core core.trac.wordpress.org/attachment/tic… #wp_date ⏳
this was ported from a reliable 100% unit tested library I am very confident in excuse me I just found another bug be right back #timezones #wp_date ⏳
dropping idea of going canonical UTC from #wp_date ⏳ for now, since it's not an adequate solution for scheduling needs github.com/Rarst/wp-date/…
finished #wp_date ⏳ API audit. you would think that unexciting saturday activity... but look at this resulting graph! isn’t it pretty!? (I need a life.) github.com/Rarst/wp-date/…
Something went wrong.
Something went wrong.
United States Trends
- 1. Eagles 151K posts
- 2. Lions 75.9K posts
- 3. Goff 16.7K posts
- 4. Dan Campbell 9,113 posts
- 5. Jalen 30.2K posts
- 6. Gibbs 7,303 posts
- 7. Chiefs 89.2K posts
- 8. #OnePride 5,063 posts
- 9. AJ Brown 7,562 posts
- 10. Nakobe Dean 1,546 posts
- 11. Broncos 65.2K posts
- 12. Patullo 10.6K posts
- 13. Adoree Jackson 2,157 posts
- 14. Collinsworth 2,326 posts
- 15. Vic Fangio 2,743 posts
- 16. #DETvsPHI 3,246 posts
- 17. Jamo 4,243 posts
- 18. Shedeur 52.1K posts
- 19. Sirianni 3,234 posts
- 20. NFC North 4,559 posts