Title: Red Warning message
Last modified: October 30, 2022

---

# Red Warning message

 *  [tfrank77](https://wordpress.org/support/users/tfrank77/)
 * (@tfrank77)
 * [3 years, 7 months ago](https://wordpress.org/support/topic/red-warning-message/)
 * Hi,
 * It sounds a bit odd, but I think it’s a bug.
 * I got a red warning (screenshot) whenever I started the batch renaming with the
   bottom ‘Apply’ button in the media library. The renaming is fine after finished.
   
   There is no warning if I use the top ‘Apply’ button. But the renaming is fine
   in both cases.
 * > [View post on imgur.com](https://imgur.com/xOBmYSh)
 * I hope it makes sense. 🙂

Viewing 1 replies (of 1 total)

 *  Plugin Author [crossi72](https://wordpress.org/support/users/crossi72/)
 * (@crossi72)
 * [3 years, 7 months ago](https://wordpress.org/support/topic/red-warning-message/#post-16161801)
 * Hi [@tfrank77](https://wordpress.org/support/users/tfrank77/),
    this is quite
   strange: those buttons are equal, the plugin doesn’t know which one has been 
   pressed.
 * Can you tell me which other plugins are active in your site?
 * Thank you for reporting
    C.

Viewing 1 replies (of 1 total)

The topic ‘Red Warning message’ is closed to new replies.

 * ![](https://ps.w.org/phoenix-media-rename/assets/icon-256x256.png?rev=3120623)
 * [Phoenix Media Rename](https://wordpress.org/plugins/phoenix-media-rename/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/phoenix-media-rename/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/phoenix-media-rename/)
 * [Active Topics](https://wordpress.org/support/plugin/phoenix-media-rename/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/phoenix-media-rename/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/phoenix-media-rename/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [crossi72](https://wordpress.org/support/users/crossi72/)
 * Last activity: [3 years, 7 months ago](https://wordpress.org/support/topic/red-warning-message/#post-16161801)
 * Status: not resolved