WPIntell

Source evidence

all images disapear after update

WP Compress – Instant Performance & Speed Optimization · support · 2022-11-15T16:51:00+00:00

mixedsentiment
mediumseverity
0.78relevance
3replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

6 / 28 rows with source links

21.4% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

22 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
John Huebner resolved
When updating from 5.11.10 to 6.00.04 all images on the site are removed. Reverting restores images. @hube2 Hi,sorry to hear that! But we actually don’t have a function which removes images (delete_attachment) or anything similar. Just simply on plugin update you needed to click “Reconnect” and re-enter your API Key just so that the plugin connects back to the CDN. We are working on a fix for that, but your images were not removed. In case you need further assistance feel free to contact us! 🙂 This issue can be closed. I’m working with the client to try an figure out what their api key is. Seems they’ve forgotten they had an account or the account belongs to their previous developer. I will open a new ticket if we’re still having problems when we get that worked out.

Comments

3 shown
WP Compress 2022-11-16T06:31:00+00:00

@hube2 Hi,sorry to hear that! But we actually don’t have a function which removes images (delete_attachment) or anything similar. Just simply on plugin update you needed to click “Reconnect” and re-enter your API Key just so that the plugin connects back to the CDN. We are working on a fix for that, but your images were not removed. In case you need further assistance feel free to contact us! 🙂

WP Compress 2022-11-18T05:45:00+00:00

This issue can be closed.

John Huebner 2022-11-18T12:41:00+00:00

I’m working with the client to try an figure out what their api key is. Seems they’ve forgotten they had an account or the account belongs to their previous developer. I will open a new ticket if we’re still having problems when we get that worked out.