Replies: 3 comments 1 reply
-
Yes
Thanks to you, this is not the case anymore (During the development process, J4 was at RC stage and many APIs have been changed since, we faced some serialization issues that apparently were linked to Joomla itself, so we introduced a workaround for some caching issues that hopefully are not required anymore)
Yes, what made our work so hassling was the fact to not break future compatibility with potential future K2 releases (No db change, No API change), more over the current fork still point to K2 official update link and we did not increase the version number in our code. This means that whenever an official k2 version is released you will be notified to update. Just make sure by then that the official K2 release is compatible with J4 or J5 and not another <=J3 compatible release. |
Beta Was this translation helpful? Give feedback.
-
|
You're right, I do keep a close eye on caching. My blog is on AWS and I have to strictly monitor resource consumption. |
Beta Was this translation helpful? Give feedback.
-
|
after chance to joomla 4 and than to 5 I get this error bei using the User Menu as frontend modul. What can I do? ..../htdocs/modules/mod_k2_user/helper.php:110 | Function | Location-- | -- | -- |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'll ask those questions here. Because they're not bugs, they're questions.
Beta Was this translation helpful? Give feedback.
All reactions