bccampus / excel-export Goto Github PK

Migrate to its direct successor PhpSpreadsheet. This will break compatibility to dramatically improve the code base quality (namespaces, PSR compliance, use of latest PHP language features, etc.).

When submitting the form for both the export users and export post buttons.

Stay DRY in creating an export function that gets the export data requested in the options screen.

• Options page added in admin. Located in Settings->Excel Export.

• Now supports exporting any post type. It will find all available post types on your website for export. (labels aren't quite right yet, but the data is there)

• Exports all user data, and is now unserialized for readability. (BuddyPress user data is almost there, working on it)

• Update the screenshot

Create the column labels based on the data, map them to correct columns, and add the document properties.

Let's take a look at the export feature from a FIPPA and GDPR perspective.

Currently only the get_user_meta() values and labels are exported. Export the get_userdata() Fields and Values as well. May require Typecasting the WP_User object to convert into an associative array, and then combine that array with the one that's currently used for export.

Add options Screen to allow users to choose what data to export to excel:

• Pages
• Post
• Custom post types
• Users

Exporting users extended buddy press field data will fail on a site that doesn't have this filter and associated data which is in the EYPD theme functions file.

The following lines use array_combine which return FALSE without the above fields/data:

Export of user data not working as expected after recent changes, there are duplicate values and extra columns.

Currently providing a $key argument on get_user_meta() to extract specific data. Leaving the $key argument blank retrieves all meta data for the given user. We can then use array_map() on the results of get_user_meta() in order to take only the first index of each result, and then Filter out empty values by using array_filter() on the results of the array_map().

Currently using Complex (curly) syntax manually to allow for the use of complex expressions when object properties include an unexpected character. Example: $presenter = $post->{'Presenter(s)'}; A better approach to automate this might be sanitizing the object properties.

Check for Buddy Press, and if it exists, use bp_get_profile_field_data() or similar to get the extended profile data for the user (fields and values), and add this to the export array.

Currently exports the raw values, for example the value of wp_capabilities is exported as a:2:{s:13:"administrator";b:1;s:13:"bbp_keymaster";b:1;}