Support Forum
Support › MB Custom Table › Custom table save error
Hi,
I've a WordPress installation with 2 Custom Post Type (orders and products, over wp default post types).
I'm using Custom Table (order_table) for Order CPT.
When I save a new order, new row is correctly create and populate in custom table order_table.
But also a new empty row (only ID e autoincrement index obviously - others columns are empty) is create in custom order_table when any post type was saved in posts table.
Can you help me?
The metabox for custom table is correctly set and view only on order post
Hello,
I've just tested again with the custom table for only 1 CPT. When I save another CPT, there's nothing happened. Can you please check again? Maybe there's somewhere else that you use the same CPT.
Hi,
I’ve do several test.
when I have a cpt with metabox with custom table I’ve seen this behavior:
If I have other cpt without metabox there’s nothing happened when it is Saved.
But if another cpt has only one metabox, the custom table was populate with an empty row.
when I have more metabox for other cpt nothing happened when it is saved.
Is there some bug?
Hello, can you give me the code to test? This seems to be a weird situation.
Hi,
I've replicate all on a pilvia installation.
https://mbtest.demo.site/wp-admin/
user: mbtest-admin
pass: demopass
https://app.pilvia.com/yourphpmyadmin/copper/sql.php?server=1&db=mbtest&table=wp_customtable&pos=0
user: mbtest
pass:h6YeC7yceywcgUE
Scenario:
CPT test #1 -> Test CPT test #1 (metabox with custom table wp_customtable)
when I save CPT also wp_customtable was populate
CPT test #2 -> no metabox
when I save CPT nothing happened on wp_customtable
standard posts -> (ONLY ONE METABOX) "new meta box for posts" (metabox for standard post)
when I save new post also wp_customtable was populate with an empty row (only postId and AI)
Pages -> two classic metabox
when I save a new page nothing happened on wp_customtable
Hello, I got what you meant. Let me debug it.
Hi, I've just fixed the bug in the version 1.1.3. Please update and let me know how it goes.
Hi,
It seems that the problem was resolved
thanks