I noticed that in comprofiler database table there are the fields that the management of CB fields can not see.
Practically in comprofiler table DB I have some fields in more that I can not handle by CB -> Edit Fields.
How is this possible? What can I do to correct?
Thanks for the support
I don't understand what you mean. You've fields in the database that are not showing in Field Management? That typically means they're bad field rows and need to be removed manually. Basically orphaned fields, which we currently don't have a tool to clean up at this time (Fields tool will eventually).
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.
You've fields in the database that are not showing in Field Management?
It could happen when I rename the name of a field?
These fields may cause problems in conditional cb?
Some fields, such as text are not stored. For this I looked at the structure of the DB and I realized that these orphans fields.
I advise me to delete them manually?
Thank you
Shouldn't cause any harm as it's unlikely they'll be loaded. Typically they're plugin fields that got left behind. If their tab id is pointing to a non-existing tab you can try setting their tab id to a valid tab id. Otherwise if you've no need for them you can probably delete them safely, but I highly recommend making a backup first just to be safe.
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.
Excuse me krileon. I want to be precise. Orphaned fields are present in "comprofiler" table and not in "comprofiler_fields" table.
The fields in "comprofiler_fields" table are correct.
I write this because you mezionato the tab id that is not present in comprofiler table.
Can I delete it anyway?
Thank you
krileon
