qstudio

Hey, sorry for the delay – I’m going to take a look at this and fix it up shortly.

Q

@cwjordan – thanks for your reply.

Please take deeper look at the code, multiple reports are still supported – and I feel it’s more likely that different users will want to run their own exports, at least that’s the common usage on a large site I use this on.

I keep the same logic you had in terms of saving, loading and deleting reports ( I called them exports ) – but I switched the code around a bit and added some more validation and error checking.

The exports are still saved in one large array, with named keys, the name the user gives them at the time of saving.

I’ll add that missing css to github in a minute.

Cheers

Q

I thought I’d drop this note in this topic also, as this includes a fix for the offset issue:

—————-

First push of 0.9.6 is up on github for testing:

https://github.com/qstudio/export-user-data

There are a few bits missing and a few changes, mostly to the saving of previous export data:

– I moved this from the wp_options table to the wp_usermeta – this will allow several users to store data on the same install
– I moved some of the saving and retrieving options around in the layout and reformatted the methods a little, to match the rest of the plugin
– I had to comment out the array data sanitizing lines for now, noted with an @todo – @cwjordan, please can you take a look at this, as it’s including the saved array as a key within itself?

I tested a 1500 member export and all the saving and loading functions, but most testing is required before this goes up on WP.

Any questions, just ask.

Q

Ok – first push is up:

https://github.com/qstudio/export-user-data

There are a few bits missing and a few changes, mostly to the saving of previous export data:

– I moved this from the wp_options table to the wp_usermeta – this will allow several users to store data on the same install
– I moved some of the saving and retrieving options around in the layout and reformatted the methods a little, to match the rest of the plugin
– I had to comment out the array data sanitizing lines for now, noted with an @todo – @cwjordan, please can you take a look at this, as it’s including the saved array as a key within itself?

I tested a 1500 member export and all the saving and loading functions, but most testing is required before this goes up on WP.

Any questions, just ask.

Q

@grexican – all makes good sense – thanks, I’m reading over all the new options, tidying up and testing things – I might push an update onto git later today – if you’d all be up for testing from there?

Cheers

Q

@cwjordan – thanks for looking into this – I often find the BP documentation a bit sparse, so we have to chase functions calls up the chain to find out how they relate to one another.

Seems a shame that we can’t by-pass the cache-creation programmatically – but I certainly agree that we should stick to using provided top-level functions and avoid custom SQL, it’s always inadvisable.

I’ll take a look at everything you’ve been working on at the weekend.

Thanks!

Q

Thanks @cwjordan – seems like a stack of changes and updates to review – I’ll try to make time as soon as possible.

Q