- Issue created by @ishore
- 🇸🇦Saudi Arabia ishore
Changing this line:
->condition('uid', RoleInterface::ANONYMOUS_ID, '<>')
to:
->condition('uid', '0', '<>')
appears to have fixed the error for me.
- Assigned to zanonmark
- Status changed to Postponed: needs info
over 1 year ago 4:37pm 2 May 2023 - 🇮🇹Italy zanonmark
Thanks for reporting Your issue.
However, I wasn't able to reproduce it. Enabling 'By-user checks' and then clicking on 'Add directory' was flawless, as concretely adding a directory.
Did You clear the cache after installing / updating the module?
Thanks,
MZ - 🇸🇦Saudi Arabia ishore
I'm not sure. So I re-instated the original DirectoryForm.php, cleared the cache, clicked on Add Directory, and the error is still there.
Could this be a Postgres vs MySQL thing?
- 🇮🇹Italy zanonmark
Thanks for reporting this issue, which actually seems like a bug indeed - and a one lying there for about 10 years, since they actually changed that constant from an integer to a string (I guess most of the people here is using MySQL, which probably casts strings to 0?).
Only, I replaced with an integer, not a string.
Could You please check the latest code and tell me if everything works for You?Thanks,
MZ - Status changed to Needs review
over 1 year ago 8:26pm 29 May 2023 - 🇸🇦Saudi Arabia ishore
Hello
Where would I find the latest code? I am already at 3.1.0 and I don't see a newer version in the Git repo.
The change I previously mentioned that I made to DirectoryForm.php has not caused any errors since, and the module is working fine for me. I'm not sure if it would throw up errors for MySQL users though.
- Status changed to Fixed
over 1 year ago 2:51pm 31 May 2023 - 🇮🇹Italy zanonmark
Thanks for Your info.
I just released 3.1.1 which checks against 0 (integer) instead of '0' (string) or the previous constant (string too).
It works well under MySQL too.Thanks,
MZ - Status changed to Fixed
over 1 year ago 5:23pm 1 June 2023