Support » Plugin: Gravity Forms HTML5 Placeholders » Incredibly weird path for .css and .js files produced

  • Resolved dekket

    (@dekket)


    I just had the weirdest problem that managed to disappear nearly all by itself…

    The fields for the placeholders didn’t show up, so I opened up Dev Tools and saw that the path for the .css and .js that the plugin required, was completely wrong. Instead of using the right path:
    http://[DOMAIN]/wp-content/plugins/gravityforms-html5-placeholders/css/gravityforms-placeholders-editor.css

    It created this interesting path:
    http://[DOMAIN]/wp-content/plugins/Volumes/Sites/Clients/WordPress/?ver=2.7.3#indev/[OTHER SITE]/wp-content/plugins/gravityforms-html5-placeholders/css/gravityforms-placeholders-editor.css

    So, uhm. That makes about zero sense.

    1. It starts off properly:
      http://[DOMAIN]/wp-content/plugins/
    2. Then it starts adding the full path from the system root:
      /Volumes/Sites/Clients/WordPress/
    3. For some reason, it adds ver=2.7.3 after this.
    4. Then, as if this wasn’t weird enough, it prints out a path that is not even part of the project, nor is it referenced ANYWHERE in my code:
      #indev/[OTHER SITE]/wp-content/plugins/gravityforms-html5-placeholders/css/gravityforms-placeholders-editor.css

    If the last part of the path is part of the current site I’m working on, or the other one, not sure.

    Anyways. I figured I should check the plugin code to give a better bug report. I decided to remove all of the path except $this->get_base_url() to see if that produced some interesting error. It didn’t. The path was correct. Weird.

    So I restored the code, hit refresh and voilá! It works as normal now.

    So in essence, I’ve change zero, and yet it fixed an incredibly weird error.

    Just FYI, I’m running MAMP Pro on Mac OS X Snow Leopard. PHP 5.3.x. WP4.1 and GF 1.8.x

    https://wordpress.org/plugins/gravityforms-html5-placeholders/

Viewing 1 replies (of 1 total)
  • Plugin Author iSoftware

    (@isoftware)

    Thank you for your input.

    We have tested this on MAMP Pro but could not reproduce this error. Should this issue come up again please let us know.

    iSoftware

Viewing 1 replies (of 1 total)
  • The topic ‘Incredibly weird path for .css and .js files produced’ is closed to new replies.