Search Results (Searched for: message)

Yesterday 15:01

The next Error is when i want to answer to a topic or click on "new topic". I can't write any text because the Editor field missing. Just the field "subject" is there. Instead of the editor field this error message appears:
Rendering Error in layout Widget/Editor: The image file does not exist. in /var/www/html/components/com_kunena/template/aurelia/layouts/widget/editor/ckeditor.php on line 49
Layout was rendered in /var/www/html/components/com_kunena/template/aurelia/layouts/topic/edit/default.php on line 373

Do you have a backup of the old page? Go to /media/kunena/emoticons and check if all smileys are there. If not, copy them from the old site into this folder.
It may also help if you install the Kunena sample data ( see here ).
Yesterday 14:08
Hello rich,

I have repair these two menu items and update kunea to 6.2.6 but the descriped error messages are still there. Also the Editor field is missing.

Here the new Configuration report:

This message contains confidential information

Database collation check: The collation of your table fields are correct

Joomla! SEF: Enabled | Joomla! SEF rewrite: Enabled | FTP layer: Disabled |

This message contains confidential information
htaccess: Exists | PHP environment: Max execution time: 30 seconds | Max execution memory: 128M | Max file upload:

Kunena menu details:

Warning: Spoiler!

Joomla default template details : YOOtheme | author: YOOtheme | version: 4.3.11 | creationdate: April 2024

Kunena default template details : Aurelia | author: Kunena Team | version: 6.2.6 | creationdate: 2024-04-16

Kunena template params:

Warning: Spoiler!

Kunena version detailed: Kunena 6.2.6 | 2024-04-16 [ Git Repository ]
| Kunena detailed configuration:

Warning: Spoiler!
| Kunena integration settings:
Warning: Spoiler!
| Joomla! detailed language files installed:
Warning: Spoiler!

Third-party components: None

Third-party SEF components: None

Plugins: None

Modules: None

Yesterday 12:24
Hello,
after the Update from Joomla 3 to Joomla 4 and Kunea 5 to Kunea 6, i become Error messages.

In top of a topic and next to an Admin-User this error message appears:
Warning: Undefined property: stdClass::$rankImage in /var/www/html/libraries/kunena/src/User/KunenaUser.php on line 1720
or
Warning: Undefined property: stdClass::$rankId in /var/www/html/libraries/vendor/joomla/database/src/DatabaseDriver.php on line 1382

The next Error is when i want to answer to a topic or click on "new topic". I can't write any text because the Editor field missing. Just the field "subject" is there. Instead of the editor field this error message appears:
Rendering Error in layout Widget/Editor: The image file does not exist. in /var/www/html/components/com_kunena/template/aurelia/layouts/widget/editor/ckeditor.php on line 49
Layout was rendered in /var/www/html/components/com_kunena/template/aurelia/layouts/topic/edit/default.php on line 373

Can anyone help me?



This message contains confidential information

Database collation check: st_kunena_logs have wrong collation of type utf8mb3_general_ci on field ip st_kunena_logs have wrong collation of type utf8mb3_general_ci on field operation st_kunena_ranks have wrong collation of type utf8mb3_general_ci on field rank_title st_kunena_ranks have wrong collation of type utf8mb3_general_ci on field rank_image st_kunena_sessions have wrong collation of type utf8mb3_general_ci on field allowed st_kunena_sessions have wrong collation of type utf8mb3_general_ci on field readtopics st_kunena_smileys have wrong collation of type utf8mb3_general_ci on field code st_kunena_smileys have wrong collation of type utf8mb3_general_ci on field location st_kunena_smileys have wrong collation of type utf8mb3_general_ci on field greylocation st_kunena_user_categories have wrong collation of type utf8mb3_general_ci on field params st_kunena_user_topics have wrong collation of type utf8mb3_general_ci on field params st_kunena_users have wrong collation of type utf8mb3_general_ci on field status_text st_kunena_users have wrong collation of type utf8mb3_general_ci on field view st_kunena_users have wrong collation of type utf8mb3_general_ci on field signature st_kunena_users have wrong collation of type utf8mb3_general_ci on field avatar st_kunena_users have wrong collation of type utf8mb3_general_ci on field personalText st_kunena_users have wrong collation of type utf8mb3_general_ci on field location st_kunena_users have wrong collation of type utf8mb3_general_ci on field icq st_kunena_users have wrong collation of type utf8mb3_general_ci on field yim st_kunena_users have wrong collation of type utf8mb3_general_ci on field skype st_kunena_users have wrong collation of type utf8mb3_general_ci on field twitter st_kunena_users have wrong collation of type utf8mb3_general_ci on field facebook st_kunena_users have wrong collation of type utf8mb3_general_ci on field myspace st_kunena_users have wrong collation of type utf8mb3_general_ci on field linkedin st_kunena_users have wrong collation of type utf8mb3_general_ci on field delicious st_kunena_users have wrong collation of type utf8mb3_general_ci on field friendfeed st_kunena_users have wrong collation of type utf8mb3_general_ci on field digg st_kunena_users have wrong collation of type utf8mb3_general_ci on field blogspot st_kunena_users have wrong collation of type utf8mb3_general_ci on field flickr st_kunena_users have wrong collation of type utf8mb3_general_ci on field bebo st_kunena_users have wrong collation of type utf8mb3_general_ci on field websitename st_kunena_users have wrong collation of type utf8mb3_general_ci on field websiteurl st_kunena_users_banned have wrong collation of type utf8mb3_general_ci on field ip st_kunena_users_banned have wrong collation of type utf8mb3_general_ci on field reason_private st_kunena_users_banned have wrong collation of type utf8mb3_general_ci on field reason_public st_kunena_users_banned have wrong collation of type utf8mb3_general_ci on field comments st_kunena_users_banned have wrong collation of type utf8mb3_general_ci on field params

Joomla! SEF: Enabled | Joomla! SEF rewrite: Enabled | FTP layer: Disabled |

This message contains confidential information
htaccess: Exists | PHP environment: Max execution time: 30 seconds | Max execution memory: 128M | Max file upload:

Kunena menu details:

Warning: Spoiler!

Joomla default template details : YOOtheme | author: YOOtheme | version: 4.3.11 | creationdate: April 2024

Kunena default template details : Aurelia | author: Kunena Team | version: 6.1.4 | creationdate: 2023-10-05

Kunena template params:

Warning: Spoiler!

Kunena version detailed: Kunena 6.1.4 | 2023-10-05 [ Git Repository ]
| Kunena detailed configuration:

Warning: Spoiler!
| Kunena integration settings:
Warning: Spoiler!
| Joomla! detailed language files installed:
Warning: Spoiler!

Third-party components: None

Third-party SEF components: None

Plugins: None

Modules: None

16 Apr 2024 00:49 - 16 Apr 2024 00:49
Looks like that nightly build did it's magic.

The stdArray error is no longer visible on the front end.

As a bonus it looks like all the other errors I was experiencing in the back end have also gone away as reported here: www.kunena.org/forum/k-6-2-0-support/168...to-j4-upgrade#231069

Namely,
1. "Specified key too long error" when tables were being upgrade for J3>j J4
2. Accessing the Reporting config setting is also now possible (before it was showing the stdClass error.

Thanks!
07 Apr 2024 19:19
Replied by Hifi2you on topic Change language

You can find the text in "/language/en-GB/en-GB/com_kunena.ini" in column COM_KUNENA_BBCODE_SECURE_TEXT_GUESTS = "This message contains secure Information".
You can change the text accordingly in the Danish language file.

gindi


 
Can you guide me to find where it is ?
I cant find it 

Thanks
 
07 Apr 2024 14:03
Replied by Gindi on topic Change language
You can find the text in "/language/en-GB/en-GB/com_kunena.ini" in column COM_KUNENA_BBCODE_SECURE_TEXT_GUESTS = "This message contains secure Information".
You can change the text accordingly in the Danish language file.

gindi

 
07 Apr 2024 13:12
Change language was created by Hifi2you
Is it possible to change the text in the red square to Danish ?
It is the message that appears when you have written a private message.

 

Thanks


 
06 Apr 2024 15:50 - 06 Apr 2024 15:52
Did not see any errors with error reporting. Here is the page I get when I try to edit my profile. Configuration follows. 


#FunctionLocation1()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:10652FWD\Illuminate\Foundation\Application->abort()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Foundation/helpers.php:423fwd_abort()JROOT/components/com_jreviews/routes/web-legacy-joomla.php:1204JReviewsLegacyRouting()JROOT/components/com_jreviews/routes/web.php:735FWD\Illuminate\Support\ServiceProvider->{closure}()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Routing/CallableDispatcher.php:366FWD\Illuminate\Routing\CallableDispatcher->dispatch()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Routing/Route.php:2067FWD\Illuminate\Routing\Route->runCallable()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Routing/Route.php:1818FWD\Illuminate\Routing\Route->run()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Routing/Router.php:6789FWD\Illuminate\Routing\Router->FWD\Illuminate\Routing\{closure}()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:12410FWD\Illuminate\Pipeline\Pipeline->FWD\Illuminate\Pipeline\{closure}()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Routing/Middleware/SubstituteBindings.php:4411FWD\Illuminate\Routing\Middleware\SubstituteBindings->handle()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:15812FWD\Illuminate\Pipeline\Pipeline->FWD\Illuminate\Pipeline\{closure}()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:10113FWD\Illuminate\Pipeline\Pipeline->then()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Routing/Router.php:67814FWD\Illuminate\Routing\Router->runRouteWithinStack()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Routing/Router.php:66515FWD\Illuminate\Routing\Router->runRoute()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Routing/Router.php:63816FWD\Illuminate\Routing\Router->dispatchToRoute()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Routing/Router.php:62817FWD\Illuminate\Routing\Router->dispatch()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:15018FWD\Illuminate\Foundation\Http\Kernel->FWD\Illuminate\Foundation\Http\{closure}()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:12419FWD\Illuminate\Pipeline\Pipeline->FWD\Illuminate\Pipeline\{closure}()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Http/Middleware/HandleCors.php:4520FWD\Illuminate\Http\Middleware\HandleCors->handle()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:15821FWD\Illuminate\Pipeline\Pipeline->FWD\Illuminate\Pipeline\{closure}()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php:10122FWD\Illuminate\Pipeline\Pipeline->then()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:12823FWD\Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter()JROOT/components/com_s2framework/build/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:10924FWD\Illuminate\Foundation\Http\Kernel->handle()JROOT/components/com_s2framework/build/bootstrap/joomla.php:9325s2framework\s2_dispatch()JROOT/components/com_jreviews/jreviews/cms_compat/joomla/bootloader.php:1326require()JROOT/components/com_jreviews/joomla.php:2627JReviews\JReviews->__invoke()JROOT/components/com_jreviews/jreviews.php:2528require_once()JROOT/libraries/src/Dispatcher/LegacyComponentDispatcher.php:7129Joomla\CMS\Dispatcher\LegacyComponentDispatcher::Joomla\CMS\Dispatcher\{closure}()JROOT/libraries/src/Dispatcher/LegacyComponentDispatcher.php:7330Joomla\CMS\Dispatcher\LegacyComponentDispatcher->dispatch()JROOT/libraries/src/Component/ComponentHelper.php:36131Joomla\CMS\Component\ComponentHelper::renderComponent()JROOT/libraries/src/Application/SiteApplication.php:21832Joomla\CMS\Application\SiteApplication->dispatch()JROOT/libraries/src/Application/SiteApplication.php:26133Joomla\CMS\Application\SiteApplication->doExecute()JROOT/libraries/src/Application/CMSApplication.php:30634Joomla\CMS\Application\CMSApplication->execute()JROOT/includes/app.php:5835require_once()JROOT/index.php:32



This message contains confidential information

Database collation check: The collation of your table fields are correct
        

Joomla! SEF: Enabled | Joomla! SEF rewrite: Enabled | FTP layer: Disabled |
        

This message contains confidential information
htaccess: Exists | PHP environment: Max execution time: 30 seconds | Max execution memory: 128M | Max file upload:  

Kunena menu details:

Warning: Spoiler!

Joomla default template details : shaper_helixultimate | author: JoomShaper.com | version: 2.0.18 | creationdate: Feb 2018

Kunena default template details : Aurelia | author: Kunena Team | version: 6.2.5 | creationdate: 2024-03-21

Kunena template params:

Warning: Spoiler!

Kunena version detailed: Kunena 6.2.5 | 2024-03-21 [ Git Repository ]
        | Kunena detailed configuration:

Warning: Spoiler!
| Kunena integration settings:
Warning: Spoiler!
| Joomla! detailed language files installed:
Warning: Spoiler!

Third-party components: None

Third-party SEF components: None

Plugins: None

Modules: Kunena Login 6.0.6

06 Apr 2024 14:23
Hello Gindi,

Thanks for the response, I appreciate your help.

I wonder if the email templates are being produced by a separate component / plugin I am running?

Anyway, having edited the contents of the two accessible email templates and tested the resulting messages received, there is no change to the format or text and I still receive the standard email from Kunena. Not to worry, I shall find an alternative method for altering the format, layout and text that the user receives when the Kunena component sends notifications.

I am assuming that an override will be required and perhaps there is information regarding this in the documentation, so I shall go and search for that.

Kunena is a very good extension however, there are some accessibility issues when using a screen reader to interact with the frontend. I shall find a section of the forum to post my observations on how the accessibility can be improved for the visually impaired.

All the best,
Z.
06 Apr 2024 09:48
In my installation with Joomla version: 5.0.3 and Kunena version: 6.2.5 I can't find any entry "com_kunena_mail_replymoderator_title" on the admin page under System > E- Mail Templates >.
In my email templates there is no entry starting with "com_kunena_".
I only have entries with "com_actionlogs.xxx" , "com_config.xxxx" , com_contact.xxxx" , com_messages.xxx" , "com_privacy.xxxx" and "com_users.xxxx" .
Then there are three entries starting with "plg", "plg_task_privacyconsent.request.reminder" , "plg_task_updatenotification.mail" and "plg_user_joomla.mail".
 I also get no error messages.

Best regards
gindi
04 Apr 2024 13:19 - 04 Apr 2024 13:19
Hello,

It seems in the update process the news tables hasn't been created. Do a abckup of your database and set your prefix for the tables and run that in phpmyadmin :
Code:
CREATE TABLE IF NOT EXISTS `#__kunena_private` (                 `id`          int                                 NOT NULL AUTO_INCREMENT,                 `parent_id`   int                                 NOT NULL DEFAULT '0',                 `author_id`   int                                 NOT NULL DEFAULT '0',                 `created_at`  datetime                            NOT NULL,                 `attachments` tinyint                             NOT NULL DEFAULT '0',                 `subject`     tinytext COLLATE utf8mb4_unicode_ci NOT NULL,                 `body`        text COLLATE utf8mb4_unicode_ci     NOT NULL,                 `params`      text COLLATE utf8mb4_unicode_ci     NOT NULL,                 PRIMARY KEY (`id`),                 KEY `parent_id` (`parent_id`),                 KEY `author_id` (`author_id`),                 KEY `created_at` (`created_at`)                 );             CREATE TABLE IF NOT EXISTS `#__kunena_private_attachment_map` (                 `private_id`    int NOT NULL,                 `attachment_id` int NOT NULL,                 PRIMARY KEY (`private_id`, `attachment_id`),                 KEY `attachment_id` (`attachment_id`)                 );             CREATE TABLE IF NOT EXISTS `#__kunena_private_post_map` (                 `private_id` int NOT NULL,                 `message_id` int NOT NULL,                 PRIMARY KEY (`private_id`, `message_id`),                 KEY `message_id` (`message_id`)                 );             CREATE TABLE IF NOT EXISTS `#__kunena_private_user_map` (                 `private_id` int      NOT NULL,                 `user_id`    int      NOT NULL,                 `read_at`    datetime NOT NULL,                 `replied_at` datetime NOT NULL,                 `deleted_at` datetime NOT NULL,                 PRIMARY KEY (`private_id`, `user_id`),                 KEY `user_id` (`user_id`)                 );
04 Apr 2024 12:48
Hi Gingi, thanks for your reply.
I checked the database. All of these tables are missing.
How can I restore these missing tables?

"Enable private messages" is set to Yes. But there is no difference if I set it to "No".
04 Apr 2024 01:47
[SOLVED] Error Message:  Cannot use object of type stdClass as an array'     See solution here: 
www.kunena.org/forum/k-6-2-0-support/168...lass-as-array#231095

I installed Kunena 6.24 and the front end error message has gone away and the forum loads fine now.  

That said, I a still seeing "Specified key is too long; Max key length is 1000 bytes" upon installation of 6.24
03 Apr 2024 21:56 - 04 Apr 2024 01:43
So the huge lingering issues that I cannot get to the bottom off are:

Front End: "Cannot use object of type stdClass as an array'

Backend: "Specified key is too long; Max key length is 1000 bytes".   (Occurs when tables updated during install of Kunena 6.25.   J3 version was uninstalled prior to J4 upgrade)

I've dome some tests on a cleaner instal (removing J3 tables) and i STILL get errors so seems like no confidence this will work either.

But yes, a better understanding about what these errors means and if they are related is vital to figure this out.  

 
03 Apr 2024 20:43
Did you find this line ? "../public_html/libraries/kunena/src/Config/KunenaConfig.php (1803)"
Displaying 1 - 15 out of 21255 results.
Time to create page: 2.562 seconds