This plugin is intended for developer to send data to Simperium. Followings are use cases in which this plugin might come in handy:<\/p>\n
How to use it<\/strong><\/p>\n Once this plugin is installed and activated, you can send data to Simperium in following ways:<\/p>\n The value of Before using the action hooks or helper methods, you need to supply Simperium app credentials via In addition to Sender Examples<\/strong><\/p>\n I've created sender examples plugin<\/a> that you can use as a starting point, though it will run without any customization. Currently it has following features:<\/p>\n Consumer Examples<\/strong><\/p>\n I'm working to provide listener apps, written in PHP (stay tuned!), for now you can check Simperium examples<\/a> and their awesome libraries.<\/p>\n Contributing<\/strong><\/p>\n \n
do_action( 'simperium_send_data', $bucket, $data )<\/code> or do_action( 'simperium_send_buffered_data', $bucket, $data )<\/code>. The first hook, will send the $data<\/code> immediately, while the later will send the data to buffer and will send all buffered data to Simperium at once after calling do_action( 'simperium_flush_buffer', $bucket )<\/code>. If $bucket<\/code> arg is provided, it only flushes buffered data that's targetted to $bucket<\/code>.<\/li>\nWP_Simperium::send_data( $bucket, $data )<\/code> or WP_Simperium::send_buffered_data( $bucket, $data )<\/code>. To flush buffer, you call WP_Simperium::flush_buffer( $bucket )<\/code>. Again, $bucket<\/code> arg is optional.<\/li>\n<\/ol>\n $data<\/code> MUST BE in key-value array structure as nested structure is not supported by Simperium.<\/p>\n simperium_config<\/code> filter, for example:<\/p>\n add_filter( 'simperium_config', function() { return array( 'app_id' => 'YOUR_APP_ID', 'api_key' => 'YOUR_API_KEY', ) } ); <\/code><\/pre>\n app_id<\/code> and api_key<\/code> you can pass username<\/code> and\/or access_token<\/code> to the array config. If access_token<\/code> is omitted, the plugin will request access_token<\/code> from Simperium with provided username<\/code> (if exists) or get_bloginfo( 'admin_email' )<\/code> and store the info in option. Subsequent calls will read access_token<\/code> information from option, but can be bypassed by providing access_token<\/code> in array config. It's preferred to supply your own access_token<\/code> or username<\/code> that hasn't registered yet. Please keep in mind that token has 30 days life span. If you're using access_token<\/code> that's automatically retrieved by the plugin, you don't need to worry as scheduled event will refresh the token per 29 days.<\/p>\n \n
\n
\n
wp-content\/plugins\/<\/code> directory and activate.<\/li>\nsimperium_config<\/code> filter either as drop-in plugin or in your theme's functions.php<\/code><\/li>\n<\/ol>\n\n\nDoes the plugin provides API to retrieve entity from Simperium<\/h4>\n