Solution to the problem Model Comments could not fetch column list for the table #__engage_comments

[primok]

I thought I'd share the solution to the Model Comments "could not fetch column list for the table #__engage_comments" problem for those like me who needed to install akkeba engage on Altervista host.
After a thorough analysis of my database I found that after installing the akkeba engage software the xxxxx_engage_comments table was not installed and Idon't Know why.
The xxxxx is the table prefix of my database. By installing the software on a local Xamp server, however, this table was present.
At this point I thought of exporting the missing table from local and importing it remotely.
After this I saw that everything was working correctly as you can check on my website: https: //primok.altervista.org.
The query to execute in your database is:

`-- phpMyAdmin SQL Dump
-- version 5.1.1
-- https://www.phpmyadmin.net/

-- Host: 127.0.0.1
-- Creato il: Nov 05, 2021 alle 22:43
-- Versione del server: 10.4.21-MariaDB
-- Versione PHP: 8.0.12

SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
START TRANSACTION;
SET time_zone = "+00:00";

/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT /;
/!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS /;
/!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION /;
/!40101 SET NAMES utf8mb4 */;

--
-- Database: joomla_db

---

--
-- Struttura della tabella heete_engage_comments

CREATE TABLE heete_engage_comments (
engage_comment_id bigint(20) UNSIGNED NOT NULL,
parent_id bigint(20) UNSIGNED DEFAULT NULL,
asset_id int(10) UNSIGNED NOT NULL,
body longtext NOT NULL,
name varchar(255) DEFAULT NULL,
email varchar(255) DEFAULT NULL,
ip varchar(64) DEFAULT NULL,
user_agent varchar(255) NOT NULL,
enabled tinyint(3) NOT NULL DEFAULT 0,
created_on datetime DEFAULT NULL,
created_by int(11) DEFAULT NULL,
modified_on datetime DEFAULT NULL,
modified_by int(11) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='Content comments';

--
-- Indici per le tabelle scaricate

--
-- Indici per le tabelle heete_engage_comments

ALTER TABLE heete_engage_comments
ADD PRIMARY KEY (engage_comment_id),
ADD KEY heete_engage_comments_asset (asset_id),
ADD KEY heete_engage_comments_created_on (created_on);

--
-- AUTO_INCREMENT per le tabelle scaricate

--
-- AUTO_INCREMENT per la tabella heete_engage_comments

ALTER TABLE heete_engage_comments
MODIFY engage_comment_id bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=7;
COMMIT;

/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT /;
/!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS /;
/!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
`
Where heete is the table prefix of your database.
Best regards.

[nikosdion]

Is it possible that your database user does not have the CREATE privilege? This would prevent it from creating new tables.

Do remember that phpMyAdmin runs under a different, privileged, system user which is not the same as the database user your site runs under.

In this case you will have similar problems installing any extension which needs to install its own tables. For example, trying to install JCE it would be unable to install its profiles table and it would fail to work properly.

In most cases this is trivially fixed through cPanel, Plesk or similar by granting those privileges to your database user. In rare cases you have to contact your host to do that for you.

[primok]

Ok, thanks for the tip.
It is the first time that such a problem has arisen.
The next time a similar problem arises I will refer to what you suggested. Thank you very much.