Is there a way to quote safely however? Because I notice placeholder text with a comma breaks things again.
For example, this breaks:
placeholder::For example, placeholder text.
Thanks,
T
-
This reply was modified 3 years, 4 months ago by Trippetchz.
-
This reply was modified 3 years, 4 months ago by Trippetchz.
:facepalm: Sorry, my bad syntax.
The attributes field formatting should be double colon and no quoting:
placeholder::For example placeholder text.
That works fine. Hope this helps someone!
Oh great, thanks for that. We’ll check that out. 🙂
Hi there,
Okay.
But just to comment, I don’t understand that problem, as described.
At least with Apache-compatible implementations, the .htaccess file resides with the WordPress root, right? So even if WordPress was installed in a directory, say for example, http://example.com/alice/, the .htaccess file would reside in something like /public_html/alice/.htaccess and hence rules from there would be relative, as with root directory installs?
I don’t know though as I haven’t tested that deployment.
In any case, it should be unwanated behaviour to redirect the replaced /wp-login.php or /wp-admin strings at the *end* of a URL.
Good luck and thanks!
Thank you for reply. Yes, undocumented breaking change with -1 was our issue as previous versions of the theme used -1 as “show all.”
Thank you for your help fixing.
That’s really disappointing.
This appears to be fixed in 2.0.8. Thank you!
That’s great news, thanks.
Well, if that’s how it’s supposed to work, it’s not happening. Here’s a screen recording to further illustrate:
https://archive.org/download/2022-03-15-21-30-15/2022-03-15%2021-30-15.mp4
The update time is always wrong.
-
This reply was modified 4 years, 5 months ago by Trippetchz.
Hello there,
I see you have made some changes in 2.0.1 to begin ironing this out. Thanks!
Unfortunately, the bug isn’t completely squashed, although behaviour with ‘Date Recorded’ seems to be better.
Listing members in the admin “Date Recorded” times is now correct, but “Date Updated” isn’t, both on individual records, and in the list. Here are the screenshots to illustrate what I mean:
The “Date Updated” time should match the “Date Recorded” in above example as it was both created and saved at the same time.
And for an example of an edit, my local time (Australia/Melbourne) is 13 March 2022 7:03pm but the field shows 13 March 2022 8:03 am
-
This reply was modified 4 years, 5 months ago by Trippetchz. Reason: typo
-
This reply was modified 4 years, 5 months ago by Trippetchz. Reason: context
Thanks for getting back.
So just to clarify, does that mean this feature is being developed?
Thanks for the consideration 🙂
PS: Also, hopefully with something like wp_date() you won’t have to reinvent the wheel, as it looks like in participants-database\classes\PDb_List_Query.php and participants-database\classes\PDb_admin_list\query.php with all the hardcoded calculating a difference from UTC and Linux epoch—which is precisely the problem here: what happens if UTC is never used or FROM_UNIXTIME is wrong (because again, like above, these are hard low-level server settings that cannot be changed on a shared host)?
I hope I’ve made the case that using a WordPress function to write dates/times will be much easier for you in the long run, less buggy, less complex, and more flexible for other people’s timezones.
🙂
