Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Yeah, I was having the same problem. We thought that we may have fixed it within advanced custom fields’ image field code by changing a class. This brought up the correct interface, but we still were having problems with the image being submitted.

    Anyone else having this issue?

    jdrefahl

    (@jdrefahl)

    I’ve recently came across the same bug as Sladestyle.

    I’ve run into the exact same situation. From what I can tell when you have deployed a WP under a subdirectory, in the case of my its http://localhost/wordpress/ any site I cloned will not be linked correctly in the Admin bar. The only way to access the cloned site it seems to to directly enter in the URL.

    I have tried Never Settle’s work around where you should only put in the site name and not the full path to the deployment, but I still get the same behavior. The new Cloned site shows up in all the admin interfaces, however all the menus seemed to be linked bac k to the originally cloned site. I can access the site via typing the full path of the URL, but due to the menuing in WordPress, this makes it un-usable for any sort of deployment if you need to deploy under a sub-directory.

    Its probably best that you set up some Virtual Hosts in your Apache HTTPD.CONF file. You can find a lot of information online about how to do that. This way you can get around the whole subfolder in your path issue.

    Thanks
    John

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