Skip to content
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

Closed
jasonvarga opened this issue Dec 7, 2017 · 0 comments
Closed

First #1

jasonvarga opened this issue Dec 7, 2017 · 0 comments

Comments

@jasonvarga
Copy link
Member

It was too heavy of a decision to decide on what the first issue should be.

Instead, here is Nick Offerman.

jasonvarga pushed a commit that referenced this issue Nov 27, 2019
jasonvarga pushed a commit that referenced this issue Feb 17, 2020
jasonvarga pushed a commit that referenced this issue Apr 17, 2020
FrittenKeeZ pushed a commit to FrittenKeeZ/cms that referenced this issue Aug 9, 2022
linaspasv added a commit to linaspasv/cms that referenced this issue Dec 12, 2022
@what-the-diff what-the-diff bot mentioned this issue Dec 14, 2022
27 tasks
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant