Kunena 6.3.3 released

The Kunena team has announce the arrival of Kunena 6.3.3 [K 6.3.3] in stable which is now available for download as a native Joomla extension for J! 4.4.x/5.0.x/5.1.x. This version addresses most of the issues that were discovered in K 6.2 / K 6.3 and issues discovered during the last development stages of K 6.3
Note: Please go to the Kunena Dashboard after an upgrade so that the Kunena database tables are also updated.

Solved KunenaScssPhp\ScssPhp\Parser:

More
8 months 1 week ago - 8 months 1 week ago #1 by Chico Gois
Joomla 5.0
PHP 8.1
Kunena version:6.2.1
I have this error.
Thanks
Code:
KunenaScssPhp\ScssPhp\Parser::registerPushedBlock(): Argument #1 ($b) must be of type KunenaScssPhp\ScssPhp\Block, ScssPhp\ScssPhp\Block\DirectiveBlock given, called in /home/u141892142/domains/mysite/public_html/libraries/kunena/External/scssphp/scssphp/src/Parser.php on line 879

Atenciosamente,

Chico Gois
Last edit: 8 months 1 week ago by Chico Gois.
The following user(s) said Thank You: TomasFC

Please Log in or Create an account to join the conversation.

More
8 months 1 week ago - 8 months 1 week ago #2 by xillibit
Hello,

I have looked to it but i don't have this issue it don't goes at the line that he said

Do-you have set a  custom.scss file ?

I don't provide support by PM, because this can be useful for someone else.
Last edit: 8 months 1 week ago by xillibit.

Please Log in or Create an account to join the conversation.

More
8 months 1 week ago #3 by TomasFC
Hello,
I don't want to hijack this thread, but I had this same error when upgrading from 6.2.0 to 6.2.1 while on Joomla 4.4 (without upgrading Joomla). 
The same parser error giving a 500 error. 
- I do have a custom.scss file.
- I also have a Gantry template. 
What I noticed is that the @mixin I had in Kunena's custom.scss caused the issue when upgrading to K 6.2.1, without any changes to the file.  I removed that @mixin portion and placed it in the Gantry template's custom.scss file for the entire site. 
That solved the issue for me, as Gantry did parse the scss file properly, and while the mixin was just for the forum, it doesn't affect the rest of the site. 
There could be a bug in the parser. 
Hoping this helps,
Tomás 

Please Log in or Create an account to join the conversation.

More
8 months 6 days ago #4 by Leen
Replied by Leen on topic KunenaScssPhp\ScssPhp\Parser:
If I search locally for mixin on my test site
I mainly come across it a lot in akeeba backup and gantry
so my comment/question is, are all extensions all Up to Date?

L.v.d.A

Please Log in or Create an account to join the conversation.

More
8 months 6 days ago #5 by TomasFC
In my case, yes. All extensions are up to date and compatible with J4.4 

Within the custom.scss file I added quite a bit of code. Amongst all that code was some @include and @mixin 
I removed the portions of both to see if either was breaking when parsing, and the @include instructions were fine, but not the @mixin ...  
So I removed all of that @mixin part of the code I had and the forum was back working. In order to have that back again (mainly color coding categories) I inserted that same code in the main template's custom scss file and it worked fine. Meaning all the color coded categories displayed how I wanted. 
So from that I deduce that
  1. The code was written properly and
  2. Probably, Kunena's parsing of the @mixin functionality has a bug, but it could be something other within my @mixin instructions, though I doubt it as it was quite straightforward. 
Hoping this helps,
Tomás 

Please Log in or Create an account to join the conversation.

More
8 months 5 days ago #6 by xillibit
Hello,

Is-it possible to send to me your file custom.scss ? Like i can try to reproduce it

I don't provide support by PM, because this can be useful for someone else.

Please Log in or Create an account to join the conversation.

More
8 months 4 days ago #7 by Chico Gois
Apologies for the delay.

The problem apparently is with my template

Atenciosamente,

Chico Gois

Please Log in or Create an account to join the conversation.

Time to create page: 0.418 seconds