Term Cleanup: When initially starting the term consolidation process, can take a while to reload the page
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- php
- Domain
- backend, performance
Research direction
Reproduce the delay by clicking Find similar tags with a taxonomy containing many terms, then trace the action that handles the initial term consolidation request. Determine which work blocks the page reload; done means the initial page refresh is prompt while the consolidation continues as intended, with coverage for the large-taxonomy case.
Written by the indexing model from the issue text.
Description
Describe the bug
Originally reported by @dkotter:
This may not be a big deal but I noticed that if I have a taxonomy with lots of terms (in my case, was testing with ~8000 tags), when I initially click the
Find similar tagsbutton, it reloads the page but takes quite awhile for that reload to work. I had assumed that clicking that button would trigger the process to start in the background, which means it wouldn't take any extra time to load. I'm guessing what's happening is it's starting the process and running the first iteration at the same time, thus resulting in the page taking a bit to load.
That assumption may be wrong but would be nice to figure out why that first load is so long and see if we can make that a normal page load.
Steps to Reproduce
Originally reported by @dkotter:
Start the term consolidation process with a taxonomy that has lots of terms. Note that it takes quite a few seconds for the page to refresh.
Screenshots, screen recording, code snippet
No response
Environment information
No response
WordPress information
Originally reported in https://github.com/10up/classifai-cleanup/issues/4.
Code of Conduct
- I agree to follow this project's Code of Conduct
- Dominant language
- PHP
- Stars
- 714
- Forks
- 68
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 23
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from 10up/classifai
-
wpvc
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
wpvc
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Register ClassifAI functionality with the Abilities APIPossibly taken @nhrrob claimed this 10 days ago. Openhelp wanted
Difficulty 4/5 3-5 days Newbie friendliness 48/100
10up/classifai#1249 · 1 assignee ·
Maintainers usually reply within 1 day
-
OpenAI usage tracking: Project ID setting is ignoredPossibly taken @dajiaohuang claimed this 30 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
BYOK Openai modelsOpen
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
Similar issues
-
Exclude module `require-dev` and `autoload-dev` from the generated `composer.json`Possibly taken @keiserjb claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
uiowa/uiowa#10310 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mailcow/mailcow-dockerized#7677 · 1 comment ·
Maintainers usually reply within 1 day
-
a11y
Difficulty 2/5 1-3 hours Newbie friendliness 67/100