We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 14883 ☆ A M B ☆
    • 450 Posts
    OK. First read this: http://modxcms.com/forums/index.php/topic,51360.0.html

    Um, yeah. Funny story... It turns out, a while back, I created a softlink in my production server (long before I installed MODx there), linking to the /assets directory on my development server (the two domains & MODx installations referred to are virtual hosts on the same physical server).

    I did that because I have /js, /css, /images subdirectories under /assets. We moved a few small sites into production by just copying/pasting the rendered HTML source code of the files and saving them as static files on the production server. Worked great, except that the images/js/css stuff was broken. So I just made a virtual /assets directory, and everything was A-OK.

    Didn’t really think about how this might affect a MODx installation on the production server - honestly, I was ignorant to the fact that there was anything besides my own content in there.

    So now "its as though Provisioner thinks it is actually installed on the remote server" begins to make sense.

    Now that I figured this out, I thought I knew how to solve it. I deleted the /assets soft link, created a real /assets directory, and created individual softlinks within it to point to my /assets/js, /assets/images, etc. This way, I figured, there’d be a real /assets/components directory on the production server for the Provisioner files to go in to.

    So, I created the physical /assets directory, then uninstalled and reinstalled Provisioner on the production server.

    But I got the exact same results... POST requests for /assets/components/provisioner/connector.php showing up on the remote server’s logs.

    Huh. Must be a caching thing, I thought.

    So I uninstalled & reinstalled Revo RC-3 on the production server... reinstalled Provisioner... bounced Apache...

    And still got the same outcome.

    Now I have no idea what to make of the situation. The only thing that makes any sense is that maybe there is some sort of filesystem caching going on (which would be completely outside the scope of my comprehension & understanding)... such that the old mapping info about the softlink that I deleted is somehow persisting even after deleting it, creating a physical directory with the same name, completely uninstalling & reinstalling MODx and bouncing Apache.

    Does that even make sense as a theory?

    Or maybe the caching is at the PHP level?

    I don’t know what to think anymore.
      • 14883 ☆ A M B ☆
      • 450 Posts
      In addition to the softlink, I also had a ProxyPass directive linking the new /assets folder to the old one. Things cleared up beautifully once I deleted that and bounced Apache.

      I will now bludgeon myself with eight sharp pencils.
        • 28215
        • 4,149 Posts
        Unacceptable. Your punishment is to start blogging again.
          shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com