Nico Marcuz

Forum Replies Created

Viewing 15 replies - 1 through 15 (of 259 total)
1 2 3 … 16 17 18
  • Forum: Plugins
    In reply to: [Query Monitor] Error updating WordPress 6.6.2 => 6.7.1
    Thread Starter Nico Marcuz

    (@nick7766)

    1 year, 5 months ago

    Thnx John for your reply. I just hope that Automatic fixes the bug soon. Fingers crossed.

    Forum: Plugins
    In reply to: [Query Monitor] Error updating WordPress 6.6.2 => 6.7.1
    Thread Starter Nico Marcuz

    (@nick7766)

    1 year, 5 months ago

    @johnbillion Good morning John, did you see my additional post?

    Forum: Plugins
    In reply to: [Query Monitor] Error updating WordPress 6.6.2 => 6.7.1
    Thread Starter Nico Marcuz

    (@nick7766)

    1 year, 6 months ago

    Hello John,
    Thank you very much for your quick response. I have included the entire dump from the PHP error log here.

    You can see that the recording starts with Query Monitor and then alternates with the Shortcode Ultimate plugin.

    I hope that helps you/us a little.

    [29-Nov-2024 14:17:46 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the query-monitor 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 /kunden/469469_76275/webseiten/testseite.hello-world.net/wp-includes/functions.php on line 6114
    [29-Nov-2024 14:17:46 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the query-monitor 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 /kunden/469469_76275/webseiten/testseite.hello-world.net/wp-includes/functions.php on line 6114
    [29-Nov-2024 14:17:46 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the shortcodes-ultimate 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 /kunden/469469_76275/webseiten/testseite.hello-world.net/wp-includes/functions.php on line 6114
    [29-Nov-2024 14:17:47 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the shortcodes-ultimate 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 /kunden/469469_76275/webseiten/testseite.hello-world.net/wp-includes/functions.php on line 6114
    [29-Nov-2024 14:17:53 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the shortcodes-ultimate 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 /kunden/469469_76275/webseiten/testseite.hello-world.net/wp-includes/functions.php on line 6114
    [29-Nov-2024 14:17:54 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the query-monitor 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 /kunden/469469_76275/webseiten/testseite.hello-world.net/wp-includes/functions.php on line 6114
    [29-Nov-2024 14:17:54 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the query-monitor 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 /kunden/469469_76275/webseiten/testseite.hello-world.net/wp-includes/functions.php on line 6114
    [29-Nov-2024 14:17:54 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the shortcodes-ultimate 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 /kunden/469469_76275/webseiten/testseite.hello-world.net/wp-includes/functions.php on line 6114
    [29-Nov-2024 14:17:55 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the query-monitor 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 /kunden/469469_76275/webseiten/testseite.hello-world.net/wp-includes/functions.php on line 6114
    [29-Nov-2024 14:17:55 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the query-monitor 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 /kunden/469469_76275/webseiten/testseite.hello-world.net/wp-includes/functions.php on line 6114
    [29-Nov-2024 14:17:55 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the shortcodes-ultimate 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 /kunden/469469_76275/webseiten/testseite.hello-world.net/wp-includes/functions.php on line 6114
    [29-Nov-2024 14:17:56 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the query-monitor 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 /kunden/469469_76275/webseiten/testseite.hello-world.net/wp-includes/functions.php on line 6114
    [29-Nov-2024 14:17:56 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the query-monitor 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 /kunden/469469_76275/webseiten/testseite.hello-world.net/wp-includes/functions.php on line 6114
    [29-Nov-2024 14:17:56 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the shortcodes-ultimate 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 /kunden/469469_76275/webseiten/testseite.hello-world.net/wp-includes/functions.php on line 6114
    [29-Nov-2024 14:18:23 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the query-monitor 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 /kunden/469469_76275/webseiten/testseite.hello-world.net/wp-includes/functions.php on line 6114
    [29-Nov-2024 14:18:23 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the query-monitor 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 /kunden/469469_76275/webseiten/testseite.hello-world.net/wp-includes/functions.php on line 6114
    [29-Nov-2024 14:18:23 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the shortcodes-ultimate 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 /kunden/469469_76275/webseiten/testseite.hello-world.net/wp-includes/functions.php on line 6114
    [29-Nov-2024 14:18:24 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the shortcodes-ultimate 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 /kunden/469469_76275/webseiten/testseite.hello-world.net/wp-includes/functions.php on line 6114
    [29-Nov-2024 14:18:24 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the query-monitor 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 /kunden/469469_76275/webseiten/testseite.hello-world.net/wp-includes/functions.php on line 6114
    [29-Nov-2024 14:18:24 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the query-monitor 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 /kunden/469469_76275/webseiten/testseite.hello-world.net/wp-includes/functions.php on line 6114
    [29-Nov-2024 14:18:24 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the shortcodes-ultimate 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 /kunden/469469_76275/webseiten/testseite.hello-world.net/wp-includes/functions.php on line 6114
    Forum: Plugins
    In reply to: [WooCommerce] Error warning
    Nico Marcuz

    (@nick7766)

    1 year, 12 months ago

    @cfm168 same here

    PHP Warning: Attempt to read property “order_awaiting_payment” on null in /xxx/wordpress/wp-content/plugins/woocommerce/includes/wc-cart-functions.php on line 187

    Forum: Plugins
    In reply to: [Unite Gallery Lite] Is there still support for Unite Gallery Pro?
    Thread Starter Nico Marcuz

    (@nick7766)

    2 years, 2 months ago

    are you using the pro (pay!) version?

    Forum: Plugins
    In reply to: [Contact Form 7] PHP Fatal error: Uncaught Error: Call to undefined function plugin_basename()
    Thread Starter Nico Marcuz

    (@nick7766)

    2 years, 5 months ago

    thnx Takayuki

    Forum: Plugins
    In reply to: [Contact Form 7] PHP Fatal error: Uncaught Error: Call to undefined function plugin_basename()
    Thread Starter Nico Marcuz

    (@nick7766)

    2 years, 5 months ago

    Good morning Takayuki!
    Thank you very much for your quick response.
    We work with the Generate Press theme (current Pro version).

    The plugins we use are:

    1. Advanced Custom Fields PRO
    2. Borlabs Cookie – Cookie Opt-in
    3. Classic Editor
    4. Contact Form 7
    5. Custom Post Type UI
    6. Elementor Pro
    7. Elementor
    8. GP Premium
    9. Post Types Order
    10. Product Filter for WooCommerce
    11. WooCommerce
    12. Yoast SEO Premium
    13. Yoast SEO
    14. WP Grid Builder – Elementor
    15. WP Grid Builder
    16. WP Rocket
    17. wpDiscuz
    Forum: Plugins
    In reply to: [Query Monitor] PHP Fatal error: Uncaught Error: Class ‘QM_Component’ not found
    Thread Starter Nico Marcuz

    (@nick7766)

    2 years, 6 months ago

    Hi John,

    yes, the error only occurred when updating the plugin to the current version.

    We have updated from the last current version to the most current version.

    Maybe this will help you a little further in troubleshooting.

    Forum: Plugins
    In reply to: [WooCommerce] WC Cronjob tasks . Here: Action: none
    Thread Starter Nico Marcuz

    (@nick7766)

    2 years, 11 months ago

    With pleasure. i did it some time ago.

    Forum: Plugins
    In reply to: [Unite Gallery Lite] Unite Gallery Lite Vulnerability
    Thread Starter Nico Marcuz

    (@nick7766)

    2 years, 11 months ago

    @davidritter Are you using the Lite or the Pro version?

    Forum: Plugins
    In reply to: [WooCommerce] WC Cronjob tasks . Here: Action: none
    Thread Starter Nico Marcuz

    (@nick7766)

    2 years, 11 months ago

    Thank you for the explanation. I understood everything.

    I think we can close this ticket.

    best regards
    Nick

    Forum: Plugins
    In reply to: [WooCommerce] WC Cronjob tasks . Here: Action: none
    Thread Starter Nico Marcuz

    (@nick7766)

    2 years, 11 months ago

    @babylon1999

    Hi Saif,

    I understand what the task “woocommerce_cleanup_rate_limits” is responsible for. However, since no action is assigned to the task, I thought that the task could not be executed properly if it was required by WooCommerce.

    Just for my understanding the additional question:

    Do I understand correctly that if WooCommerce requires the task “woocommerce_cleanup_rate_limits” then an action is dynamically assigned to this task?

    Forum: Plugins
    In reply to: [WooCommerce] WC Cronjob tasks . Here: Action: none
    Thread Starter Nico Marcuz

    (@nick7766)

    2 years, 11 months ago

    Good morning Igor. Many thanks for your feedback.

    Sorry that I’m asking here again: I understand that as you write, the cron event is set to run but that there is no function stored that should be processed when it is run. Understood everything.

    This is exactly what worries us about the woocommerce_cleanup_rate_limits cron job.

    Does your last sentence “This issue frequently arises when plugins fail to clear their cron events upon deactivation. It is probable that these can be safely removed” mean that an external plugin may have caused this problem and that we should delete the cron job “woocommerce_cleanup_rate_limits” to fix the problem?

    Sorry for the trouble!

    Forum: Plugins
    In reply to: [WooCommerce] WC Cronjob tasks . Here: Action: none
    Thread Starter Nico Marcuz

    (@nick7766)

    2 years, 11 months ago

    Good morning Igor!

    Many thanks for your feedback. If we see it correctly, these two tasks should be performed on a daily basis. If this assumption is correct, is it okay that there is no entry in “Action”? (See the screenshot).

    2023-06-13_08h10_13.png

    Forum: Plugins
    In reply to: [WooCommerce] WC Cronjob tasks . Here: Action: none
    Thread Starter Nico Marcuz

    (@nick7766)

    2 years, 11 months ago

    Godd morning @xue28 ,

    What is the function of the two tasks woocommerce_cleanup_rate_limits and woocommerce_tracker_send_event? What should they do in principle?

Viewing 15 replies - 1 through 15 (of 259 total)
1 2 3 … 16 17 18