bobbysmith007

Did you ever look back into this? If its posting the ajax correctly, was there any error in your php log file or javascript console? What was the reply to that ajax request?

The plugin cannot automatically figure out how to save joined data. You will have to write custom data-saving code.

If you check the examples/cf7dbsubmit_integration.php file there are some examples of custom save hooks.

Hey sorry you are having issues. That looks correct to me. Usually it just posts back to the same page. It was posted on. I will try to check into this soon

I dont know what happened on my end, but suddenly two days later the warnings started showing up. I guess a computer / brain fart.

They are hopefully fixed in 1.8.4

Thanks for bearing with me

Are you sure? I am using the version (1.8.3) from wordpress plugin installer and I get no warnings and the two variables are defined and in the file for me.

Thanks for pointing this out. I believe this is fixed in 1.8.3

Thanks for updating this issue, glad you got it fixed.

So when you type into the “new row” at the end of the page, it immediately adds a new “new-row” just below it. That is so you could add multiple rows at once (not super recommended anyway, but… ). This shouldn’t disrupt the original new row you were editing. Perhaps, that older new-row is resorted weird?

hrmm… I havent experienced that particularly. I just tested it on a local instance with the latest version and I was able to set default_values that worked.

I did notice a weirdness. Usually as soon as you edit the “new” row, it will fill in all the default values at once. However if you edit the column with a default value in it first. It replaces the value typed in with the default value. I didn’t see it clearing anything, but maybe its related. Anyway, thank you for your comment as it uncovered a bug.

Cheers,
Russ

There is an open issue for this on Git Hub, but I have not really looked into custom slick grid editors at all.

It is definitely possible, but usually I have opted for a custom interface when it gets to that point. If you make any progress, please do update the ticket:

https://github.com/AccelerationNet/wp-db-table-editor/issues/11

Hey thank you for the kind offer. I dont think I received your email, or a notification of this comment. I am happy to add you as a github contributor if you want. Thanks so much!

Are you sure you wrote to the correct plugin? You can have a database table that has a notes field and you can edit it, but that doesnt quite sound like what you are looking for?

Can you ensure that DB errors are logged and then check your php-error log? This is probably / almost certainly something borked in the query it is running. I use a SQL parser to try and safely insert WHERE clauses, so that my guess is that something about that is failing.

Just FYI, I am working on adding automatic paging support in the next release 1.7.0 Should be up sometime this week or next

Its just an example, not something you would probably want to copy and paste whole.

The idea is that you modify the SQL that runs based on a URL parameter (year in the example), with a reasonable default if the value is not sent.

      // !!! DONT SQL INJECT !!! This is guaranteed to be a valid integer
      // use wpdb->prepare if you are not sure !!!
      'sql'=>'SELECT * FROM payments'.
            ' WHERE YEAR(date_entered)='.$year.
            ' ORDER BY ID date_entered DESC',

Then code this says, “on appropriate admin pages, enqueue the script that will change the table editor interface”.

add_action('admin_enqueue_scripts','xxx_register_scripts_admin');
function xxx_register_scripts_admin (){
      if(@$_REQUEST['page'] == 'dbte_payments'){ // matches 'id' or 'table' above
        $base_url = get_stylesheet_directory_uri();
        wp_enqueue_script(
          'payment-paging.js', $base_url . '/payment-paging.js', Array('jquery'));
      }
    }

The javascript, builds next and previous year buttons and adds them to the table editor page and has some code to handle query string variables.

I hope this helps, but without knowning the details of your table schema / query, its hard for me to provide specific advice.

• This reply was modified 6 years, 3 months ago by bobbysmith007.