Broken image paths, local dev environment

  • Wanted to point out a bug, hopefully to get it fixed or have you guys point me in the direction of a viable solution. I run MAMP for local development, with local projects URLs as:

    projectname:8888

    Consequently, images added to table cells are given paths as:

    /8888/wp-content/uploads/etc/etc

    I’ve traced this in the plugin files to /inc/admin/element-classes/element-scripts/image-element.js, line 39. The image src is split at the ‘:’ character, to return a clean path. But the port number in MAMP project domains busts this, resulting in 404s. Can this logic be tweaked in next release to be sure it’s using the initial protocol colon?

  • The topic ‘Broken image paths, local dev environment’ is closed to new replies.