Ok, looks like a database problem. My new test field saves fine. Most likely the table pointer is broken for your fields. Please PM database login credentials (e.g. phpmyadmin login) and will see what's wrong with those field rows.
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.
Have reviewed your database. Those fields had no tablecolumn associated with them, which is why they couldn't store. Where did these fields come from? I'm not sure how this could happen unless they were manually added to the database maybe. I've went ahead and fixed their tablecolumn for you and everything appears to be storing fine now. Please also test to ensure they're storing fine. Newly created fields appear to work fine as well so I'm not sure what happened to these.
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.
I didn't add anything manually or do anything with CB Subs beyond a "typical install." I used brand new versions of everything, didn't migrate data, and only created one or two custom fields after the basic installation using the typical method in the backoffice interface. So I can't say how the issue became the issue. I typically don't go into a DB unless I have no choice. I just don't know enough to be effective although I have been know to go in to reset a password or two.
In any case, I appreciate the massive effort and your patience. This has been a great learning experience for me. CB Subs is amazing as are all the support staff.
And yes, everything is indeed working perfectly!
Many, MANY thanks to you and everyone st Joomlapolis. I remain a huge fan.
Mark
P.S. I've noticed a lot of irritating minor issues with this update to 3.4.0 (and now 3.4.1) mainly due to CSS stuff but perhaps there is something more sinister at play with this latest update of Joomla? Just a thought.
krileon
