Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
User Registration | Event Espresso - Staging Server

Support

Home Forums Roles & Permissions User Registration

User Registration

Posted: December 13, 2012 at 10:11 am

Viewing 4 reply threads


Dennis Massimo

December 13, 2012 at 10:11 am

Today I tried to register a new user to be an event manager.

When I first registered the member I received these errors:

> Warning: Missing argument 2 for wpdb::prepare(), called in
> /home/content/15/9901015/html/wp-content/plugins/espresso-permissions-pro/espresso-permissions-pro.php on line 356 and defined in
> /home/content/15/9901015/html/wp-includes/wp-db.php on line 990
>
> Warning: MailChimp listSubscribe() Error: 104 – API Key can not be
> blank in
> /home/content/15/9901015/html/wp-content/plugins/mailchimp-sync/mailchimp-sync.php
> on line 106
>
> Warning: MailChimp listSubscribe() Error: 104 – API Key can not be
> blank in
> /home/content/15/9901015/html/wp-content/plugins/mailchimp-sync/mailchimp-sync.php
> on line 106
>
> Warning: Cannot modify header information – headers already sent by
> (output started at
> /home/content/15/9901015/html/wp-includes/wp-db.php:990) in
> /home/content/15/9901015/html/wp-includes/pluggable.php on line 876

It did however register the user. When I tried to change that user’s info in the backend I received these errors:

Warning: Missing argument 2 for wpdb::prepare(), called in /home/content/15/9901015/html/wp-content/plugins/espresso-permissions-pro/espresso-permissions-pro.php on line 356 and defined in /home/content/15/9901015/html/wp-includes/wp-db.php on line 990

Warning: MailChimp listSubscribe() Error: 104 – API Key can not be blank in /home/content/15/9901015/html/wp-content/plugins/mailchimp-sync/mailchimp-sync.php on line 106

> Warning: MailChimp listSubscribe() Error: 104 – API Key can not be
> blank in
> /home/content/15/9901015/html/wp-content/plugins/mailchimp-sync/mailchimp-sync.php
> on line 106
>
> Warning: Cannot modify header information – headers already sent by
> (output started at
> /home/content/15/9901015/html/wp-includes/wp-db.php:990) in
> /home/content/15/9901015/html/wp-includes/pluggable.php on line 876

Any help? This stuff is way over my head.

Thank you.

Justin


Josh

December 13, 2012 at 1:10 pm

Hi there,

The error messages indicate that you have error_display set to On, which should only be the case if your site is under development.

Usually error_display is set to ON for a server that is set up for development, with the understanding that when the site goes live, error_display will be disabled.

It’s not recommended or secure to display errors on a live site. Otherwise server info will display on public facing pages if any errors get thrown. So it’s recommend to log errors on a live site, not display them.

It may be possible to override the error display setting in php.ini by adding this line to the wp-config.php file above any require_once or include commands:

@ini_set(‘display_errors’,’Off’);

http://codex.wordpress.org/Editing_wp-config.php#Configure_Error_Log

On of the errors that you’re getting indicate that the MailChimp add-on has been activated, but no API key has been set. You can deactivate the Mailchimp add-on -or- enter an API key.

The errors with the Permissions add-on are coming up because of the changes in WP 3.5 that we haven’t been able to address yet in the Roles and permissions add-on. The warnings are basically saying “You need one more parameter here if you want to use this function” So in the next version of R&P, there will be one more parameter in that function.


Josh

December 13, 2012 at 1:15 pm

Update:

Do you have the current version of Permissions Pro active? (The version number is 2.0.5)


Dennis Massimo

December 13, 2012 at 3:24 pm

I do have permissions pro active. That is the version number (2.0.5).

Also, I followed the link you provided and inserted the code. No more error messages.


Seth Shoultes

  • Support Staff

December 14, 2012 at 11:13 am

@Josh I created an internal bug ticket for the Permissions Pro.


@Dennis
this error:
Warning: MailChimp listSubscribe() Error: 104 – API Key can not be blank in /home/content/15/9901015/html/wp-content/plugins/mailchimp-sync/mailchimp-sync.php on line 106

This is happening because your Mailchimp API Key is blank.

Viewing 4 reply threads

The support post ‘User Registration’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Event Espresso - Staging Server