Forum Replies Created

Viewing 15 replies - 1 through 15 (of 67 total)
  • @raamdev the whole issue with this new @clavaque , is that he ignored all my replies to all my support tickets, and since he toke over the project from you, not one update was pushed clean in the PRO version! Since 170808-RC . Even that was on RC left. Simply either he is completely ignorant, or he lacks common sense! I cannot display my disappointment, since this plugin had a great future, thats why I bought the pro version, just to see that for years we are supportless.

    @yvankarman2 I see the point of @vitaljik here. First of all just for the fact that the same team who made FluentCRM pushes their products and not allowing native integration with modules renowned on WordPress ecosystem, does not make them better.

    Each product has their free version, what the developers here ignore is that many of us out there already have customers integrated to products like Gravity forms, and to throw those out in favour of any other forms, just because the developers ignore the community demands, thats their issue.

    A lot of people try to push their products and only those in front, thats ignorance and lack of respect to the people who already use other plugins. I am in same boat with his points made above.

    Thread Starter Viorel-Cosmin Miron

    (@siravecavec)

    @ihereira maybe would help more to review also the github issue we opened. Since this forum is ancient, does not allow users to upload images in year 2022… Should we assume not everyone is using some online screenshot solution.

    Thread Starter Viorel-Cosmin Miron

    (@siravecavec)

    @sterndata I did not wished to be disrespectful in any ways, yet in such manners no one will ever solve their issues, when we hide behind words and our actions lead nowhere. If you follow along the ticket, I provided all information requested on time, and this even after proving that we are dealing with a issue that is not a corrupt DB, yet a possible bug in latest WooCommerce release. Its just absurd since the very same behaviour in this ticket alone was enforced twice for no given reason. Not only we make mistakes remind that to your support team. It seems is exactly as I would expect, @rainfallnixfig just jumped in the ticket, not even studying properly what was done and said, no proof was presented to us as to tests conducted, and one cannot try to replicate a issue, without having out of all our data or no steps were asked nor provided to allow this issue to be properly tested on by @rainfallnixfig . So I must agree NOT all SUPPORT people are easy or maybe I should assume, that this is not meant to help people solve real issues, just to forward them to a codeable 3rd party developer, for trying to debug a real issue that occurs only when upgrading to latest release. And that is something we do not control unfortunately. To keep users out of date, is not an option either, to upgrade will break portions of site that worked well before upgrade, still to tell us that is nothing you can do, show us what was done in regards to our specific issues, all issues are specific here.

    Only a person who did not what they said to be done, would go and report someone who tries only to track a possible bug, like said earlier bug request with images and details was opened here: https://github.com/woocommerce/woocommerce-admin/issues/8507

    Thread Starter Viorel-Cosmin Miron

    (@siravecavec)

    @rainfallnixfig do not mark this as resolved, until we say is resolved, you did nothing as to what and how our issue is manifesting, only empty promises.

    Thread Starter Viorel-Cosmin Miron

    (@siravecavec)

    We will never understand such stace from any support unfortunately is not acceptable. We will rather look into alternatives to woocommerce, since this is not affecting us directly, yet our customers, and it seems no matter what we provided here, was all ignored, in favour of these nonsense replies and yeah, perfect closed loop.

    Thread Starter Viorel-Cosmin Miron

    (@siravecavec)

    @rainfallnixfig how can you replicate this, when you do not have my data. The issue in question cannot be replicated without a few years of data in woocommerce, or the whole point of the issue described does not matter. So what you want me to do now, since your reply is not conclusive, we wont ask help from anyone, we will open a bug request, the fast that you cannot replicate it, does not bother me, since you never even touched or seen our setup, so please. You folks must have a good life doing these nonsense replies and not giving any help to troubleshoot real issues, that if you do not replicate, arent issues? You be jocking me please let someone else reply or just reply to other threads, since you seem to neglect real issues in favour of pushing people to codeable, I prooved you this is not a corrupt DB, I bring proof the website works perfectly right before the upgrade, and you give us this non-sense. Expected from somehow who is solely on making money from doing nothing.

    Thread Starter Viorel-Cosmin Miron

    (@siravecavec)

    Hi,

    Anyhow your support lacks support. Because I did more investigation into this, and got to conclusion my DB is not corrupt, yet after migrating to version 6.3.1 the leaderboard part in analytics is completely missing.

    Since I restored a working backup in staging again, ofc the stable release was 6.2.2 at the time, and it seems all works as designed, once I upgrade to latest wooCommerce release, leaderboard data gets the above issue.

    So what ever was done in latest update, is what messed the DB, so stop implying our DB is corrupt, and we need to look into restoring. Thats what we did, and I can replicate this scenario 100 times, results are identical.

    Thread Starter Viorel-Cosmin Miron

    (@siravecavec)

    So I have absolutely no idea what and why I was working on this ticket for 3 days, made all the steps, and on end you tell me to restore. Some support!

    Thread Starter Viorel-Cosmin Miron

    (@siravecavec)

    so running the above, will render unusable what previously worked. I had issues only with Missing leaderboard in analytics, now all are missing again.

    Now we move to what? I see a Exclamation mark, for now I cannot provide snapshop, not using any of the mentioned tools.

    This is what we have in console.

    03:31:10.026 XHR GEThttps://www.staging.tabaklaedeli.ch/wp-json/wc-analytics/leaderboards?after=2021-01-01T00:00:00&before=2021-12-31T23:59:59&per_page=5&persisted_query={}&_locale=user
    [HTTP/2 500 Internal Server Error 103ms]
    P
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/api-fetch.min.js:2:5296
    p
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/api-fetch.min.js:2:2692
    jqrR/x/</<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/api-fetch.min.js:2:5592
    jqrR/v<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/api-fetch.min.js:2:5057
    jqrR/x/</<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/api-fetch.min.js:2:5592
    a
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/api-fetch.min.js:2:1488
    jqrR/x/</<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/api-fetch.min.js:2:5592
    jqrR/v<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/api-fetch.min.js:2:4881
    jqrR/x/</<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/api-fetch.min.js:2:5592
    jqrR/s/</<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/api-fetch.min.js:2:1721
    a
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/api-fetch.min.js:2:1488
    jqrR/s/<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/api-fetch.min.js:2:1523
    jqrR/x/</<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/api-fetch.min.js:2:5592
    t
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/api-fetch.min.js:2:1204
    jqrR/x/</<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/api-fetch.min.js:2:5592
    j
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/api-fetch.min.js:2:3959
    jqrR/x/</<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/api-fetch.min.js:2:5592
    jqrR/i/<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/api-fetch.min.js:2:2338
    jqrR/x/</<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/api-fetch.min.js:2:5592
    x
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/api-fetch.min.js:2:5600
    FETCH_WITH_HEADERS
    https://www.staging.tabaklaedeli.ch/wp-content/plugins/woocommerce/packages/woocommerce-admin/dist/data/index.js:2:76742
    +ekt/l/r</<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/redux-routine.min.js:2:1495
    vsQm/e.default/t/c/r/<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/redux-routine.min.js:2:9446
    r
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/redux-routine.min.js:2:9421
    vsQm/e.default/t/c/u/<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/redux-routine.min.js:2:9375
    c
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/redux-routine.min.js:2:9476
    t
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/redux-routine.min.js:2:9732
    k4FQ/e.iterator
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/redux-routine.min.js:2:7260
    vsQm/e.default/t/c/r/<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/redux-routine.min.js:2:9446
    r
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/redux-routine.min.js:2:9421
    vsQm/e.default/t/c/u/<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/redux-routine.min.js:2:9375
    c
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/redux-routine.min.js:2:9476
    t
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/redux-routine.min.js:2:9732
    +ekt/l/</<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/redux-routine.min.js:2:1634
    +ekt/l/<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/redux-routine.min.js:2:1614
    +ekt/s/</</<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/redux-routine.min.js:2:1792
    pfJ3/L/</<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/data.min.js:2:10824
    pfJ3/x/</</<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/data.min.js:2:11136
    Q
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/data.min.js:2:16625
    pfJ3/q/instantiate/e.selectors</u/a/<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/data.min.js:2:15503
    (Async: setTimeout handler) a
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/data.min.js:2:15444
    u
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/data.min.js:2:15547
    Ro
    https://www.staging.tabaklaedeli.ch/wp-content/plugins/woocommerce/packages/woocommerce-admin/dist/data/index.js:2:84883
    639/_<
    https://www.staging.tabaklaedeli.ch/wp-content/plugins/woocommerce/packages/woocommerce-admin/dist/chunks/leaderboards.js:1:2671
    pfJ3/Pe/</</n<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/data.min.js:2:23078
    pfJ3/xe/h<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/data.min.js:2:22173
    a
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/data.min.js:2:17866
    pfJ3/Z/d/</<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/data.min.js:2:18237
    pfJ3/xe/b<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/data.min.js:2:22042
    xe
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/data.min.js:2:22166
    pfJ3/Pe/</<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/data.min.js:2:23069
    Le
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/vendor/react-dom.min.js:100:3
    Pj
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/vendor/react-dom.min.js:231:183
    di
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/vendor/react-dom.min.js:168:307
    Nj
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/vendor/react-dom.min.js:168:238
    sc
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/vendor/react-dom.min.js:168:96
    gf
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/vendor/react-dom.min.js:162:109
    $g/<
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/vendor/react-dom.min.js:73:230
    unstable_runWithPriority
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/vendor/react.min.js:24:26
    Za
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/vendor/react-dom.min.js:73:8
    $g
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/vendor/react-dom.min.js:73:178
    R
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/vendor/react.min.js:16:299
    ua.port1.onmessage
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/vendor/react.min.js:22:361
    (Async: EventHandlerNonNull) <anonymous>
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/vendor/react.min.js:22:295
    <anonymous>
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/vendor/react.min.js:9:179
    <anonymous>
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/vendor/react.min.js:9:195
    <anonymous>
    https://www.staging.tabaklaedeli.ch/wp-includes/js/dist/vendor/react.min.js:31:3

    ?

    Nothing works nor is displayed not even how it worked after reporting last Leaderboard issues.

    I asked to what table does it belong, nothing is mentioned on the link you said referring to the question I asked.

    Thread Starter Viorel-Cosmin Miron

    (@siravecavec)

    @rainfallnixfig unfortunatelly I have already did all the above mentioned steps, can you maybe be more specific towards what tables are causing the issue.

    None of the Tables show any errors in phpmyadmin nor in CLI.

    I have runned also the Update Database.

    And sorry, to do a fresh woocommerce install, do not see the point of doing all previous steps, fresh install cannot be connected to the issues I had and tried to remediate.

    Also I have done all previous all steps.

    Thread Starter Viorel-Cosmin Miron

    (@siravecavec)

    @rainfallnixfig yes we did all specified.

    I have moved the site to staging

    Disabled all plugins, switched to storefront, cleared the analytics cache, and rebuilt historical data. Errors persists in console.

    Thread Starter Viorel-Cosmin Miron

    (@siravecavec)

    @hegenberg so I managed to restore the broken tables from a backup, yet we still got this on woo error logs:

    2022-03-23T23:01:03+00:00 CRITICAL Uncaught Error: Object of class WP_Error could not be converted to string in /home/tabaklaedeli/public_html/wp-content/plugins/woocommerce/packages/woocommerce-admin/src/API/Leaderboards.php:175
    Stack trace:
    #0 /home/tabaklaedeli/public_html/wp-content/plugins/woocommerce/packages/woocommerce-admin/src/API/Leaderboards.php(356): Automattic\WooCommerce\Admin\API\Leaderboards->get_categories_leaderboard(5, '2021-01-01T00:0...', '2021-12-31T23:5...', Array)
    #1 /home/tabaklaedeli/public_html/wp-content/plugins/woocommerce/packages/woocommerce-admin/src/API/Leaderboards.php(371): Automattic\WooCommerce\Admin\API\Leaderboards->get_leaderboards(5, '2021-01-01T00:0...', '2021-12-31T23:5...', Array)
    #2 /home/tabaklaedeli/public_html/wp-includes/rest-api/class-wp-rest-server.php(1141): Automattic\WooCommerce\Admin\API\Leaderboards->get_items(Object(WP_REST_Request))
    #3 /home/tabaklaedeli/public_html/wp-includes/rest-api/class-wp-rest-server.php(988): WP_REST_Server->respond_to_request(Object(WP_REST_Request), '/wc-anal in /home/tabaklaedeli/public_html/wp-content/plugins/woocommerce/packages/woocommerce-admin/src/API/Leaderboards.php on line 175

    we got the logs when accessing analytics, on leaderboard none of the boards will load.

    Thread Starter Viorel-Cosmin Miron

    (@siravecavec)

        [tabaklae_wp1.NG3tqMiSVM_wc_admin_note_actions] Incorrect information in file: './tabaklae_wp1/NG3tqMiSVM_wc_admin_note_actions.frm'    
        [tabaklae_wp1.NG3tqMiSVM_wc_admin_note_actions] Corrupt    
        [tabaklae_wp1.NG3tqMiSVM_wc_admin_notes] Incorrect information in file: './tabaklae_wp1/NG3tqMiSVM_wc_admin_notes.frm'    
        [tabaklae_wp1.NG3tqMiSVM_wc_admin_notes] Corrupt    
        [tabaklae_wp1.NG3tqMiSVM_wc_category_lookup] Incorrect information in file: './tabaklae_wp1/NG3tqMiSVM_wc_category_lookup.frm'    
        [tabaklae_wp1.NG3tqMiSVM_wc_category_lookup] Corrupt    
        [tabaklae_wp1.NG3tqMiSVM_wc_customer_lookup] Incorrect information in file: './tabaklae_wp1/NG3tqMiSVM_wc_customer_lookup.frm'    
        [tabaklae_wp1.NG3tqMiSVM_wc_customer_lookup] Corrupt    
        [tabaklae_wp1.NG3tqMiSVM_wc_download_log] OK    
        [tabaklae_wp1.NG3tqMiSVM_wc_order_coupon_lookup] Incorrect information in file: './tabaklae_wp1/NG3tqMiSVM_wc_order_coupon_lookup.frm'    
        [tabaklae_wp1.NG3tqMiSVM_wc_order_coupon_lookup] Corrupt    
        [tabaklae_wp1.NG3tqMiSVM_wc_order_product_lookup] Incorrect information in file: './tabaklae_wp1/NG3tqMiSVM_wc_order_product_lookup.frm'    
        [tabaklae_wp1.NG3tqMiSVM_wc_order_product_lookup] Corrupt    
        [tabaklae_wp1.NG3tqMiSVM_wc_order_stats] Incorrect information in file: './tabaklae_wp1/NG3tqMiSVM_wc_order_stats.frm'    
        [tabaklae_wp1.NG3tqMiSVM_wc_order_stats] Corrupt    
        [tabaklae_wp1.NG3tqMiSVM_wc_order_tax_lookup] Incorrect information in file: './tabaklae_wp1/NG3tqMiSVM_wc_order_tax_lookup.frm'    
        [tabaklae_wp1.NG3tqMiSVM_wc_order_tax_lookup] Corrupt    

    So it seems some parts of DB are corrupt, guess there is no way to recover this now or? Ofcourse restore to a previous point, I tried to run repair it did not helped.

    Thread Starter Viorel-Cosmin Miron

    (@siravecavec)

    Copying database
    -- Connecting to localhost... mysqldump: Got error: 1033: "Incorrect information in file: './tabaklae_wp1/NG3tqMiSVM_wc_admin_note_actions.frm'" when using LOCK TABLES 

    We got this while trying to clone the site. Any idea what could cause this?

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