Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Export to HTML or Word? | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Export to HTML or Word?

Export to HTML or Word?

Posted: December 3, 2012 at 1:22 am

Viewing 3 reply threads


Ben Stokes

December 3, 2012 at 1:22 am

Is it possible to export events attendees and other information to HTML or Word format rather than Excel or CSV?

If so, is there any documentation on this?


Dean

  • Support Staff

    •

December 3, 2012 at 4:01 am

Hello Ben,

No, currently the only export option is to a XLS file.

You could modify the event-espresso/includes/functions/export.php file (core file, updates will over write any modifications) to change the XLS to DOC/HTML, but the output isn’t very pretty so you would need to modify the whole structure of how it is output.


Even Onsager

December 5, 2012 at 8:40 am

If you want HTML, I recommend using export to CSV, then opening it in the great freeware windows application CSVFileView, and exporting as HTML from there. It’s only one added step, but it will result in a nice HTML table with the added bonus of easily being able to hide rows or columns (a lot easier than with Excel) before the HTML creation itself. I do this every day.


Josh

December 7, 2012 at 2:23 pm

Great tip!

Thanks Even.
Viewing 3 reply threads

The support post ‘Export to HTML or Word?’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

The original Forum description...

Status: closed

Updated by Josh 12 years, 1 month ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server