Bulk optimization for custom folder will try to optimize generated next-gen images
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- php, wordpress
- Domain
- backend, performance
Research direction
Reproduce the issue through the custom-folder bulk optimization flow: optimize once, repeat it, and inspect the media management page. Trace the code handling repeated bulk optimization and generated next-gen images; done means the second run does not add generated images to media management.
Written by the indexing model from the issue text.
Description
Before submitting an issue please check that you’ve completed the following steps:
- Made sure you’re on the latest version => 2.1.3 and 2.2.0.1
- Used the search feature to ensure that the bug hasn’t been reported before
Describe the bug
When click imagify all while having custom folder, 1st time we optimize images and create next-gen. after that , if we click again, we will optimize the generated next-gen images
To Reproduce
Steps to reproduce the behavior:
- activate imagify
- add custom folder containing couple of images and save
- In bulk optimization imagify all => wait till completed
- repeat step 3 then click media management link beside custom folder=> next-gen images are added to media management page
Expected behavior
A clear and concise description of what you expected to happen.
- from the 1st imagify all, create the most optimized version of image and next-gen
- click imagify 2nd time, won't add next-gen images in the media management table
Screenshots
If applicable, add screenshots to help explain your problem.
after 1st imagify all
after 2nd imagify all
Additional context
Add any other context about the problem here.
Acceptance Criteria (for WP Media team use only)
Clear instructions for developers, to be added before the grooming
- Dominant language
- PHP
- Stars
- 82
- Forks
- 31
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 9
Contributor guide
No contributing guide indexed for this repository
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 wp-media/imagify-plugin
-
sanitizeContext() sanitizes nothing: a string literal is passed to .replace() instead of a RegExp Openpriority: low severity: minor type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
wp-media/imagify-plugin#1263 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
wp-media/imagify-plugin#1272 ·
-
devops priority: medium type: enhancement
Difficulty 5/5 Over a week Newbie friendliness 48/100
wp-media/imagify-plugin#1268 ·
-
devops priority: low type: bug
Difficulty 4/5 3-5 days Newbie friendliness 68/100
wp-media/imagify-plugin#1264 ·
-
priority: low
Difficulty 4/5 3-5 days Newbie friendliness 42/100
wp-media/imagify-plugin#1260 ·
All issues in wp-media/imagify-plugin
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getgrav/grav-plugin-api#45 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
RSS-Bridge/rss-bridge#5098 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
phingofficial/phing#2025 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
silverstripe/developer-docs#911 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100