?
avatar uglyeoin
uglyeoin
4 Oct 2020

Steps to reproduce the issue

Turn up error reporting to development

Expected result

No errors or warnings.

Actual result

Warning: count(): Parameter must be an array or an object that implements Countable in /home/********/public_html/plugins/content/fields/fields.php on line 97

System information (as much as possible)

systeminfo-2020-10-04T21 15 16+01 00.txt

Additional comments

PHP 7.3.22

avatar uglyeoin uglyeoin - open - 4 Oct 2020
avatar joomla-cms-bot joomla-cms-bot - labeled - 4 Oct 2020
avatar zero-24
zero-24 - comment - 4 Oct 2020

Warning: count(): Parameter must be an array or an object that implements Countable in /home/******/public_html/plugins/content/fields/field

it seems the important part is missing from that message the filename and the line ;)

avatar uglyeoin uglyeoin - change - 4 Oct 2020
The description was changed
avatar uglyeoin uglyeoin - edited - 4 Oct 2020
avatar uglyeoin
uglyeoin - comment - 4 Oct 2020

Warning: count(): Parameter must be an array or an object that implements Countable in /home/******/public_html/plugins/content/fields/field

it seems the important part is missing from that message the filename and the line ;)

Yes, odd that I managed that! I have corrected.

avatar zero-24
zero-24 - comment - 4 Oct 2020

hmm how did you trigger that message? Seems this is the case once here: https://github.com/joomla/joomla-cms/blob/staging/plugins/content/fields/fields.php#L95 the return from FieldsHelper::extract($context); is NULL

And that is only the case when the context is not correct as it looks like:

avatar ceciogit
ceciogit - comment - 4 Oct 2020

hi @uglyeoin im tryin to replicate the issue without success. can u tell me where are you while this error comes up?
i am asking because i have maximum error reporting enabled but do not see this error anywhere.

avatar uglyeoin uglyeoin - change - 4 Oct 2020
Status New Closed
Closed_Date 0000-00-00 00:00:00 2020-10-04 21:00:03
Closed_By uglyeoin
avatar uglyeoin
uglyeoin - comment - 4 Oct 2020

It turns out another component was calling the content which cause this issue. I had turned it off but the other component was cached (Smart Slider 3).

avatar uglyeoin uglyeoin - close - 4 Oct 2020

Add a Comment

Login with GitHub to post a comment