Support » Plugin: Download Monitor » Download Monitor endpoint is already in use by a page or post.

  • Resolved gb24


    On the Settings page I see an error message: “The Download Monitor endpoint is already in use by a page or post. Please change the endpoint to something else.”

    Version: 4.5.0

    Adding and viewing downloads appears to work properly.

    I have no other download managers installed or other plugins which would use this endpoint.


    • This topic was modified 4 months ago by gb24. Reason: add version
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author raldea89


    Hello @gb24 ,

    Could you verify please that you do not have any pages/posts named Download ( they may have been previously named and changed afterwards, but the URL slug found when editing the page is still download ) ?

    Kind Regards!

    Thread Starter gb24


    I found a file, “download.jpg”, in my Media Library with title “download”. Here’s what I did:

    Media Library does not have the capability to change the permalink, so I changed the media item title to “download-test”. I continued to see the error message.

    It seemed I needed to change the actual post_name so I updated wp_posts.post_name to “download-test” in the mysql db. After doing this, the error message was no longer displayed.

    So I had a media library item with post_name “download” which “interfered” with the Download Monitor endpoint in some way. How could Download Monitor prevent this kind of issue in the future?

    Other than the error message, what errors or problems did/could this cause? I didn’t see any problems with Download Monitor.

    This resolves my issue with the error message, but I would be interested in your response to my questions above.

    Thank you

    Plugin Support beatrice12


    Hello @gb24,

    Unfortunately, this is a bug. I opened a ticket with our development team and we will solve this in our future update. Here is the ticket so you can see the progress:

    Please do not worry as this this is a bug and the error should only appear if it founds a post or a page.


    • This reply was modified 3 months, 3 weeks ago by beatrice12.
Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.