0 - call_user_func_array(): Argument #1 ($callback) must be a valid callback

[cmirnow]

After the last push I get this error on the page generated by the tag:

0 - call_user_func_array(): Argument #1 ($callback) must be a valid callback, function "439_Скрипт для преобразования текста в аудио. Google Cloud Text-to-Speech API_conversion-google-cloud-text-to-speech-api_tag_3233" not found or invalid function name

The problem is probably initiated by the fact that the page has the rss feed enabled. But I'm not sure.

I should add that after the last commit, a very large cache size is formed again. Take a look at the screenshot, it's only half a day's worth of site activity:

The problem appears from time to time, after clearing the cache the problem disappears.

[cmirnow]

I was forced to disable the cache. This error is repeated often. Joomla has caching issues always: perhaps this bug needs to be reported on joomla github?

[eworkers]

Please check if the latest commit closes your issue.

I should add that after the last commit, a very large cache size is formed again. Take a look at the screenshot, it's only half a day's worth of site activity

Things looks normal to me, you have a popular website that's all, the size looks (850 MB) normal for 59680 cached items. However i understand your concerns and i do think that k2 config should provide the option for users whether they prefer to disable com_k2_extended cache or no. Its a tradeoff matter for users when i comes to server resources. But this is not what this fork is about.

[cmirnow]

Unfortunately, it doesn't work. Right after installing the new K2 revision, enabling standard caching and clearing the cache, I got this error message. But if the cache is turned off, K2ForJ4 works without problems.

Perhaps it makes a difference? - I don't use the system cache plugin, it's always turned off.

[eworkers]

please check if the latest push fixes your issue

[cmirnow]

I have two news stories. The first news is good news, the second news is bad news.

The bad news: It took me 5 minutes to get this error again with caching enabled. Unfortunately, I see that the error also manifests itself when navigating to the K2 single article page.

Good news: I enabled progressive cache instead of standard cache. And for half an hour I can't catch the error. It's weird and makes me wonder. Maybe I'll get this error in an hour, or a day. I don't know. But maybe you'll find this information helpful as you work on your K2ForJ4 program code.

[cmirnow]

If I get this error with progressive caching enabled, I'll let you know about it.

[cmirnow]

Alas. I see that mistake again. But with progressive caching enabled, the error appears when clicking on the tags at the bottom of any K2 article.

[eworkers]

Alas. I see that mistake again. But with progressive caching enabled, the error appears when clicking on the tags at the bottom of any K2 article.

please check [1c6012e]

[cmirnow]

please check [1c6012e]

I have thoroughly tested the component with standard cache and progressive cache. It seems that this push solves all the problems. Thanks.

[cmirnow]

After clearing the cache, this problem sometimes occurs when navigating to a menu item formed by a tag. After the second click on this link, the problem disappears and does not manifest itself in the future.

I understand that Joomla caching has problems. Question: is it possible to fix this little mishap? If you think it is impossible, please close this issue.

[eworkers]

After clearing the cache, this problem sometimes occurs when navigating to a menu item formed by a tag. After the second click on this link, the problem disappears and does not manifest itself in the future.

I understand that Joomla caching has problems. Question: is it possible to fix this little mishap? If you think it is impossible, please close this issue.

this looks like residues from your browser cache, try to clear browser cache or open new session and test if the problem is there, if it is not that means that i was an old page sitting there in your browser cache from previous error

[cmirnow]

Hmm. It could have been two hours of active work on the site since the previous error. Do you have an interpretation as to why the browser shows the saved error page just after clearing the Joomla cache?

[eworkers]

from your answer can i assume that problem disappeared after cleaning browser cache? and what browser are you using? is it chrome? many users reported issues regarding chrome not respecting cache-control policies, other reported same problem for the first request. And personal wild assumption that error pages in joomla do not pass cache control in headers.

[cmirnow]

https://github.com/eworkers/K2ForJ4/discussions/57