Skip to Content Skip to Menu

Update error message

  • wasnun
  • wasnun
  • OFFLINE
  • Posts: 3
  • Thanks: 0
  • Karma: 0
4 years 3 months ago #319708 by wasnun
Update error message was created by wasnun
Hi there,

I updated CB 2.4.4 to 2.4.6 and I get a warning message that the installation wasn't quite OK.

Warning
Unknown column 'access' in 'field list'
Package Update: There was an error installing an extension : com_comprofiler.zip

Error
Error Installing package

Any instructions for me? The component seems to work fine, I made tests, I can register and all. What's wrong with that database list / field?

Thanks for any hints you might be able to give.

wasnun

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

  • krileon
  • krileon
  • ONLINE
  • Posts: 48541
  • Thanks: 8290
  • Karma: 1445
4 years 3 months ago #319716 by krileon
Replied by krileon on topic Update error message
The only core CB database table that has an "access" column is CB Blogs, but that's nothing new. So I'm not sure where that's coming from. Try running the database fix tools within CB > Tools to ensure all the core database tables are up to date. If none then it's possible the error came from Joomla or something acting on Joomla installer triggers. I also recommend running Joomlas database tool in Extensions > Manage > Database to be sure your Joomla tables are also up to date.


Kyle (Krileon)
Community Builder Team Member
Before posting on forums: Read FAQ thoroughly + Read our Documentation + Search the forums
CB links: Documentation - Localization - CB Quickstart - CB Paid Subscriptions - Add-Ons - Forge
--
If you are a Professional, Developer, or CB Paid Subscriptions subscriber and have a support issue please always post in your respective support forums for best results!
--
If I've missed your support post with a delay of 3 days or greater and are a Professional, Developer, or CBSubs subscriber please send me a private message with your thread and will reply when possible!
--
Please note I am available Monday - Friday from 8:00 AM CST to 4:00 PM CST. I am away on weekends (Saturday and Sunday) and if I've missed your post on or before a weekend after business hours please wait for the next following business day (Monday) and will get to your issue as soon as possible, thank you.
--
My role here is to provide guidance and assistance. I cannot provide custom code for each custom requirement. Please do not inquire me about custom development.

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

  • wasnun
  • wasnun
  • OFFLINE
  • Posts: 3
  • Thanks: 0
  • Karma: 0
4 years 3 months ago #319721 by wasnun
Replied by wasnun on topic Update error message
Hi Kyle,

thanks for your hints.

1) joomla DB check / fix = everything is fine.
2) CB check Checking Users Database: all green

But then:

CB Tools: Check Core CB database: Results

Core CB database structure differences:
Table #__comprofiler Column id type is int instead of int(11)
Table #__comprofiler Column user_id type is int instead of int(11)
Table #__comprofiler Column hits type is int instead of int(11)
Table #__comprofiler Column message_number_sent type is int instead of int(11)
Table #__comprofiler Column avatarapproved type is tinyint instead of tinyint(4)
Table #__comprofiler Column canvasapproved type is tinyint instead of tinyint(4)
Table #__comprofiler Column canvasposition type is tinyint instead of tinyint(4)
Table #__comprofiler Column approved type is tinyint instead of tinyint(4)
Table #__comprofiler Column confirmed type is tinyint instead of tinyint(4)
Table #__comprofiler Column banned type is tinyint instead of tinyint(4)
Table #__comprofiler Column bannedby type is int instead of int(11)
Table #__comprofiler Column unbannedby type is int instead of int(11)
Table #__comprofiler Column acceptedterms type is tinyint unsigned instead of tinyint(1) unsigned
Table #__comprofiler_field_values Column fieldvalueid type is int instead of int(11)
Table #__comprofiler_field_values Column fieldid type is int instead of int(11)
Table #__comprofiler_field_values Column ordering type is int instead of int(11)
Table #__comprofiler_field_values Column sys type is tinyint instead of tinyint(4)
Table #__comprofiler_fields Column fieldid type is int instead of int(11)
Table #__comprofiler_fields Column maxlength type is int instead of int(11)
Table #__comprofiler_fields Column size type is int instead of int(11)
Table #__comprofiler_fields Column required type is tinyint instead of tinyint(4)
Table #__comprofiler_fields Column tabid type is int instead of int(11)
Table #__comprofiler_fields Column ordering type is int instead of int(11)
Table #__comprofiler_fields Column cols type is int instead of int(11)
Table #__comprofiler_fields Column rows type is int instead of int(11)
Table #__comprofiler_fields Column sys type is tinyint instead of tinyint(4)
Table #__comprofiler_fields Column pluginid type is int instead of int(11)
Table #__comprofiler_lists Column listid type is int instead of int(11)
Table #__comprofiler_lists Column viewaccesslevel type is int unsigned instead of int(10) unsigned
Table #__comprofiler_lists Column ordering type is int instead of int(11)
Table #__comprofiler_members Column referenceid type is int instead of int(11)
Table #__comprofiler_members Column memberid type is int instead of int(11)
Table #__comprofiler_plugin Column id type is int instead of int(11)
Table #__comprofiler_plugin Column viewaccesslevel type is int unsigned instead of int(10) unsigned
Table #__comprofiler_plugin Column ordering type is int instead of int(11)
Table #__comprofiler_plugin Column published type is tinyint instead of tinyint(3)
Table #__comprofiler_plugin Column iscore type is tinyint instead of tinyint(3)
Table #__comprofiler_plugin Column client_id type is tinyint instead of tinyint(3)
Table #__comprofiler_plugin Column checked_out type is int unsigned instead of int(11) unsigned
Table #__comprofiler_tabs Column tabid type is int instead of int(11)
Table #__comprofiler_tabs Column ordering type is int instead of int(11)
Table #__comprofiler_tabs Column ordering_edit type is int instead of int(11)
Table #__comprofiler_tabs Column ordering_register type is int instead of int(11)
Table #__comprofiler_tabs Column pluginid type is int instead of int(11)
Table #__comprofiler_tabs Column sys type is tinyint instead of tinyint(4)
Table #__comprofiler_tabs Column viewaccesslevel type is int unsigned instead of int(10) unsigned
Table #__comprofiler_userreports Column reportid type is int instead of int(11)
Table #__comprofiler_userreports Column reporteduser type is int instead of int(11)
Table #__comprofiler_userreports Column reportedbyuser type is int instead of int(11)
Table #__comprofiler_userreports Column reportedstatus type is tinyint instead of tinyint(4)
Table #__comprofiler_views Column viewer_id type is int instead of int(11)
Table #__comprofiler_views Column profile_id type is int instead of int(11)
Table #__comprofiler_views Column viewscount type is int instead of int(11)
Table #__comprofiler_views Column vote type is tinyint instead of tinyint(3)
Table #__comprofiler_sessions Column userid type is int unsigned instead of int(11) unsigned
Table #__comprofiler_sessions Column ui type is tinyint instead of tinyint(4)
Table #__comprofiler_sessions Column expiry_time type is int unsigned instead of int(14) unsigned
Table #__comprofiler_ratings Column id type is int instead of int(11)
Table #__comprofiler_ratings Column user_id type is int instead of int(11)
Table #__comprofiler_ratings Column item type is int instead of int(11)
Table #__comprofiler_ratings Column target type is int instead of int(11)

