Support » Plugin: WP Original Media Path » Please Explain Further “Crush” the File of Another Site

  • Resolved Joe Banks


    In your sticky post about version 2, you stated:

    The concern, come that a user can “crush” the file of another site and suddenly it is not good.

    The question: Could you please go into additional detail about what this means?


    After having your plugin active and in use for 2 years on our multisites, we recently had (with the 2.0 update) our entire multisite upload_path and upload_url_path values changes to incorrect values, apparently by your plugin, and I am working to explain what happened in a report to our department.

    Example, for every site on the multisite:

    Upload URL Path set to: (for every site #)

    Upload Path set to:
    wp-content/uploads/sites/# (for every site #)

    Thanks in advance.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author RVOLA


    Hello Joe

    I am currently on holiday, I do the necessary to answer you more details on my return in early July. Version 2.1.1 does not break the previous settings.

    Plugin Author RVOLA


    Hello Joe,

    Before, I am sorry that you have encountered worries. Trying to do my best, I unfortunately do not answer all the problems of each user.

    I received several requests from users asking me for multi-site support.
    After several tests, I noticed that the plugin always behaves in the following way: it adds “sites/” to the end of the URL of the uploads folder.

    I tried to do it properly to tell WordPress to stop adding “site/” to the end of the URL.

    During these tests, I noticed that a child site could choose its media location.
    In my example, let’s say a user put the following media field: “”.
    With the plug-in it was totally possible to add to another site the same field which has the consequence of sending media in the file of “toto”.

    Noting a serious problem of integrity I prefer in version 2.0.0 to “stop” the support (with a message on the dashboard and the WordPress repository) for the non-compatibility with the multisites.

    While waiting for a more experienced multisite person to modify the code, I found this solution more “safe”.

    It is entirely possible to use version 1.6.1 which keeps the behavior “classic”.

    The version 2.X is born from the same and perpetual question of the users who can not easily configure the 2 fields.

    do not hesitate to get back to me

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Please Explain Further “Crush” the File of Another Site’ is closed to new replies.