dlsstudios

Thanks for bringing this to our attention. Currently, we are unable to reproduce on our end and need to continue investigating. We are going to release an upgraded version of Sign-up Sheets in the near future that may resolve your problem.

This is currently not editable in the plugin. However, the asterisk “*” is wrapped in a CSS class of dls-sus-required-icon. It may help your users to style that so it doesn’t match the preceding text as much or even move it to the beginning. Adding a little CSS like the example below to your theme may help…

.dls-sus-required-icon {
	float: left;
	padding-right: 0.6em;
	color: #f00;
}

If you are interested in having this be more editable within the plugin itself, please feel free to submit what you are looking for via our Request for Quote form and we can provide an estimate for adding the feature.

@venkmanuk,

The [sign_up_sheet] shortcode shouldn’t be dependent on the_content() function. However, it does require that shortcodes be processed in whatever field you are outputting. So, if you are using a custom field to display your shortcode, you may need to wrap it in do_shortcode().

For example, if you are using this for your code to output your page content…

echo get_the_field('my_custom_content');

You can try wrapping it like so…

echo do_shortcode(get_the_field('my_custom_content'));

Note that if the call to your custom field is using an echo to display the contents, you will need to change it to output as a string and manually echo so do_shortcode() can properly process it.

Please feel free to send it through out contact form on our site and just reference this URL: http://wordpress.org/support/topic/no-sign-up-form-when-i-click-to-sign-up

We have recently published a fix for this issue in v2.0.16.1.

I am also getting this error (see below with the traceback) which is being thrown when the main login form is being displayed.

Strict standards: Only variables should be assigned by reference in /path/to/wordpress/repo/wp-content/plugins/theme-my-login/modules/custom-redirection/custom-redirection.php on line 92
Call Stack
#	Time	Memory	Function	Location
1	0.0010	241176	{main}( )	../index.php:0
2	0.0015	244536	require( '/path/to/wordpress/repo/wp-blog-header.php' )	../index.php:17
3	0.3493	33468440	require_once( '/path/to/wordpress/repo/wp-includes/template-loader.php' )	../wp-blog-header.php:16
4	0.3591	33490448	include( '/path/to/wordpress/repo/wp-content/themes/my-theme/page-login.php' )	../template-loader.php:74
5	0.4631	34793200	the_content( )	../page-login.php:26
6	0.4632	34793840	apply_filters( )	../post-template.php:211
7	0.4640	34796224	call_user_func_array ( )	../plugin.php:192
8	0.4640	34796256	do_shortcode( )	../plugin.php:192
9	0.4640	34797304	preg_replace_callback ( )	../shortcodes.php:201
10	0.4640	34799024	do_shortcode_tag( )	../shortcodes.php:201
11	0.4641	34799312	call_user_func ( )	../shortcodes.php:287
12	0.4641	34799400	Theme_My_Login->shortcode( )	../shortcodes.php:287
13	0.4643	34800240	Theme_My_Login_Template->display( )	../class-theme-my-login.php:767
14	0.4643	34817616	Theme_My_Login_Template->get_template( )	../class-theme-my-login-template.php:125
15	0.4655	34836360	include( '/path/to/wordpress/repo/wp-content/plugins/theme-my-login/templates/login-form.php' )	../class-theme-my-login-template.php:481
16	0.4665	34837816	do_action( )	../login-form.php:20
17	0.4665	34839312	call_user_func_array ( )	../plugin.php:470
18	0.4665	34839392	Theme_My_Login_Custom_Redirection->login_form( )	../plugin.php:470

The error disappears when I remove the ampersand in line 92 in the plugin file/modules/custom-redirection/custom-redirection.php. I changed…

$template =& Theme_My_Login::get_object()->get_active_instance();

to

$template = Theme_My_Login::get_object()->get_active_instance();

We haven’t been able to reproduce this error yet on our end. Can you please try deactivating your other plugins one by one to determine if there is a conflict with a specific plugin?

If that solves it, please let us know which plugin it is and we can see if we can resolve it on our end.