nicola.bavaro

Location Module for Contact Form 7 is an “Contact Form 7” extension to let users search their location, adjust and send it. It displays an address form and a map (using Google Maps). The user can set their address and locate it on the Map by pressing “Set” button. Is possible to drag and drop the marker to adjust the location. Using: cf7-location-lng’,’cf7-location-lat’ and ‘cf7-location-url’ tags is possible to send in the email the coordinates and the location link set by the user.
<h4>Required Plugins</h4>
The following plugins are required for Location Module (lite) for Contact Form 7 users:
<ul>
<li><a href="https://wordpress.org/plugins/contact-form-7/" rel="ugc">Contact Form 7</a> by Takayuki Miyoshi – Contact Form 7 can manage multiple contact forms, plus you can customize the form and the mail contents flexibly with simple markup.</li>
</ul>
<h4>This Plugin Needs Your Support</h4>
It is hard to continue development and support for this free plugin without contributions from users like you. If you enjoy using Contact Form 7 Location Module and find it useful, please consider <a href="http://www.nicolabavaro.it/donate/" rel="nofollow ugc">making a donation</a>. Your donation will help encourage and support the plugin’s continued development.
<h3>Credits</h3>
Thanks to GMaps.js v0.4.25 https://github.com/hpneo/gmaps

Location Module (Lite) for Contact Form 7

Just another Contact Form 7 Extension. Let users send their location.

Thorsten Frommen

Use the new Text Modules custom post type and display a text module by either shortcode or widget.
Have you ever wanted to use some pieces of text information more than once? For instance, contact information such as a postal address? Or some slogan, motto or claim?
This is exactly when Text Modules kicks in.
<h4>Usage</h4>
This plugin registers a simple post type for text modules. A text module can be accessed either via shortcode (by means of the text module’s ID or slug) or via a new Tex Modules widget.
Filters
In order to customize certain aspects of the plugin, it provides you with several filters. For each of these, a short description as well as a code example on how to alter the default behavior is given below. Just put the according code snippet in your theme’s <code>functions.php</code> file or your customization plugin, or to some other appropriate place.
<code>text_modules_after_widget_content</code>
This filter lets you alter the HTML after the widget content.
<pre><code>/**
 * Filter the HTML after the widget content.
 *
 * @param string $after_widget_content Some HTML after the widget content.
 */
add_filter( 'text_modules_after_widget_content', function() {

 return '';
} );
</code></pre>
<code>text_modules_before_widget_content</code>
This filter lets you alter the HTML before the widget content.
<pre><code>/**
 * Filter the HTML before the widget content.
 *
 * @param string $before_widget_content Some HTML before the widget content.
 */
add_filter( 'text_modules_before_widget_content', function() {

 return '';
} );
</code></pre>
<code>text_modules_post_type</code>
Yes, you can alter the post type (slug).
<pre><code>/**
 * Filter the post type.
 *
 * @param string $post_type Post type.
 */
add_filter( 'text_modules_post_type', function() {

 return 'exotic_stuff';
} );
</code></pre>
<code>text_modules_post_type_args</code>
If you want to alter a specific post type argument but you can’t find a fitting filter, there’s <code>text_modules_post_type_args</code>, which provides you with the complete args array.
<pre><code>/**
 * Filter the post type args.
 *
 * @param array $args Post type args.
 */
add_filter( 'text_modules_post_type_args', function( $args ) {

 // Use hierarchical external content
 $args[ 'hierarchical' ] = TRUE;

 return $args;
} );
</code></pre>
<code>text_modules_post_type_description</code>
The post type description can be customized by using the <code>text_modules_post_type_description</code> filter.
<pre><code>/**
 * Filter the post type description.
 *
 * @param string $description Post type description.
 */
add_filter( 'text_modules_post_type_description', function() {

 // Provide a description
 return 'Simple post type for text modules.';
} );
</code></pre>
<code>text_modules_post_type_labels</code>
In case you don’t like the labels, easily adapt them to your liking.
<pre><code>/**
 * Filter the post type labels.
 *
 * @param array $labels Post type labels.
 */
add_filter( 'text_modules_post_type_labels', function( $labels ) {

 // A little more horror, please...
 $labels[ 'not_found' ] = 'ZOMG, no text module found!!1!!1!!oneone!!!1!eleven!1!';

 return $labels;
} );
</code></pre>
<code>text_modules_post_type_supports</code>
This filter provides you with the post type supports.
<pre><code>/**
 * Filter the post type supports.
 *
 * @param array $supports Post type supports.
 */
