bobbysmith007

Alright, there was some problem with the type detection, so I just replaced it with a system of trying to cast to number and if it works great. This seemed to resolve the bug. Thanks for your assistance in tracking down this matter.

Please try out 1.5.3 to get this fixed on your end ??

Cheers,
Russ

I think this was probably due to a bug in the plugin that I have just released a fix for. Please try 1.5.2 and see if your problem is resolved.

Sorry should have included the version number: 1.5.2 is the one with this bug fixed

I am not entirely sure what you are asking, but you should be able to create whatever menu structure you want and just use the [dbte id=table-editor-id] shortcode to include that content on your admin pages. I am not sure, but you can probably use remove_menu_page to remove the default menus if you wanted to.

Hope this helps,
Cheers,
Russ

OK there is a new/fixed version updated, sorry for the confusion.

Cheers and hope you find this plugin useful,
Russ

Apologies, I thought I had fixed this error, but I guess I forgot to push it up to the main repo. I will have it fixed for you soon

Also:
https://www.ads-software.com/support/topic/does-not-show-in-menu-items?replies=3

You need to edit your functions file to add add_db_table_editor calls or the plugin will not display anything. (Please read the provided installation / activation instructions).

It looks like you need to add id_column=”wdt_ID” to that add_db_table_editor call

Usually db tables have some intrinsic id column. If it does not have an id column, something like the following command can add one. The plugin will not adjust table schema automatically.

ALTER TABLE event_registrations ADD COLUMN id int PRIMARY KEY AUTO_INCREMENT;

If you added an “id” column, simply remove this line: “‘id_column’=>’er_id’,” (which was looking for an id_column named “er_id”; “id” is the default name). Hopefully this will get you going.

The basic idea is that we need an easy consistent way to track what rows we are editing and sending back and forth to the server.

—-

still nothing appears in the DB Table Editor

If nothing is displaying you have a problem unrelated to id_column (which only allows editing). You can turn on wordpress debugging as it sounds like you might have an error in your sql or something.

You can add the following line to the top of wp-config, but dont forget to remove it after you figure out your troubles.

define( ‘WP_DEBUG’, true ); define( ‘WP_DEBUG_DISPLAY’, true );

Hope this helps

As stated in the installation instructions, this plugin requires you to edit the functions.php file in your theme to add calls to add_db_table_editor. Without any add_db_table_editor calls, there is no interface to display.

Please look at the README or examples.

Hope this helps and cheers

Do you have a column named ‘id’ in event_registrations? If not you need to specify a single column primary key (preferably an integer) in the ‘id_column’ parameter to add_db_table_editor.

eg:


add_db_table_editor(array(
'title'=>'Event Registrations',
'table'=>'event_registrations',
'id_column'=>'er_id',
'sql'=>'SELECT * FROM event_registrations ORDER BY date_entered DESC'
));


Not sure what data you are dealing with, but I have handled this by adding some nominal paging external to the grid (Eg: query / display results by year). You can change what sql is executed in the grid based on query params. Might not apply in your case, but maybe this helps.

Whoops, misread something, this is still a live bug

It seems like this security bug was fixed rather promptly (I guess, it was fixed in less than a month).

Can I see your add_db_table_editor call, so that I can test it locally please? Setting auto_date to false worked for me:

add_db_table_editor(array(
    'title'=>'DBTE Test',
    'table'=>'dbte_test',
    'sql'=>$sql,
    'auto_date'=>false
  ));