Forum Replies Created

Viewing 15 replies - 1 through 15 (of 21 total)
  • Hi @godsdead

    As I said before, this is still a issue for me, you and thousands others…

    However, it should be best to open another topic and mention this entry because they seem to prefer to mark topics as “solved” instead of solving it… I don’t think they watch “solved” topics…

    Don’t forget to mention you entry here!

    Thread Starter gotman

    (@gotman)

    Hi @adskiller

    I think it must be better for you to open a new topic because I suspect that when they as “resolved” this one, they stop to see it (statistics … go imagine).

    I also still have this problem on my site. In fact, I’m still stuck to Vers?o 13.5…

    Regards

    Thread Starter gotman

    (@gotman)

    Why are you closing this? This is not fixed and…

    I don’t have a Github account and I don’t plan to open one.

    That way, this is the only channel that I have to provide you precious information.

    ps- this is NOT resolved! Please un-mark this as a resolved thread.

    • This reply was modified 4 years, 1 month ago by gotman.
    Thread Starter gotman

    (@gotman)

    Hi, @jerparx

    …yeah, I have more information:

    This not only affects the wp-admin dashboard. It affects the loading time on the intire site frontend. But I guess you already know that…

    Hopefully you can tell this to your developers so they can take this as a serious issue and prioritize it.

    Thanks!

    Thread Starter gotman

    (@gotman)

    @priscillamc

    My question for now, is: When do you predict a solution for this bug?

    Thread Starter gotman

    (@gotman)

    Hi @priscillamc

    First of all, this is the second time that I have serious problems that seriously hurt my site by using your SEO plugin. I use o think you’re the best, but…

    Secondly, I’m force to downgrade because I need my site working. That being said, I have some questions.

    Questions:

    – Will I loose anything from my hard work by downgrading you plugin?

    Also:

    – What current tables (example: indexables) I can delete without loosing my SEO efforts?

    Thread Starter gotman

    (@gotman)

    I appreciate your apologies, but please understand that each attempt to access the back end throws the server load to limits that make my site go offline.

    This bug needs an ASAP solution!

    I need to access my backend regularly.

    wrong reply… sorry

    • This reply was modified 4 years, 1 month ago by gotman.
    Thread Starter gotman

    (@gotman)

    My server did that (WP CLI command) but now my site is even slower and now I just can’t access to wp-admin.

    Last minute update:

    My hosting company says: Below, the queries that we continue to see, even after wp cli has been indexing.

    +-----+----------------+-----------+----------------+---------+------+------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------+
    | Id | User | Host | db | Command | Time | State | Info | Progress |
    +-----+----------------+-----------+----------------+---------+------+------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------+
    | 554 | mysite | localhost | mysite | Query | 128 | Sending data | SELECT COUNT(term_id)
    FROM wp_term_taxonomy
    WHERE term_id NOT IN (
    SELECT object_id FROM wp_yoast_indexable WHERE link_count IS NOT NULL AND object_type = 'term'
    ) AND taxonomy IN ('category', 'post_tag', 'post_format') | 0.000 |
    | 597 | mysite | localhost | mysite | Query | 93 | Sending data | SELECT COUNT(term_id)
    FROM wp_term_taxonomy
    WHERE term_id NOT IN (
    SELECT object_id FROM wp_yoast_indexable WHERE link_count IS NOT NULL AND object_type = 'term'
    ) AND taxonomy IN ('category', 'post_tag', 'post_format') | 0.000 |
    | 666 | mysite | localhost | mysite | Query | 49 | Waiting for table level lock | UPDATE wp_yoast_indexable SET permalink = 'https://www.mysite.com/tag/bucket/', permalink_hash = '46:c0a4ffa1bec561f0bcabfbc8a4addf53', updated_at = '2020-10-22 09:59:49' WHERE id = '5303' | 0.000 |
    | 670 | mysite | localhost | mysite | Query | 46 | Waiting for table level lock | SELECT * FROM wp_yoast_indexable WHERE object_id = '28047' AND object_type = 'post' LIMIT 1 | 0.000 |
    | 673 | mysite | localhost | mysite | Query | 40 | Waiting for table level lock | SELECT * FROM wp_yoast_indexable WHERE object_id = '25624' AND object_type = 'post' LIMIT 1 | 0.000 |
    | 674 | mysite | localhost | mysite | Query | 40 | Waiting for table level lock | SELECT * FROM wp_yoast_indexable WHERE object_id = '9542' AND object_type = 'post' LIMIT 1 | 0.000 |
    | 676 | mysite | localhost | mysite | Query | 34 | Waiting for table level lock | SELECT * FROM wp_yoast_indexable WHERE object_id = '1476' AND object_type = 'term' LIMIT 1 | 0.000 |
    | 677 | mysite | localhost | mysite | Query | 28 | Waiting for table level lock | SELECT * FROM wp_yoast_indexable WHERE object_id = '25543' AND object_type = 'post' LIMIT 1 | 0.000 |
    | 678 | mysite | localhost | mysite | Query | 19 | Waiting for table level lock | SELECT * FROM wp_yoast_indexable WHERE object_id = '3936' AND object_type = 'post' LIMIT 1 | 0.000 |
    | 680 | mysite | localhost | mysite | Query | 16 | Waiting for table level lock | SELECT * FROM wp_yoast_indexable WHERE object_id = '29306' AND object_type = 'post' LIMIT 1 | 0.000 |
    | 681 | mysite | localhost | mysite | Query | 16 | Waiting for table level lock | SELECT * FROM wp_yoast_indexable WHERE object_id = '5270' AND object_type = 'term' LIMIT 1 | 0.000 |
    | 682 | mysite | localhost | mysite | Query | 15 | Waiting for table level lock | SELECT * FROM wp_yoast_indexable WHERE object_id = '16582' AND object_type = 'post' LIMIT 1 | 0.000 |
    | 684 | mysite | localhost | mysite | Query | 8 | Waiting for table level lock | SELECT * FROM wp_yoast_indexable WHERE object_id = '1148' AND object_type = 'term' LIMIT 1 | 0.000 |
    | 685 | mysite | localhost | mysite | Query | 5 | Waiting for table level lock | SELECT * FROM wp_yoast_indexable WHERE object_id = '16172' AND object_type = 'post' LIMIT 1 | 0.000 |
    | 687 | mysite | localhost | mysite | Query | 4 | Waiting for table level lock | SELECT * FROM wp_yoast_indexable WHERE object_id = '25849' AND object_type = 'post' LIMIT 1 | 0.000 |
    | 688 | mysite | localhost | mysite | Query | 3 | Waiting for table level lock | SELECT * FROM wp_yoast_indexable WHERE object_id = '16172' AND object_type = 'post' LIMIT 1 | 0.000 |
    | 689 | root | localhost | NULL | Query | 0 | NULL | show full processlist | 0.000 |

    HELP!!

    Tested solutions in wampp:

    • Replaced my theme to Twenty Twenty;
    • Switch OFF all other plugins.

    Result: site very slower and no access to wp-admin

    • This reply was modified 4 years, 1 month ago by gotman.
    • This reply was modified 4 years, 1 month ago by gotman.
    • This reply was modified 4 years, 1 month ago by gotman.
    • This reply was modified 4 years, 1 month ago by gotman.
    Thread Starter gotman

    (@gotman)

    OK! My hosting company response:

    The URLs /wp-json/yoast/v1/indexation/terms and /wp-json/yoast/v1/indexation/prepare can give 404 or 524 errors due to timeout. In other words, their execution starts the process, the load triggers and this situation occurs.

    We now open them in the browser and the load has skyrocketed from 2 to 9. When the load goes up, there is an error 404 or 524 for not being able to complete the request. 524 is the timeout code.

    The server is configured with the normal rewrite rules of WordPress and we have nothing to block these URLs.

    Also, there is no special coding on the theme

    • This reply was modified 4 years, 1 month ago by gotman.
    • This reply was modified 4 years, 1 month ago by gotman.
    Thread Starter gotman

    (@gotman)

    Hi @pcosta88

    First of all, thanks!

    Here’s some answers to your questions. Hopefully you can find possible culprits.

    1. Yes. I’m using WordPress 5.5.1.
    2. I was using only ONE plugin (Yoast WordPress SEO) and the Twenty Twenty theme. Both where updated.
    3. I have 4000 posts, 15 pages, 90 categories and 2000 tags.
    4. The server has all the right requirements. I’m on a VPS (nginx 1.17.2).
    5. Those messages in the dev tools, did appear when I ran the SEO data button.

    One more thing: even in my dev site, I have HUGE dificulties to enter my wp-admin. In localhost (wampp), I only have ONE plugin: Yoast WordPress SEO, and the Twenty Twenty theme.

    • This reply was modified 4 years, 1 month ago by gotman.

    Hi @pcosta88

    I was only replying to the question posed by @arzoo:

    Hi, just wondering if anyone else is experiencing significant slowdown of the WP admin?

    Not only I’m experiencing a big slowdown, but I’m also experiencing my site being offline when I sometimes try to access wp-admin, and also:

    yoast settings panel not accessible

    This is my own topic: Site constantly Offline & SEO Optimization error message

    Hi @devnihil does my message help? Should I open one topic to this?

    I’m asking because I already tried the solution that you proposed to @scalero and it did not work …

    In fact, this is a serious problem on my site…

    Thanks for your attention.

    I also have this.

    My site is barely unusable from 5 months to this part. The problem must be related with the indexables…

    I also tried to put this on my dev machine and I found this message on dev tools console:

    POST https://localhost/mysite/wp-json/yoast/v1/indexation/prepare 404 (Not Found)
    (anonymous) @ indexation-1511.js:1

    tryCatch @ wp-polyfill.min.js:3
    invoke @ wp-polyfill.min.js:3
    t.<computed> @ wp-polyfill.min.js:3
    r @ indexation-1511.js:1
    (anonymous) @ indexation-1511.js:1
    (anonymous) @ indexation-1511.js:1
    (anonymous) @ indexation-1511.js:1
    (anonymous) @ indexation-1511.js:1
    tryCatch @ wp-polyfill.min.js:3
    invoke @ wp-polyfill.min.js:3
    t.<computed> @ wp-polyfill.min.js:3
    tryCatch @ wp-polyfill.min.js:3
    maybeInvokeDelegate @ wp-polyfill.min.js:3
    invoke @ wp-polyfill.min.js:3
    t.<computed> @ wp-polyfill.min.js:3
    r @ indexation-1511.js:1
    (anonymous) @ indexation-1511.js:1
    Promise.then (async)
    r @ indexation-1511.js:1
    (anonymous) @ indexation-1511.js:1
    (anonymous) @ indexation-1511.js:1
    (anonymous) @ indexation-1511.js:1
    (anonymous) @ indexation-1511.js:1
    tryCatch @ wp-polyfill.min.js:3
    invoke @ wp-polyfill.min.js:3
    t.<computed> @ wp-polyfill.min.js:3
    r @ indexation-1511.js:1
    (anonymous) @ indexation-1511.js:1
    (anonymous) @ indexation-1511.js:1
    (anonymous) @ indexation-1511.js:1
    Ag @ react-dom.min.js:116
    zg @ react-dom.min.js:116
    qi @ react-dom.min.js:130
    ui @ react-dom.min.js:133
    (anonymous) @ react-dom.min.js:158
    unstable_runWithPriority @ react.min.js:27
    Vc @ react-dom.min.js:158
    Sc @ react-dom.min.js:158
    Z @ react-dom.min.js:156
    ah @ react-dom.min.js:159
    xf @ react-dom.min.js:40

    And online I get this message:

    POST https://www.mysite.com/wp-json/yoast/v1/indexation/terms 524

    indexation-1511.js:1

    (anonymous) @ indexation-1511.js:1
    tryCatch @ wp-polyfill.min.js:1
    invoke @ wp-polyfill.min.js:1
    t.<computed> @ wp-polyfill.min.js:1
    r @ indexation-1511.js:1
    (anonymous) @ indexation-1511.js:1
    (anonymous) @ indexation-1511.js:1
    (anonymous) @ indexation-1511.js:1
    (anonymous) @ indexation-1511.js:1
    tryCatch @ wp-polyfill.min.js:1
    invoke @ wp-polyfill.min.js:1
    t.<computed> @ wp-polyfill.min.js:1
    tryCatch @ wp-polyfill.min.js:1
    maybeInvokeDelegate @ wp-polyfill.min.js:1
    invoke @ wp-polyfill.min.js:1
    t.<computed> @ wp-polyfill.min.js:1
    r @ indexation-1511.js:1
    (anonymous) @ indexation-1511.js:1
    Promise.then (async)
    r @ indexation-1511.js:1
    (anonymous) @ indexation-1511.js:1
    (anonymous) @ indexation-1511.js:1
    (anonymous) @ indexation-1511.js:1
    (anonymous) @ indexation-1511.js:1
    tryCatch @ wp-polyfill.min.js:1
    invoke @ wp-polyfill.min.js:1
    t.<computed> @ wp-polyfill.min.js:1
    r @ indexation-1511.js:1
    (anonymous) @ indexation-1511.js:1
    Promise.then (async)
    r @ indexation-1511.js:1
    (anonymous) @ indexation-1511.js:1
    (anonymous) @ indexation-1511.js:1
    (anonymous) @ indexation-1511.js:1
    yg @ react-dom.min.js:62
    xg @ react-dom.min.js:61
    Ti @ react-dom.min.js:148
    unstable_runWithPriority @ react.min.js:26
    Ma @ react-dom.min.js:52
    Ia @ react-dom.min.js:140
    ze @ react-dom.min.js:118
    (anonymous) @ react-dom.min.js:53
    unstable_runWithPriority @ react.min.js:26
    Ma @ react-dom.min.js:52
    mg @ react-dom.min.js:52
    V @ react-dom.min.js:52
    Be @ react-dom.min.js:119
    xi @ react-dom.min.js:39

    Please solve this asap!

    Note: I even replaced my theme to Twenty Twenty and switch OFF all other plugins.

    • This reply was modified 4 years, 1 month ago by gotman.
    • This reply was modified 4 years, 1 month ago by gotman.
    • This reply was modified 4 years, 1 month ago by gotman.
    • This reply was modified 4 years, 1 month ago by gotman.
    • This reply was modified 4 years, 1 month ago by gotman.
Viewing 15 replies - 1 through 15 (of 21 total)