乔姆拉! 3.6.5 'field list' 中的未知列 'c.version'

Joomla! 3.6.5 Unknown column 'c.version' in 'field list'

我从 plesk 上的一个完全运行的站点获得了文件夹“httpdocs”的副本和 Joomla 数据库的 .sql,并被要求在本地安装该网站。

Joomla的版本是3.6.5,我在en-GB.xml上查过了。原来服务器上的PHP版本是5.4.45,现在我用的是Xampp1.8.2和PHP5.4.31.

更改 configuration.php 以连接到数据库,然后访问该站点后出现此错误:

1054 - Unknown column 'c.version' in 'field list'

SQL=

SELECT c.id, c.asset_id, c.access, c.alias, c.checked_out, c.checked_out_time,
       c.created_time, c.created_user_id, c.description, c.extension,
       c.hits, c.language, c.level, c.lft, c.metadata, c.metadesc,
       c.metakey, c.modified_time, c.note, c.params, c.parent_id,
       c.path, c.published, c.rgt, c.title, c.modified_user_id, c.version,
       CASE
           WHEN CHAR_LENGTH(c.alias) != 0 THEN CONCAT_WS(':', c.id, c.alias)
           ELSE c.id
       END as slug,
       COUNT(i.`id`) AS numitems
FROM #__categories as c
LEFT JOIN (
    SELECT cat.id as id
    FROM #__categories AS cat
    JOIN #__categories AS parent ON cat.lft BETWEEN parent.lft AND parent.rgt
    WHERE parent.extension = 'com_content'
        AND parent.published != 1 GROUP BY cat.id
) AS badcats ON badcats.id = c.id
LEFT JOIN #__categories AS s ON 
    (s.lft < c.lft AND s.rgt > c.rgt AND c.language in ('en-GB','*'))
     OR (s.lft >= c.lft AND s.rgt <= c.rgt)
LEFT JOIN `#__content` AS i ON
     i.`catid` = c.id AND i.state = 1 AND (i.language = '*' OR i.language = 'en-GB')
WHERE (c.extension='com_content' OR c.extension='system')
    AND c.access IN (1,1)
    AND c.published = 1
    AND badcats.id is null
    AND s.id=10
GROUP BY c.id, c.asset_id, c.access, c.alias, c.checked_out,
    c.checked_out_time, c.created_time, c.created_user_id,
    c.description, c.extension, c.hits, c.language, c.level,
    c.lft, c.metadata, c.metadesc, c.metakey, c.modified_time,
    c.note, c.params, c.parent_id, c.path, c.published, c.rgt,
    c.title, c.modified_user_id, c.version
ORDER BY c.lft

据我所知,此错误在从 Joomla! 更新的网站中很常见。 2.5到3.x,这个不是

我对 Joomla! 不是很熟悉,但我会根据任何要求的信息更新此问题。

显然我得到了 Joomla 的数据库! 2.5 而不是当前版本,现在可以正常工作了