Forum Replies Created

Viewing 15 replies - 1 through 15 (of 39 total)
  • Thread Starter prwordpressorg

    (@prwordpressorg)

    I switched over to Gutenberg, now the duplicate button does appear.

    However, since it wasn´t clear how to use this/duplicate, here are the steps for everyone else:

    1. Make sure you are using Gutenberg to create new posts/pages.
    2. Create new post/page, add title and content.
    3. Save/publish.
    4. Go back to the editing of the post/page, find the Translations section.
    5. Click the + button next to the language version you now want to create of this page.
    6. A new empty post/page will open in edit mode.
    7. Go to the Translation section, look for a button “Duplicate translation from (previous language)”.
    8. Click = Duplicate.
    9. The currently opened page will now be replaced by a new one that will import the title and the content from the post/page language you selected.
    10. Be carefull that the words “translation” will be automatically be added to the title; delete/edit title/page as you wish.
    11. Save/publish.
    12. Repeat for more languages if needed.

    It would be great if the developers copied these “how to” into the instructions section.

    Thread Starter prwordpressorg

    (@prwordpressorg)

    I found the solution, so for anyone else:

    Go to your MySQL database and run the following command (where table_name is the name of the tabe with users):

    UPDATE TABLE_NAME SET user_registered = ‘1900-01-01 01:01:01’ WHERE user_registered = ‘0000-00-00 00:00:00’

    This will replace the 0000-00-00 00:00:00 records with the new date.

    Thread Starter prwordpressorg

    (@prwordpressorg)

    I have noticed the bug has been found and solved and a patch will come out in the 7.7 version.

    But that is another two-three weeks away 😥

    Since 80 % of my database has been imported into WordPress and WooCommerce from a CSV file (a few years back, it has never been an issue until now), I have potentially thousands of customers that get an error in the checkout and won´t be able to complete their order (some are reporting it, most just leave after the error without buying).

    If I understand it correctly, the way to solve this for now is to go into the database/mySQL, find the users with the 0000000 in the user_registered column and change it to something non-00000.

    Is there a way to do this in bulk for thousands of users?

    Thanks.

    Thread Starter prwordpressorg

    (@prwordpressorg)

    Thanks for the quick response. I had a look and that is exactly what´s happening in my installation: I have cusomers that have been imported through a csv file and thus their date/time of registration is the problematic 00000000. If there is a workaround (change the registartion date/time of these records in bulk to a non 000000 time/date), I´d be happy to find out. Otherwise I will just ahve to wait for the update.

    Thread Starter prwordpressorg

    (@prwordpressorg)

    I just noticed this is a known bug in iThemes Security: https://wordpress.org/support/topic/error-for-php-8-1-2/

    Thread Starter prwordpressorg

    (@prwordpressorg)

    The issue disappeared/was solved by the 7.0.2 – 2023-01-11 update (Fix – Expand charges object from incoming webhooks using Stripe API version 2022-11-15.)

    Thread Starter prwordpressorg

    (@prwordpressorg)

    That worked, thanks!

    Thread Starter prwordpressorg

    (@prwordpressorg)

    Hi, thanks for the reply and instructions. I was using another email customizer for styling the general WordPress emails and that was the conflict. I have now solved the issue.

    Thread Starter prwordpressorg

    (@prwordpressorg)

    I deleted Kadence Email Designer and now I am using just your plugin for both WordPress as well as WooCommerce emails. I found all the settings and all is fine, thanks.

    Thread Starter prwordpressorg

    (@prwordpressorg)

    I deactivated iThemes Security, but the issue persisted, so it wasn´t caused by iThemes Security.

    Thread Starter prwordpressorg

    (@prwordpressorg)

    Hi, I take the previous back… I found all the options/everything 🙂

    Thread Starter prwordpressorg

    (@prwordpressorg)

    Will do, obvious, thanks for pointing it out… 🙂

    Thread Starter prwordpressorg

    (@prwordpressorg)

    Hi, thanks for all the suggestions.

    After further debugging, I have narrowed the issue down to the following:

    When looking into the WooCommerce error log, I see the following notice…

    2022-12-11T22:29:39+00:00 CRITICAL Uncaught Error: Attempt to modify property "data" on null in /www/doc/www.mydomain.com/www/wp-content/plugins/woocommerce-gateway-stripe/includes/class-wc-stripe-webhook-handler.php:848
    Stack trace:
    #0 /www/doc/www.mydomain.com/www/wp-content/plugins/woocommerce-gateway-stripe/includes/class-wc-stripe-webhook-handler.php(990): WC_Stripe_Webhook_Handler->process_payment_intent_success(Object(stdClass))
    #1 /www/doc/www.mydomain.com/www/wp-content/plugins/woocommerce-gateway-stripe/includes/class-wc-stripe-webhook-handler.php(70): WC_Stripe_Webhook_Handler->process_webhook('{\n  "id": "evt_...')
    #2 /www/doc/www.mydomain.com/www/wp-includes/class-wp-hook.php(308): WC_Stripe_Webhook_Handler->check_for_webhook('')
    #3 /www/doc/www.mydomain.com/www/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters('', Array)
    #4 /www/doc/www.mydomain.com/www/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
    #5 /www/doc/www.mydomain.com/www/wp-content/plugins/woocommerce/includes/class-wc-api.php(161): do_action('woocommerce_api...')
    #6 /www/doc/www.mydomain.com/www/wp-includes/class-wp-hook.php(308): WC_API->handle_api_requests(Object(WP))
    #7 /www/doc/www.mydomain.com/www/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array)
    #8 /www/doc/www.mydomain.com/www/wp-includes/plugin.php(565): WP_Hook->do_action(Array)
    #9 /www/doc/www.mydomain.com/www/wp-includes/class-wp.php(399): do_action_ref_array('parse_request', Array)
    #10 /www/doc/www.mydomain.com/www/wp-includes/class-wp.php(780): WP->parse_request('')
    #11 /www/doc/www.mydomain.com/www/wp-includes/functions.php(1332): WP->main('')
    #12 /www/doc/www.mydomain.com/www/wp-blog-header.php(16): wp()
    #13 /www/doc/www.mydomain.com/www/index.php(17): require('/www/doc/mydomain...')
    #14 {main}
      thrown v /www/doc/www.mydomain.com/www/wp-content/plugins/woocommerce-gateway-stripe/includes/class-wc-stripe-webhook-handler.php on line 848
    

    So the issue is with WC_Stripe_Webhook_Handler (woocommerce-gateway-stripe) and the line 848 in class-wc-stripe-webhook-handler.php is

    $charge = end( $intent->charges->data );

    The setting of this line is marked yellow on this screenshot: https://snipboard.io/XTagHM.jpg

    I am however not sure of the function of this line, would anyone please have an idea? Thanks.

    Thread Starter prwordpressorg

    (@prwordpressorg)

    On further investigation, I turned wp-congif to debug and found the following lines of code…

    [10-Dec-2022 17:51:42 UTC] PHP Deprecated:  trim(): Passing null to parameter #1 ($string) of type string is deprecated in /www/doc/www.mydomain.com/www/wp-content/plugins/better-wp-security/core/core.php on line 1102
    [10-Dec-2022 17:51:42 UTC] PHP Deprecated:  strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /www/doc/www.mydomain.com/www/wp-includes/functions.php on line 7022
    [10-Dec-2022 17:51:42 UTC] PHP Deprecated:  str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /www/doc/www.mydomain.com/www/wp-includes/functions.php on line 2162
    [10-Dec-2022 17:51:42 UTC] PHP Deprecated:  strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /www/doc/www.mydomain.com/www/wp-includes/functions.php on line 7022
    [10-Dec-2022 17:51:42 UTC] PHP Deprecated:  str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /www/doc/www.mydomain.com/www/wp-includes/functions.php on line 2162
    [10-Dec-2022 17:51:42 UTC] PHP Deprecated:  Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /www/doc/www.mydomain.com/www/wp-includes/Requests/Cookie/Jar.php on line 63
    [10-Dec-2022 17:51:42 UTC] PHP Deprecated:  Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /www/doc/www.mydomain.com/www/wp-includes/Requests/Cookie/Jar.php on line 73
    [10-Dec-2022 17:51:42 UTC] PHP Deprecated:  Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /www/doc/www.mydomain.com/www/wp-includes/Requests/Cookie/Jar.php on line 89
    [10-Dec-2022 17:51:42 UTC] PHP Deprecated:  Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /www/doc/www.mydomain.com/www/wp-includes/Requests/Cookie/Jar.php on line 102
    [10-Dec-2022 17:51:42 UTC] PHP Deprecated:  Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /www/doc/www.mydomain.com/www/wp-includes/Requests/Cookie/Jar.php on line 111
    [10-Dec-2022 17:51:43 UTC] PHP Deprecated:  trim(): Passing null to parameter #1 ($string) of type string is deprecated in /www/doc/www.mydomain.com/www/wp-content/plugins/better-wp-security/core/core.php on line 1102
    [10-Dec-2022 17:51:43 UTC] PHP Deprecated:  strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /www/doc/www.mydomain.com/www/wp-includes/functions.php on line 7022
    [10-Dec-2022 17:51:43 UTC] PHP Deprecated:  str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /www/doc/www.mydomain.com/www/wp-includes/functions.php on line 2162
    [10-Dec-2022 17:51:43 UTC] PHP Deprecated:  Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /www/doc/www.mydomain.com/www/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40
    [10-Dec-2022 17:51:43 UTC] PHP Deprecated:  Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /www/doc/www.mydomain.com/www/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51
    [10-Dec-2022 17:51:43 UTC] PHP Deprecated:  Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /www/doc/www.mydomain.com/www/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68
    [10-Dec-2022 17:51:43 UTC] PHP Deprecated:  Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /www/doc/www.mydomain.com/www/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82
    [10-Dec-2022 17:51:43 UTC] PHP Deprecated:  Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /www/doc/www.mydomain.com/www/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91
    [10-Dec-2022 17:51:44 UTC] PHP Deprecated:  strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /www/doc/www.mydomain.com/www/wp-includes/functions.php on line 7022
    [10-Dec-2022 17:51:44 UTC] PHP Deprecated:  str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /www/doc/www.mydomain.com/www/wp-includes/functions.php on line 2162

    Can somebody please see what I am not seeing?

Viewing 15 replies - 1 through 15 (of 39 total)