- This topic has 17 replies, 2 voices, and was last updated 3 years, 2 months ago by
.
-
Posts
-
Hi,
On every page there are multiple PHP notices:
[02-Feb-2022 22:04:44 UTC] PHP Notice: Kirki_Field::set_output was called <strong>incorrectly</strong>. "output" invalid format in field navigation_sub_menu_border_color. The "output" argument should be defined as an array of arrays. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.0.10.) in /asite/wp-includes/functions.php on line 5768 [02-Feb-2022 22:04:44 UTC] PHP Stack trace: [02-Feb-2022 22:04:44 UTC] PHP 1. {main}() /asite/wp-admin/admin-ajax.php:0 [02-Feb-2022 22:04:44 UTC] PHP 2. require_once() /asite/wp-admin/admin-ajax.php:22 [02-Feb-2022 22:04:44 UTC] PHP 3. require_once() /asite/wp-load.php:50 [02-Feb-2022 22:04:44 UTC] PHP 4. require_once() /asite/wp-config.php:98 [02-Feb-2022 22:04:44 UTC] PHP 5. do_action() /asite/wp-settings.php:565 [02-Feb-2022 22:04:44 UTC] PHP 6. WP_Hook->do_action() /asite/wp-includes/plugin.php:474 [02-Feb-2022 22:04:44 UTC] PHP 7. WP_Hook->apply_filters() /asite/wp-includes/class-wp-hook.php:331 [02-Feb-2022 22:04:44 UTC] PHP 8. Grimlock_Navigation_Customizer->add_customizer_fields() /asite/wp-includes/class-wp-hook.php:307 [02-Feb-2022 22:04:44 UTC] PHP 9. Grimlock_Navigation_Customizer->add_sub_menu_border_color_field() /asite/wp-content/plugins/grimlock/inc/customizer/class-grimlock-navigation-customizer.php:243 [02-Feb-2022 22:04:44 UTC] PHP 10. Kirki::add_field() /asite/wp-content/plugins/grimlock/inc/customizer/class-grimlock-navigation-customizer.php:884 [02-Feb-2022 22:04:44 UTC] PHP 11. Kirki_Field_Color->__construct() /asite/wp-content/plugins/kirki/core/class-kirki.php:250 [02-Feb-2022 22:04:44 UTC] PHP 12. Kirki_Field_Color->set_field() /asite/wp-content/plugins/kirki/core/class-kirki-field.php:296 [02-Feb-2022 22:04:44 UTC] PHP 13. Kirki_Field_Color->set_output() /asite/wp-content/plugins/kirki/core/class-kirki-field.php:319 [02-Feb-2022 22:04:44 UTC] PHP 14. _doing_it_wrong() /asite/wp-content/plugins/kirki/core/class-kirki-field.php:509 [02-Feb-2022 22:04:44 UTC] PHP 15. trigger_error() /asite/wp-includes/functions.php:5768 [02-Feb-2022 22:04:44 UTC] PHP Notice: Kirki_Field::set_output was called <strong>incorrectly</strong>. "output" invalid format in field navigation_sub_menu_border_color. The "output" argument should be defined as an array of arrays. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.0.10.) in /asite/wp-includes/functions.php on line 5768 ### wp-parent-theme ### name: Cera (cera) version: 1.1.12 author: Themosaurus author_website: https://www.themosaurus.com theme_path: /Users/sam/Sites/fairsound/wp-content/themes/cera auto_update: Disabled ### wp-plugins-active (25) ### BuddyPress: version: 9.1.1, author: The BuddyPress Community (latest version: 10.0.0), Auto-updates disabled Grimlock: version: 1.4.6, author: Themosaurus, Auto-updates disabled Grimlock Animate: version: 1.1.8, author: Themosaurus, Auto-updates disabled Grimlock for BuddyPress: version: 1.4.6, author: Themosaurus, Auto-updates disabled Grimlock Login: version: 1.1.7, author: Themosaurus, Auto-updates disabled Kirki Customizer Framework: version: 3.1.9, author: David Vongries, Auto-updates disabled
Hi Sam,
Thank you for your precious feedback. 🙏🏼 There is definitely an issue in our theme which will be fixed in the next update.
Be aware that these are PHP warnings, not errors. Unlike errors, warnings won’t break your website. They’re just messages aimed at developers to improve their code.
To hide this message, I suggest that you activate error logging on your website. Please keep WP_DEBUG to true and just paste the following code lines in your wp-config.php file, just before the line that says ‘That’s all, stop editing! Happy blogging.’:
// Enable WP_DEBUG mode define( 'WP_DEBUG', true ); // Enable Debug logging to the /wp-content/debug.log file define( 'WP_DEBUG_LOG', true ); // Disable display of errors and warnings define( 'WP_DEBUG_DISPLAY', false ); @ini_set( 'display_errors', 0 );More on this in the following topic: Debugging in WordPress
You will still be able to consult the warnings and errors triggered by your website but these won’t appear on your pages anymore.
We’ll be back to you as soon as the update is available.
Thank you for your patience.
Regards,
Thanks.
The problem is I am constantly watching the debug log as I am developing and these kind of errors make it hard to spot errors in my code versus other plugins 🙂
So for anyone else finding this topic, I use this to stop this error polluting the log file:
add_filter( 'doing_it_wrong_trigger_error', function ( $trigger, $function ) { if ( ! $trigger ) { return $trigger; } $disable = [ 'Kirki_Field::set_output' ]; return ! in_array( $function, $disable ); }, 10, 2 );Also, are you aware your forum has issues notifying of replies? i.e. I no longer receive any emails when someone responds.
Hi Sam,
Thank you for sharing the solution with us. I’m sure it will help other users facing the same issue! By doing this, you’re making a great contribution to this forum, and we thank you very much for that! #SharingIsCaring 💪🏻
Thank you for reporting this to us. Concerning the notifications, we checked and it seems all emails are well send. Did you checked your spam folder?
Best,
I have checked my Spam folder, it is not there.
Is it normal to have no email settings in my profile settings?
This reply has been marked as private.
Not sure if this error is related?
[08-Feb-2022 00:06:00 UTC] PHP Notice: Kirki\Module\CSS::field_init was called <strong>incorrectly</strong>. "output" invalid format in field . The "output" argument should be defined as an array of arrays. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.0.10.) in /example/wp-includes/functions.php on line 5768 [08-Feb-2022 00:06:00 UTC] PHP Stack trace: [08-Feb-2022 00:06:00 UTC] PHP 1. {main}() /example/index.php:0 [08-Feb-2022 00:06:00 UTC] PHP 2. require() /example/index.php:17 [08-Feb-2022 00:06:00 UTC] PHP 3. require_once() /example/wp-blog-header.php:13 [08-Feb-2022 00:06:00 UTC] PHP 4. require_once() /example/wp-load.php:50 [08-Feb-2022 00:06:00 UTC] PHP 5. require_once() /example/wp-config.php:98 [08-Feb-2022 00:06:00 UTC] PHP 6. do_action() /example/wp-settings.php:609 [08-Feb-2022 00:06:00 UTC] PHP 7. WP_Hook->do_action() /example/wp-includes/plugin.php:474 [08-Feb-2022 00:06:00 UTC] PHP 8. WP_Hook->apply_filters() /example/wp-includes/class-wp-hook.php:331 [08-Feb-2022 00:06:00 UTC] PHP 9. Kirki\Field\Color->Kirki\{closure:/example/wp-content/plugins/kirki/packages/kirki-framework/field/src/Field.php:92-94}() /example/wp-includes/class-wp-hook.php:307 [08-Feb-2022 00:06:00 UTC] PHP 10. do_action() /example/wp-content/plugins/kirki/packages/kirki-framework/field/src/Field.php:93 [08-Feb-2022 00:06:00 UTC] PHP 11. WP_Hook->do_action() /example/wp-includes/plugin.php:474 [08-Feb-2022 00:06:00 UTC] PHP 12. WP_Hook->apply_filters() /example/wp-includes/class-wp-hook.php:331 [08-Feb-2022 00:06:00 UTC] PHP 13. Kirki\Module\CSS->field_init() /example/wp-includes/class-wp-hook.php:307 [08-Feb-2022 00:06:00 UTC] PHP 14. _doing_it_wrong() /example/wp-content/plugins/kirki/packages/kirki-framework/module-css/src/CSS.php:133 [08-Feb-2022 00:06:00 UTC] PHP 15. trigger_error() /example/wp-includes/functions.php:5768
Hi Sam,
Popular email clients like Gmail, Yahoo, Office 365 are in a constant battle with email spammers. One of the things they look at is if an email is originating from the location it claims to be originating from. If the proper authentication isn’t there, then emails either go in the SPAM folder or worst, don’t get delivered at all, like it seems it is the case for you.
Our mail are well being send, but we just added an authentification that should now allow you to receive these emails. Can you please tell us if you received the email notification concerning this reply? If not, can you please make sure to subscribe to this topic?
Concerning the emails settings: All is set by default. You should receive the emails for new replies in the topics you created and new replies to topics you subscribed. This is why there is no setting.
Note that the PHP notices mentioned above won’t break your website. It is just a message aimed at developers to improve their code. You can hide this message by activating error logging on your website using the php snippet in one of my previous reply.
Best,
I still did not receive the reply, I am subscribed to the topic.
Regarding the PHP notice, I have traced the issue to this line:
plugins/grimlock/inc/customizer/class-grimlock-navigation-customizer.php:867It should be:
‘output’ => [ $this->get_css_var_output( ‘navigation_sub_menu_border_color’ ) ],Thanks for your response, I understand in this instance it does not break my websites but it does indicate a bug which is why I’m reporting it.
Hi Sam,
The authentication we added to emails should have solved this problem. 🤔 We’ll investigate further to find out if there is anything else we could do. I’m afraid that I don’t have any solution at the moment.
Thank you for these specifications. You’re right, don’t hesitate to share these kind of notices! I transmitted these specifications to our developers team.
Thank you for contributing to this theme! 🙏🏼
Best,
Please be aware that we have just released a new update of Grimlock. Updating this plugin to the latest version should fix this notice.
After the update, the problem should now be fixed. However, you might still be seeing the issue because your browser cache is showing you an older version of the page (browsers do that to load pages faster). To see that the issue is resolved you will need to empty your browser cache and reload the page. If you want to read more on what browser cache is and how to clear it, here is an article that might help you: How to Clear Internet Cache in Every Major Browser.
Kindest regards,
This reply has been marked as private.
This reply has been marked as private.
I’m sorry Sam, I’m afraid there’s nothing more we could do.
I suggest you contact your web host to check if there is a security option that would prevent you from receiving our emails.
Best,
Thanks for trying, it’s setup in Google Workplace so we don’t have any issues elsewhere.
I’m sorry we couldn’t help you more with that Sam. Be sure we did all we could. 🤔
Hi,
A similar issue but this time in the Grimlock Login v1.1.10 plugin. Would you like me to open a new topic?
[08-Mar-2022 04:21:17 UTC] PHP Notice: Undefined index: font-weight in /sites/example/wp-content/plugins/grimlock-login/inc/class-grimlock-login.php on line 181 [08-Mar-2022 04:21:17 UTC] PHP Stack trace: [08-Mar-2022 04:21:17 UTC] PHP 1. {main}() /sites/example/wp-login.php:0 [08-Mar-2022 04:21:17 UTC] PHP 2. login_header() /sites/example/wp-login.php:1371 [08-Mar-2022 04:21:17 UTC] PHP 3. do_action() /sites/example/wp-login.php:114 [08-Mar-2022 04:21:17 UTC] PHP 4. WP_Hook->do_action() /sites/example/wp-includes/plugin.php:474 [08-Mar-2022 04:21:17 UTC] PHP 5. WP_Hook->apply_filters() /sites/example/wp-includes/class-wp-hook.php:331 [08-Mar-2022 04:21:17 UTC] PHP 6. Grimlock_Login->login_enqueue_styles() /sites/example/wp-includes/class-wp-hook.php:307 [08-Mar-2022 04:21:17 UTC] PHP 7. Grimlock_Login->get_google_fonts_url() /sites/example/wp-content/plugins/grimlock-login/inc/class-grimlock-login.php:75 [08-Mar-2022 04:21:17 UTC] PHP Notice: Undefined index: font-size in /sites/example/wp-content/plugins/grimlock-login/inc/customizer/class-grimlock-login-typography-customizer.php on line 49 [08-Mar-2022 04:21:17 UTC] PHP Stack trace: [08-Mar-2022 04:21:17 UTC] PHP 1. {main}() /sites/example/wp-login.php:0 [08-Mar-2022 04:21:17 UTC] PHP 2. login_header() /sites/example/wp-login.php:1371 [08-Mar-2022 04:21:17 UTC] PHP 3. do_action() /sites/example/wp-login.php:114 [08-Mar-2022 04:21:17 UTC] PHP 4. WP_Hook->do_action() /sites/example/wp-includes/plugin.php:474 [08-Mar-2022 04:21:17 UTC] PHP 5. WP_Hook->apply_filters() /sites/example/wp-includes/class-wp-hook.php:331 [08-Mar-2022 04:21:17 UTC] PHP 6. Grimlock_Login_Typography_Customizer->enqueue_styles() /sites/example/wp-includes/class-wp-hook.php:307 [08-Mar-2022 04:21:17 UTC] PHP Notice: Undefined index: letter-spacing in /sites/example/wp-content/plugins/grimlock-login/inc/customizer/class-grimlock-login-typography-customizer.php on line 51 [08-Mar-2022 04:21:17 UTC] PHP Stack trace: [08-Mar-2022 04:21:17 UTC] PHP 1. {main}() /sites/example/wp-login.php:0 [08-Mar-2022 04:21:17 UTC] PHP 2. login_header() /sites/example/wp-login.php:1371 [08-Mar-2022 04:21:17 UTC] PHP 3. do_action() /sites/example/wp-login.php:114 [08-Mar-2022 04:21:17 UTC] PHP 4. WP_Hook->do_action() /sites/example/wp-includes/plugin.php:474 [08-Mar-2022 04:21:17 UTC] PHP 5. WP_Hook->apply_filters() /sites/example/wp-includes/class-wp-hook.php:331 [08-Mar-2022 04:21:17 UTC] PHP 6. Grimlock_Login_Typography_Customizer->enqueue_styles() /sites/example/wp-includes/class-wp-hook.php:307 [08-Mar-2022 04:21:17 UTC] PHP Notice: Undefined index: line-height in /sites/example/wp-content/plugins/grimlock-login/inc/customizer/class-grimlock-login-typography-customizer.php on line 52 [08-Mar-2022 04:21:17 UTC] PHP Stack trace: [08-Mar-2022 04:21:17 UTC] PHP 1. {main}() /sites/example/wp-login.php:0 [08-Mar-2022 04:21:17 UTC] PHP 2. login_header() /sites/example/wp-login.php:1371 [08-Mar-2022 04:21:17 UTC] PHP 3. do_action() /sites/example/wp-login.php:114 [08-Mar-2022 04:21:17 UTC] PHP 4. WP_Hook->do_action() /sites/example/wp-includes/plugin.php:474 [08-Mar-2022 04:21:17 UTC] PHP 5. WP_Hook->apply_filters() /sites/example/wp-includes/class-wp-hook.php:331 [08-Mar-2022 04:21:17 UTC] PHP 6. Grimlock_Login_Typography_Customizer->enqueue_styles() /sites/example/wp-includes/class-wp-hook.php:307 [08-Mar-2022 04:21:17 UTC] PHP Notice: Undefined index: text-transform in /sites/example/wp-content/plugins/grimlock-login/inc/customizer/class-grimlock-login-typography-customizer.php on line 53 [08-Mar-2022 04:21:17 UTC] PHP Stack trace: [08-Mar-2022 04:21:17 UTC] PHP 1. {main}() /sites/example/wp-login.php:0 [08-Mar-2022 04:21:17 UTC] PHP 2. login_header() /sites/example/wp-login.php:1371 [08-Mar-2022 04:21:17 UTC] PHP 3. do_action() /sites/example/wp-login.php:114 [08-Mar-2022 04:21:17 UTC] PHP 4. WP_Hook->do_action() /sites/example/wp-includes/plugin.php:474 [08-Mar-2022 04:21:17 UTC] PHP 5. WP_Hook->apply_filters() /sites/example/wp-includes/class-wp-hook.php:331 [08-Mar-2022 04:21:17 UTC] PHP 6. Grimlock_Login_Typography_Customizer->enqueue_styles() /sites/example/wp-includes/class-wp-hook.php:307 [08-Mar-2022 04:21:17 UTC] PHP Notice: Undefined index: font-size in /sites/example/wp-content/plugins/grimlock-login/inc/customizer/class-grimlock-login-typography-customizer.php on line 63 [08-Mar-2022 04:21:17 UTC] PHP Stack trace: [08-Mar-2022 04:21:17 UTC] PHP 1. {main}() /sites/example/wp-login.php:0 [08-Mar-2022 04:21:17 UTC] PHP 2. login_header() /sites/example/wp-login.php:1371 [08-Mar-2022 04:21:17 UTC] PHP 3. do_action() /sites/example/wp-login.php:114 [08-Mar-2022 04:21:17 UTC] PHP 4. WP_Hook->do_action() /sites/example/wp-includes/plugin.php:474 [08-Mar-2022 04:21:17 UTC] PHP 5. WP_Hook->apply_filters() /sites/example/wp-includes/class-wp-hook.php:331 [08-Mar-2022 04:21:17 UTC] PHP 6. Grimlock_Login_Typography_Customizer->enqueue_styles() /sites/example/wp-includes/class-wp-hook.php:307Thanks.
Hi Sam,
Thank you for bring this new issue to our attention. We’re glad to answer any question related with the setup of our theme.
However, it is very difficult for us to provide the best support possible and to keep track of issues and their resolution when multiple issues are addressed in a same topic.
Moreover, it’s easier for us to share the resolution for a single issue with other members of our community facing the same problem.So, could you move your request into a different topic, please? One question = one topic.
By doing this, you will be making a great contribution to this forum, and we thank you very much for that! 🙏🏼Thank you.
Hi there,
This topic has been inactive for a while now so we will be closing it to keep the forum tidy. Don't hesitate to create a new topic if you still need help and we'll be glad to help you!
Best regards,
The Themosaurus team.
The topic ‘PHP Notice: Kirki_Field::set_output was called incorrectly’ is closed to new replies.
