BirdBrain Logic

Hi creatorsdream,

Thanks for the report. We’ll look in to this ASAP and release a new version with a fix.

Should be very shortly!

Cheers.

Hi aadesh,

Currently, no. All output is handled with shortcodes. You can use the do_shortcode function to display shortcodes wherever you like in templates, though.

EG
<?php echo do_shortcode('[contact type="phone_number"]'); ?>

This will achieve the same effect.

Hi yananym,

You can use the shortcodes below to display email addresses

[contact type="email_address"]
[contact type="email_address_2"]

They can be found under the “Address 1” and “Address 2” sections under Settings -> Contact Details.

Thanks!

We are considering dropping different languages in to the plugin, but unfortunately it will not be for a short while.

You are more than welcome to make the translations in the source code, but of course, when a new version is released, those changes will be overwritten.

If you experience any further difficulty, please let us know.

Hi parterreblog,

Version 1.2.4 will be released momentarily which addresses the bug of contact details not saving correctly in WordPress 3.8

Regarding the shortcodes not working in your widgets, that is not a fault of the plugin. That is completely dependent on the theme you’re using and plugins should not alter this behaviour. To enable the use of shortcodes in Text Widgets, add the following code to your functions.php file

add_filter('widget_text', 'do_shortcode');

This will enable Text Widgets in your theme to process shortcodes.

If you experience any more difficulty, please let us know.

Given this new information, if you would like to take the time to alter your 1 star rating, that would be very much appreciated.

Thank you.

Hi parterreblog,

Contact Details has not been updated in a little while and is only officially compatible up to WordPress 3.6.1

We will be reviewing the plugin shortly and ensure it is bought up to date with WordPress 3.8.1

Hello swimflyfast,

Thanks for your feedback! We have just released an update which should resolve this issue for you.

Please update to version 1.1 at your convenience.

Let us know if you experience any more issues or have any further feedback.