add_filter( 'text_modules_post_type_supports', function( $supports ) {

 // Let's add revisions for our post type
 if ( ! in_array( 'revisions', $supports ) ) {
 $supports[] = 'revisions';
 }

 return $supports;
} );
</code></pre>
<code>text_modules_shortcode_apply_do_shortcode</code>
By default, do_shortcode() will be called on the shortcode output. Of course, you can change that.
<pre><code>/**
 * Filter if the shortcode should apply do_shortcode() to the output.
 *
 * @param bool $do_shortcode Should the shortcode apply do_shortcode()?
 */
add_filter( 'text_modules_shortcode_apply_do_shortcode', '__return_false' );
</code></pre>
<code>text_modules_shortcode_callback</code>
In case you would like to adapt how the shortcode data is handled, you can provide your own shortcode callback. This can either be a string holding the function name, or an array with either a class name or an object, and the according method.
<pre><code>/**
 * Filter the shortcode callback.
 *
 * @param array|string $callback Shortcode callback.
 */
add_filter( 'text_modules_shortcode_callback', function() {

 return 'my_text_modules_shortcode_callback';
} );
</code></pre>
<code>text_modules_shortcode_id_attribute_name</code>
This filter lets you alter the shortcode’s ‘id’ attribute name.
<pre><code>/**
 * Filter the 'id' shortcode attribute name.
 *
 * @param string $name Attribute name.
 */
add_filter( 'text_modules_shortcode_id_attribute_name', function() {

 return 'post_id';
} );
</code></pre>
<code>text_modules_shortcode_output</code>
This filter lets you alter the shortcode output. The second parameter holds the shortcode attributes array.
<pre><code>/**
 * Filter the shortcode output.
 *
 * @param string $output Shortcode output.
 * @param array $atts Shortcode attributes array.
 */
add_filter( 'text_modules_shortcode_output', function( $output ) {

 return $output . ' Over and out.';
} );
</code></pre>
<code>text_modules_shortcode_query_args</code>
Also, there’s <code>text_modules_shortcode_query_args</code>, which provides you with the complete args array for the shortcode’s query.
<pre><code>/**
 * Filter the shortcode query args.
 *
 * @param array $args Shortcode query args.
 */
add_filter( 'text_modules_shortcode_query_args', function( $args ) {

 // Exclude some text modules by ID
 $args[ 'post__not_in' ] = array( 4, 8, 15, 16, 23, 42 );

 return $args;
} );
</code></pre>
<code>text_modules_shortcode_slug_attribute_name</code>
This filter lets you alter the shortcode’s ‘slug’ attribute name.
<pre><code>/**
 * Filter the 'slug' shortcode attribute name.
 *
 * @param string $name Attribute name.
 */
add_filter( 'text_modules_shortcode_slug_attribute_name', function() {

 return 'post_slug';
} );
</code></pre>
<code>text_modules_shortcode_tag</code>
This filter lets you alter the shortcode’s tag.
<pre><code>/**
 * Filter the shortcode tag.
 *
 * @param string $shortcode_tag Shortcode tag.
 */
add_filter( 'text_modules_shortcode_tag', function() {

 return 'text_block';
} );
</code></pre>
<code>text_modules_shortcode_use_slug</code>
By default, text modules are being queried by their post ID first. Of course, you can change that and use the post slug instead.
<pre><code>/**
 * Filter if the shortcode (query) should use the post slug instead of the post ID.
 *
 * @param bool $use_slug Use slug instead of ID?
 */
add_filter( 'text_modules_shortcode_use_slug', '__return_true' );
</code></pre>
<code>text_modules_widget_form_query_args</code>
Also, there’s <code>text_modules_widget_form_query_args</code>, which provides you with the complete args array for the widget form’s query.
<pre><code>/**
 * Filter the widget form query args.
 *
 * @param array $args Query args.
 */
add_filter( 'text_modules_widget_form_query_args', function( $args ) {

 // Exclude some text modules by ID
 $args[ 'post__not_in' ] = array( 4, 8, 15, 16, 23, 42 );

 return $args;
} );
</code></pre>
<h4>Contribution</h4>
To contribute to this plugin, please see its <a href="https://github.com/tfrommen/text-modules" rel="nofollow ugc">GitHub repository</a>.
If you have a feature request, or if you have developed the feature already, please feel free to use the Issues and/or Pull Requests section.
Of course, you can also provide me with translations if you would like to use the plugin in another not yet included language.

Text Modules

Use the new Text Modules custom post type and display a text module by either shortcode or widget.

Location Module (Lite) for Contact Form 7 vs Text Modules