WordPress 5.3 custom upload path

  • andy14

    (@andy14)


    6 years, 6 months ago

    Since updating to WordPress 5.3 the custom upload path is no longer respected. Previously, I set both the Store uploads in this folder and Full URL path to files (in the media settings) values to media and media.domain.com respectively. This sent uploads into a media folder and served them from that custom domain.

    I’m seeing broken images in both the admin and on the frontend because WP is overriding that path with it’s own default value: https://domain.com/uploads/image.jpg. I’ve confirmed uploads are going into the media folder so it looks like it’s the path variable that isn’t respected here. Additionally, deleting images doesn’t seem to remove them from my custom uploads folder as it did before.

    In addition, I’ve disabled the big_image_size_threshold filter so that WP doesn’t natively process my images. That didn’t fix things.

    Is there something else I need to do here? Is this functionality no longer possible? Any advice would be much appreciated.

    • This topic was modified 6 years, 6 months ago by andy14.
Viewing 7 replies - 1 through 7 (of 7 total)
  • eiland

    (@eiland)

    6 years, 6 months ago

    Same here, our upload location is ‘../uploads’ and today, with 5.3 installed, it refused to create folder /uploads/2019/11
    ‘Unable to create directory ../2019/11. Is its parent directory writable by the server?’
    I could create it by hand though.

    The reasons for or relative location is that the wordpress files reside in /wp but i want to host the images in the root/uploads. The blog is also governing the root. I just didnt want to mix wordpress wih a load of other files.

    johannrobinson

    (@johannrobinson)

    6 years, 6 months ago

    Me sucede lo mismo: “No se pudo crear el directorio wp-content/uploads/2019/11. Asegúrese de que el servidor tiene permisos de escritura para el directorio superior.”

    Anonymous User 92042

    (@anonymized-92042)

    6 years, 5 months ago

    I’m using the same setup as @andy14 and @eiland and I’m also seeing this problem when trying upload images today (Dec 2, so a new “12” directory needs to be created).

    Permissions are fine and this site has been working this way for 5+ years. I updated to 5.3 last week.

    Manually creating the “12” directory with the correct permissions allows images to upload normally.

    CheeWah

    (@cwchan)

    6 years, 5 months ago

    I am also having similar problem when using NextCellent to create image gallery. The new directory cannot be created. The plugins has been working fine for years and after updating to WordPress 5.3, I am not able to create directory in custom path. Any help would be grateful.

    mikusv

    (@mikusv)

    6 years, 4 months ago

    Had the same issue. Resolved by removing UPLOADS and just setting the path with WP_CONTENT_DIR and WP_CONTENT_URL.

    Anonymous User 92042

    (@anonymized-92042)

    6 years, 4 months ago

    For the record, on my site the WP_CONTENT_DIR and WP_CONTENT_URL constants were set at the time the problem occurred. The UPLOADS constant was not set (I wasn’t aware of it until now).

    gmisterk

    (@gmisterk)

    6 years, 4 months ago

    i have the same problem with wp 5.3

    and i use DIVI editor, images are visible in the editor, but not in frontend website :

    hhtp://www.mysite.com/mywp/mypage it don’t show my image
    but if i use this url :
    hhtp://www.mysite.com/mywp/myspage/?et_fb=1 it active divi editor and i can see my image

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘WordPress 5.3 custom upload path’ is closed to new replies.