[SOLVED] 12 arguments are required, 2 given

[tusa]

I suddenly get this error?
Have'nt done anything.

best regards Tue

 

[troester]

Where? Enable Joomla System Debug to get an error stack.

Have'nt done anything.

Maybe your host changed to php8?

 

[tusa]

Yes @troester you're absolutely right!
How to fix it, is'nt it possible to update 2 php8?

 

[troester]

With php8 you must update from GitHub.
But nobody reported ever such an error so I don't think it's coming from Fabrik.
Anyway

Where? Enable Joomla System Debug to get an error stack.

 

[tusa]

When I downgrated to php7.4 it worked immediately.

 

[troester]

See my post above.

 

[tusa]

Did'nt help updateing from github.
Did'nt change anything change to joomla own template.

 

[troester]

If you want to get help please read anwers to your questions, give necessary informations etc.

But nobody reported ever such an error so I don't think it's coming from Fabrik.
Anyway
Where? Enable Joomla System Debug to get an error stack.

 

[tusa]

It seems like it's the calculation field that I use...
When using php8 or above there is a problem.

 

[troester]

Which exact Fabrik and Joomla version are you running?
Which Joomla template is showing such an error page?

The given code lines don't match the recent Fabrik 3 GitHub version.

So please update from GitHub.

- Fabrik3: WIKI: Update from GitHub (especially if you are using PHP8)

Additionally check your code in your calc element. It seems to create an error.

 

[tusa]

It is Fabrik 3.10

Even if I use protostar as template

 

[achartier]

You likely have a problem in one of your calc elements for that list.

 

[tusa]

And what could it be?
It's after php8, if I downgrade to php7.4 no problem.

 

[lousyfool]

Additionally check your code in your calc element. It seems to create an error.

 

[tusa]

Someone knows more about code , that can help me, this is my calc element.

// Get a db connection.
$db = JFactory::getDbo();

// Create a new query object.
$query = $db->getQuery(true);

//Select all records from the nemmanus_elementer table where elementer_manus_id same as nemmanus_manus___manus_id.
$query->select($db->quoteName(array('elementer_duration')));
$query->from($db->quoteName('nemmanus_elementer'));
$query->where($db->quoteName('elementer_manus_id') . ' = ' . $db->quote('{nemmanus_manus___manus_id}'));

// Reset the query using our newly populated query object.
$db->setQuery($query);

// Load the results as a list of stdClass objects (see later for more options on retrieving data).
$durations = $db->loadObjectList();

$myDur = 0;
foreach ($durations as $duration)
{
    $myDur+= strtotime("1970-01-01" . $duration->elementer_duration . "Z");
}

if ($counts <> 0) {
$output = sprintf('%02d:%02d:%02d', ($myDur/ 3600),($myDur/ 60 % 60), $myDur% 60);
return $output;
} else {
$output = sprintf('%02d:%02d:%02d', ($myDur/ 3600),($myDur/ 60 % 60), $myDur% 60);
return $output;
}

Seems that my sprintf code are the problem, but why?

 

[troester]

It's not directly your sprintf, but these are breaking the error message, which is using a sprintf itself.

So set some hardcoded $output (really remove the sprintf functions, not only comment them out) to get the underlying error message.

Or update again from GitHub
https://github.com/Fabrik/fabrik/commit/f0518594b24a01d2934c5ccdc6a4a8cc287c2961

 

[tusa]

I have now hardcoded the $output, then the error looks like this:


Do you get anything usefull out of that?

 

[troester]

As the error message tells you: "Undefined variable $counts" (which produces only a Notice in php7 but a warning in php8).
So fix your calc code.


But thanks to your example the issue about non-escaped-% in eror logging showed up

 

[tusa]

Now I got rid of the counts problem.
I get a implicit conversion error now:


How can I find thatconversion error?

 

[troester]

This is php, not Fabrik.

Please use php.net, stackoverflow, Google etc. to check your code, e.g. https://php.watch/versions/8.1/deprecate-implicit-conversion-incompatible-float-string

Maybe it's sufficient if you reduce your Joomla Error Reporting level (but this will not solve the underlying issue).