Support » Plugin: ShortPixel Image Optimizer » Phoenix Media Rename issue

Phoenix Media Rename issue

  • Resolved crzyhrse

    (@crzyhrse)


    6 months ago

    Please see this thread- https://wordpress.org/support/topic/conflict-with-shortpixel-image-optimizer-2/#post-13925770 –

    The “Phoenix Media Rename” plugin author has added a means for there to not be an issue with ShortPixel, and hoping you will update ShortPixel to take advantage of it – Below are the plugin author’s last words about the issue, excerpted from the above thread…

    I didn’t change anything in Phoenix Media Rename interaction with ShortPixel, I’ll check if they changed something.

    In my latest release I added a custom action to notify external plugins that an image has been renamed, I’ll contact ShortPixel support team to let them know that this integration exists, so they can avoid to compress renamed images.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support Gerard Blanco

    (@sixaxis)

    6 months ago

    Hi, @crzyhrse,

    Thank you for letting us know. We will check the status of this.

    Best,

    Plugin Support Gerard Blanco

    (@sixaxis)

    6 months ago

    Hi, @crzyhrse,

    From our side we can’t reproduce the issue; everything seems to be working well. If you can, please let us know step by step how to do so 🙂

    Best,

    Thread Starter crzyhrse

    (@crzyhrse)

    6 months ago

    Hey, it is a well known issue, you are not paying attention…

    Plugin Support Gerard Blanco

    (@sixaxis)

    6 months ago

    We do pay attention, crzyhrse.

    Like I said, we tried to reproduce the issue:

    1. Installed ShortPixel Image Optimizer
    2. Installed Phoenix Media Rename
    3. We renamed a file
    4. The file did not start re-optimizing

    If you think we are doing something wrong, please tell us what we should do step by step. Otherwise we won’t be able to help you.

    Have a good day,

    Thread Starter crzyhrse

    (@crzyhrse)

    6 months ago

    Gerard,

    Then WHY do I STILL receive this message (in blockquote below) from ShortPixel at the top of ShortPixel’s settings page and at the top of all media library related pages whenever the Phoenix Media Rename plugin is activated…???

    Both plugins updated to current, and confirmed as still happening just a few minutes ago…???

    The following plugins are not compatible with ShortPixel and may lead to unexpected results:
    Phoenix Media Rename Deactivate

    Here is a link to an actual screenshot of ShotPixel’s actual (and rather large) message banner on top of shorpixel’s settings page… It is identical to the message banner on top of media library pages when the Phoenix Media Rename plugin is activated..
    .
    https://www.spiritdesigns.life/wp-content/uploads/2021/01/shortpix.phoenix-scaled.jpg

    Perhaps you are not paying as much attention to what is going on as you would like to believe…???

    May you also have a good day…

    Plugin Support Gerard Blanco

    (@sixaxis)

    6 months ago

    Good morning, crzyhrse,

    We are here to help you. We are the first ones interested on having all issues solved, so if we tell you that we pay attention, you can believe us. There is no need to be disrespectful.

    What we know is that Phoenix Media Rename team contacted us some time ago asking for assistance in order to solve this issue. In fact, they told us something was fixed on their side. After that, we validated the fix, but we are still showing the message in case the user is using an old version of Phoenix Media Rename without the fix.

    Your next question is probably going to be “Why isn’t the message showing only for older version of Phoenix?”. The answer to that is that we are working on a new notification system that will allow us to do that 🙂 No ETA on this, though.

    And again, if you found the plugins not working properly, please tell us what we should do step by step.

    Thank you,

    Thread Starter crzyhrse

    (@crzyhrse)

    5 months, 1 week ago

    OK, because you ask, here it is, step by step…

    1- Resolve the issue that the warning keeps appearing in the backend…

    2- Mark this thread “Resolved”…

    Or in other words, stop doing the above backwards…

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.

Views