Skip to Content Skip to Menu

Fatal Error foreach() on User List after Upgrading

  • krileon
  • krileon
  • OFFLINE
  • Posts: 47949
  • Thanks: 8170
  • Karma: 1434
11 years 9 months ago #210050 by krileon
Something wrong with your database. Check _comprofiler_fields and ensure the column "tablecolumns" for all the rows begin with #__ and not jos_.


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.

11 years 8 months ago #210179 by mattchew61
Hey Kyle!

I attached a screenshot of the database westlake_westl1 and the jos_comprofiler_fields table.

You said to ensure the column "tablecolumns" for all the rows begin with #__ and not jos_. But in the screenshot, the rows that begin with #_ and jos_ is called "tables." Just wanted to double check with you before I made the change. Is the table in the screenshot the right one and is the column "table" the right one to change?

Thanks for your help!

Matthew
Attachments:

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

  • krileon
  • krileon
  • OFFLINE
  • Posts: 47949
  • Thanks: 8170
  • Karma: 1434
11 years 8 months ago - 11 years 8 months ago #210213 by krileon
Yes, I meant "tables" column, sorry. You need to fix the ones that state jos_ and change them to #__. They should not be prefixed with jos_. None of the ones that appear problematic are even valid CB fields (they don't begin with cb_) so something installed created them incorrectly or they were altered in database.


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.
Last edit: 11 years 8 months ago by krileon.

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

11 years 8 months ago #210302 by mattchew61
Hey Kyle,

We made the change to the "table" column. Alas, the issue is still there--same fatal error.

I'm about ready to create a support ticket with you guys for this issue, but my professional membership only gives me one a year, right?

Thanks for the help,

--Matthew

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

  • krileon
  • krileon
  • OFFLINE
  • Posts: 47949
  • Thanks: 8170
  • Karma: 1434
11 years 8 months ago - 11 years 8 months ago #210320 by krileon
Please PM backend super administrator login credentials as well as phpmyadmin login credentials. There's no purpose in creating a ticket, I am already helping you here.


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.
Last edit: 11 years 8 months ago by krileon.

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

11 years 8 months ago #210336 by mattchew61
OK, PMing you those details now.

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

Moderators: beatnantkrileon
Powered by Kunena Forum