roundupwp

No problem! Good luck with your project.

Hey tomzwart,

All data from “Custom” fields are serialized and saved under the “custom” column in the database. You can “unserialize” it with the function “maybe_unserialize”. Here is an example using a method from the RTEC_Db class you can use to retrieve entries in the database:

if ( class_exists( 'RTEC_db' ) ) {
	$args = array(
		// retrieve the "custom" column, can also add first_name, last_name, etc..
		'fields' => array( 'custom' ),
		// add "where" clauses, multiple will be "and" clause
		'where' => array(
			array( 'event_id', 1426, '=', 'int' )
		),
		// column to order by
		'order_by' => 'registration_date'
	);
	$rtec = RTEC();
	$entries = $rtec->db_frontend->retrieve_entries( $args );

	if ( isset( $entries[0] ) ) {
		// loop through results
		foreach ( $entries as $entry ) {
			// unserialize the custom column results
			$custom = maybe_unserialize( $entry['custom'] );

			echo '<p>' . $custom['custom1']['value'] . '</p>';
			echo '<p>' . $custom['custom2']['value'] . '</p>';
		}
	}

}

You would loop through the results and unserialize the “custom” column. This will create a multidimensional array you can use to get the data you need by first using the key “custom” followed by which custom field it is (1 or 2 in the example) and then accessing the value through the sub array with the key “value”. See the example above $custom[‘custom1’][‘value’].

Hopefully this helps! This is not very friendly for trying to get results based on what a person entered for the custom fields but can be used to display it easily enough.

Let me know if you have more questions.

– Craig

No problem! Glad we could get that working like you needed.

No obligation or anything but if you felt like leaving a review, it would be greatly appreciated. Otherwise if you ever need anything else, I’d be happy to help!

Thanks again,

Craig

Hey cain,

The latest release, 2.1.1, contains support for adding your own JavaScript after the form submits. To add the person’s first and last name to the top of the attendee list, add this JavaScript to the “Custom JavaScript” area on the “Form” tab:

window.rtecAfterSubmit = function() {
  var first = jQuery('.rtec-first input').val(),
      last = jQuery('.rtec-last input').val();
      jQuery('.rtec-attendee-list').first().prepend(
        '<span class="rtec-attendee"><strong>'+first+' '+last+'</strong></span>'
        );
};

Hey Tim,

No problem! I’m glad you mentioned that you had a few events on one page. I’m thinking that the lists might be out of order with this code. There is an update coming out next week. If you can wait a bit I’ll fix this in the next release and give you a new bit of code that should work perfectly.

Have a good weekend!

Hey Tim,

Support for this was just added in the last release though not documented. The look of the list, in other words it’s styling, relies on it being inside the single event view. The next update will include some styling for the attendee list to make sure it displays normally on all pages. Until then, try this shortcode setting:

attendeelist=true

In context:

[rtec-registration-form event=1531 showheader=true attendeelist=true]

If it looks odd, feel free to send me a link and I can help style it to look more normal!

– Craig

Hey sherpaderp,

Sorry for the trouble here! Everything looks normal in your form on the page you included a link for. Is there any chance you could send your “System info” from the “Support” tab and contact us on our website?

https://roundupwp.com/support/

Thanks!

Hey Maciej,

Unfortunately there currently isn’t an easy way to do this. You would need to manually add a registration for the correct event with the same information and then delete the registration for the wrong event. Taking a look at your registration form though this may take some effort.

Otherwise, you could change the “event_id” column in the database for this entry. Let me know if you would like to try this!

Sorry for no simple answer for this one. I’ll make a note to see if something can be done to make this easier in an update in the future.

– Craig