ycdevs
Forum Replies Created
-
We have restructured the forms to make them accessible for people with disabilities:
- we added a different structure in the modal (the label element contains an input element and a description)
- we managed toggle buttons using the input element -> we blocked the ability to navigate through the site using the tab key until cookies are accepted
- we introduced “aria” elements
- we added focus upon transitioning to the cookie selection options (Statistics, Experience, Marketing)
- and many more… (i don’t remember all changes) ??
I think you should thoroughly review the changes implemented in the code via file comparison; it will give you a broader overview ??
You can see the plugin with the applied WCAG improvements on the website: https://galeriakatowicka.eu/
Forum: Plugins
In reply to: [Read Meter - Reading Time & Progress Bar] Special ID attribute in shortcodeGive a feedback, if you add this to plugin ??
Forum: Plugins
In reply to: [Cookies and Content Security Policy] Consent Mode v2 – Implementation IssuesSUPER! Thank you ??
Forum: Plugins
In reply to: [Cookies and Content Security Policy] Consent Mode v2 – Implementation Issues@jonkastonka – When can we expect the next release of the plugin?
After 3 weeks of testing the hotfix plugin, unfortunately, the problem still persists. For over 2 weeks, the issue did not occur. However, for the past few days, we have noticed that the numbers in the year field are still setting themselves randomly.
There is a workaround for the issue using the following scenario:
- Publish a post with the previously disabled plugin in the “Enable Future Action” checkbox field.
- After reloading the page, enable the checkbox; then the year will display correctly.
- Publish a post with the correct expiration date for the post publication.
Environment:
WordPress: v. 6.3
PublishPress Future: v. 3.1.3-hotfix.568
PHP: v. 7.4.33@rizaardiyanto?– thank you for your job! I will try to test this hotfix version ??
@rizaardiyanto – The view is the same as yours, only in the field “Default Date/Time Offset” there is +1 month. Nothing special.
Screen: https://drive.google.com/file/d/1uiK_sI5PqTl6CglpClv2kQ6oAzLMYBcl/viewWe are fighting with the same issue here:
https://www.ads-software.com/support/topic/setting-year-not-works/@rizaardiyanto – We have deactivated all plugins and temporarily switched to the default theme (Twenty Twenty-Four, Twenty Twenty-Three). Unfortunately, the issue persists.
We updated all plugins and now we got:
WordPress: v. 6.4.1
PublishPress Future: v. 3.1.3
Timezone: Warsaw (in WP settings)
PublishPress Future settings:
Date Format (l F jS, Y),
Time Format (g:ia),
Default Date/Time Offset (+1 month) (in custom post types too)We tried, but it didn’t work. We even changed the language of the entire WordPress to English, but the problem still persists.
I have the same problem. The issue appears when I try to set the expiration time using the classic editor.
When I create a new post, everything is okay at times. Other times, the year is randomly set to, for example, 0567. It’s randomized…This screen is in Polish language, but it appears the same in any other languages.