What's going on? If I try to correct that I get

An error has occurred.

1054 Unknown column 'access' in 'field list'

Best wishes!

wasnun

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

  • krileon
  • krileon
  • ONLINE
  • Posts: 48541
  • Thanks: 8290
  • Karma: 1445
4 years 3 months ago #319740 by krileon
Replied by krileon on topic Update error message
Enable debug mode and maximum error reporting in Joomla global configuration then retry and see if any further information is output. As is the error isn't giving any hint as to where it's coming from so there's nothing I can suggest. The only access column in the database that exists in core CB belongs to CB Blogs. Do you know what database you're on (e.g. MYSQL or MariaDB) and what version it is (e.g. 5.6, 5.7, etc.. )?


Kyle (Krileon)
Community Builder Team Member
Before posting on forums: Read FAQ thoroughly + Read our Documentation + Search the forums
CB links: Documentation - Localization - CB Quickstart - CB Paid Subscriptions - Add-Ons - Forge
--
If you are a Professional, Developer, or CB Paid Subscriptions subscriber and have a support issue please always post in your respective support forums for best results!
--
If I've missed your support post with a delay of 3 days or greater and are a Professional, Developer, or CBSubs subscriber please send me a private message with your thread and will reply when possible!
--
Please note I am available Monday - Friday from 8:00 AM CST to 4:00 PM CST. I am away on weekends (Saturday and Sunday) and if I've missed your post on or before a weekend after business hours please wait for the next following business day (Monday) and will get to your issue as soon as possible, thank you.
--
My role here is to provide guidance and assistance. I cannot provide custom code for each custom requirement. Please do not inquire me about custom development.

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

  • wasnun
  • wasnun
  • OFFLINE
  • Posts: 3
  • Thanks: 0
  • Karma: 0
4 years 3 months ago - 4 years 3 months ago #319910 by wasnun
Replied by wasnun on topic Update error message
Me again, sorry for being a tad late.

this is the info I have about the database I use

Database Type mysql
Database Version 8.0.21-0ubuntu0.20.04.4
Database Collation utf8_general_ci
Database Connection Collation utf8mb4_0900_ai_ci

This is the debug info regarding the database when I try to check the CB db.

[REMOVED]

Best!

wasnun
Last edit: 4 years 3 months ago by krileon.

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

  • krileon
  • krileon
  • ONLINE
  • Posts: 48541
  • Thanks: 8290
  • Karma: 1445
4 years 3 months ago #319919 by krileon
Replied by krileon on topic Update error message
MySQL 8.0 is untested. I've no idea if Joomla or CB will work on MySQL 8.0. I don't know what more to suggest at this time, sorry. Joomla has a documentation note regarding MySQL 8.0 below in an attempt to force it, but again it's not tested.

docs.joomla.org/Joomla_and_MySQL_8


Kyle (Krileon)
Community Builder Team Member
Before posting on forums: Read FAQ thoroughly + Read our Documentation + Search the forums
CB links: Documentation - Localization - CB Quickstart - CB Paid Subscriptions - Add-Ons - Forge
--
If you are a Professional, Developer, or CB Paid Subscriptions subscriber and have a support issue please always post in your respective support forums for best results!
--
If I've missed your support post with a delay of 3 days or greater and are a Professional, Developer, or CBSubs subscriber please send me a private message with your thread and will reply when possible!
--
Please note I am available Monday - Friday from 8:00 AM CST to 4:00 PM CST. I am away on weekends (Saturday and Sunday) and if I've missed your post on or before a weekend after business hours please wait for the next following business day (Monday) and will get to your issue as soon as possible, thank you.
--
My role here is to provide guidance and assistance. I cannot provide custom code for each custom requirement. Please do not inquire me about custom development.

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

Moderators: beatnantkrileon
Powered by Kunena Forum