Support › MB Custom Table › Custom tables NOT BEING CREATEDResolved
MB Custom Tables won't created a new table. Here's a link that shows my server's php errors. I have tried this on multiple sites, and having same problem. Using MB AIO, though I've had to separately download the Tables plugin separately as it isn't included in the AIO options (along with some others). I've uninstalled and reinstalled, and same issues.
And to offer full context, I’m having MANY issues (all/only with Meta Box plugins). (1) And a huge one is that Custom field data created by new post types and new taxonomy ISN'T APPEARING in the site when added via Meta Box – Beaver Themer Integrator. Kinda the point, right? (2) MB Relationships – I get this error when Network Activating the MB Relationships plugin:
Fatal error: Cannot declare class MB_Relationships_Table, because the name is already in use in /var/web/site/public_html/wp-content/plugins/mb-relationships/inc/database/class-mb-relationships-table.php on line 12
Thus, MB Relationships not in use (not activatable).
All plugins up-to-date, though MB Custom Table won’t update from 1.1.6 to 1.1.7, and MB Relationships won’t activate. I"m at a total standstill, and would greatly appreciated help in getting my life moving forward again!
Did you create the custom table with code? The MB Custom Table doesn't create the table automatically. Instead, you need to put a small snippet into your theme's
functions.php file to create a table manually. Here is the guide on doing that.
If you already did that but no tables are created, please check if your database user has privileges to create new tables. Some hosts don't allow you to do that.
Regarding issue with displaying fields on the front end, are the fields just normal custom fields or they're fields used with custom table? As there is still a problem with custom table, the custom fields don't work properly until we resolve it.
I'll answer your question about MB Relationships in another topic of yours.
Hi Anh - Regarding my issue with displaying fields on the front end, I realize now that that's where I should be starting, as MB Custom Tables issue is my own setup issue. This is my biggest issue. So, I've unflagged MB Tables on both custom field groups I was attempting to use them with (so we can disqualify that as contributing to this issue). I'll attempt that again after I first resolve this primary issue of fields not displaying.
So let me add this possibly important piece of info...the only custom fields that are properly showing up are fields that were previously created with Pods! That just dawned on me. All Pod plugins were deactivated at the time I purchased my license with you, and were deleted, however the posts that are properly outputting custom fields are only my old ones created with them. Only the new ones created with MB are having issues of displaying custom fields on the front end.
Here's a summary of examples:
Old custom post types created with Pods + old custom fields originally created with Pods = properly displaying on front end
Old custom post types created with Pods + new custom fields originally created with MB = not displaying on front end
New custom post types created with MB + old custom fields originally created with Pods = not displaying on front end
New custom post types created with MB + new custom fields originally created with Pods = not displaying on front end
I got it. Let's try to fix the issue with the BB first.
Please deactivate everything related to Pods, since we don't need it anymore.
On the front end, if you keep your old modules / shortcodes, then the custom fields with Pods might be still outputted correctly. It's not a bug, it's just BB can still retrieve data from custom fields even when the plugin is deactivated. (Of course, the data is still in the database, so BB is able to retrieve it).
Regarding fields that you created with Meta Box, can you check if you installed and activated the Meta Box - Beaver Themer Integrator extension? This extension helps you to output the custom field easier. See the screenshot on the plugin page and let me know if there's anything unclear.