-
-
Notifications
You must be signed in to change notification settings - Fork 540
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
First #1
Comments
Closed
jasonvarga
pushed a commit
that referenced
this issue
Apr 17, 2020
This was referenced Jul 12, 2020
Closed
This was referenced Oct 24, 2021
FrittenKeeZ
pushed a commit
to FrittenKeeZ/cms
that referenced
this issue
Aug 9, 2022
Small fixes from unit tests
linaspasv
added a commit
to linaspasv/cms
that referenced
this issue
Dec 12, 2022
…f type string is deprecated
27 tasks
This was referenced Jan 4, 2023
bastihilger
referenced
this issue
in bastihilger/cms
Jan 31, 2023
I would really really like to tell you how to reproduce this error - unfortunately this only happens in one of my projects, and it is a project that I started with a very early version of V3. I did update it over time and I am on the latest version, and it is a multisite project. If you would prefer, I could try to make a branch of this project where I strip it down to the minimum needed content for this error to occur and put it up somewhere for inspection. What happens is the following: when editing some Collection entries with Taxonomies, right at the point where I made the proposed change in the file, `$taxonomies` is not an array, but a simple string (the handle of the taxonomy in question). That of course throws the error "count(): Argument #1 ($value) must be of type Countable|array, string given" (because of the `count($taxonomies)` a few lines further down) - and my clients can't update their content anymore. I know adding this line does nothing for most users - but it would help me a tremendous amount. Thanks for considering it, Sebastian
This was referenced Mar 13, 2023
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It was too heavy of a decision to decide on what the first issue should be.
Instead, here is Nick Offerman.
The text was updated successfully, but these errors were encountered: