Kunena / Kunena-Forum

Kunena Forum - Forum / Bulletin Board / Discussions component for Joomla - This is the 6.x/5.x main development branch. Please do not open issues regarding earlier versions of Kunena
https://www.kunena.org
GNU General Public License v3.0
1.75k stars 811 forks source link

Kunena discuss breaks front end #9699

Closed N6REJ closed 2 months ago

N6REJ commented 5 months ago

Describe the bug enabled kunena discuss plugin causes a catastrophic failure to the front end.

To Reproduce Steps to reproduce the behavior:

  1. Go to discus plugin
  2. Click on enable
  3. go to front end
  4. See error

Expected behavior discus works as designed

Actual result image

Screenshots If applicable, add screenshots to help explain your problem.

System information (please complete the following information)

Joomla version: 5.1.1 Kunena version: 6.3.2 Php version: 8.3 Database version: 10.5.24-MariaDB-cll-lve

Desktop (please complete the following information):

Smartphone (please complete the following information):

Additional context Add any other context about the problem here.

systeminfo-2024-06-27T14_10_45+00_00.txt

N6REJ commented 5 months ago

@rich20 I see you gave it an unconfirmed status. Does this mean you were able to apply discuss without issues to J5?

AlisonAMG commented 5 months ago

Can confirm this happened. It works flawlessly on the clients J3 site but on J5 we confirmed the settings and turned it on that the issue as shown shuts down the site. Unpublish and the site comes back up.

rich20 commented 5 months ago

@rich20 I see you gave it an unconfirmed status. Does this mean you were able to apply discuss without issues to J5?

You are right, I cannot reproduce this error. I only add the red bug label if I can reproduce and confirm an error.

N6REJ commented 5 months ago

@rich20 I see you gave it an unconfirmed status. Does this mean you were able to apply discuss without issues to J5?

You are right, I cannot reproduce this error. I only add the red bug label if I can reproduce and confirm an error.

Perhaps you can recommend things we can test/check. From a dev perspective there is nothing a user can do that would trigger this short of screwing with the extension code and that would've been fixed with a re-install of the discuss.
Keep in mind we are ONLY talking about discuss.

rich20 commented 5 months ago

Perhaps you can recommend things we can test/check.

Set the error reporting in the Joomla configuration to maximum and enable the debug mode, then you should receive a more accurate error message.

N6REJ commented 5 months ago

Perhaps you can recommend things we can test/check.

Set the error reporting in the Joomla configuration to maximum and enable the debug mode, then you should receive a more accurate error message.

image fresh download and attempted reinstall using drag-n-drop gives image using file upload with same file gives image

so, idk how your not getting the error but its very clearly a kunena discuss issue.

Ruud68 commented 5 months ago

I have just tried this:

  1. Joomla 5.1.1
  2. install Kunena 6.3.2
  3. install Kunena 6.3.2 languages
  4. install Kunena discuss 6.0.5

Without issues

Now looking at the error when installing I would like to ask you to add the following code in the Kunena Discuss 6.0.5

File: install.script.php

replace line 17:

defined('_JEXEC') or die();

with:

defined('_JEXEC') or die();

/**
 * We need to 'force' the KunenaDiscussInstallerHelper from the installation package as:
 *  1. autoloading doesn't work on new installs
 *  2. when the KunenaDiscussInstallerHelper is updated we must make sure that it will use the updated version
 */
require_once __DIR__ . '/src/Helper/KunenaDiscussInstallerHelper.php';

Can you tell me if that changes anything?

N6REJ commented 5 months ago

yep, that solved the issue plg_kunenadiscuss_v6.0.5a_2023-12-10.zip

AlisonAMG commented 5 months ago

Thank you Ruud and Richard :) Very much appreciated.

Ruud68 commented 5 months ago

just did a PR to the addon repo: https://github.com/Kunena/Kunena-Addons/pull/315

github-actions[bot] commented 4 months ago

This issue is stale because it has been open 30 days with no activity.

xillibit commented 2 months ago

The PR has been merged yerstayday