On March 26, 2019 we launched new MODX Forums. Please join us at the new MODX Community Forums.
Subscribe: RSS
  • After installing 2.3.4 on one of my sites i created some resources and tried to order them via drag-n-drop i got the message "target not set".

    So i was delighted to see 2.3.5 with in the changelog the mentioning of the drag-n-drop fix. Just installed it. But the error is still present. Any ideas?

    Already emptied cache folder (deleted all files and subfolders)

    System:
    - Advanced install
    - PHP 5.5.26
    - MySQL 5.6.25
    - Apache 2.4.12

    This question has been answered by mintnl. See the first response.

      Addict since 2012....
    • Be sure to force reload the cache in your web browser. Chances are the js is cached. If not and you can reproduce in more than one browser, it would suggest that this is a bug needing a fix.

        Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup magician. BlogTwitterLinkedInGitHub
      • Hi Jay,

        I did the following:
        - Cleared cache
        - Flushed sessions
        - Removed browsercache

        But the error still exists in:
        - Chrome for Mac
        - Safari for Mac
        - Chrome for Windows
        - Firefox for Windows
        - IE 10 for Windows
          Addict since 2012....
        • after upgrading from 2.3.4 to 2.3.5 drag/drop in the resource-tree is working again, for me
            -------------------------------

            you can buy me a beer, if you like MIGX

            http://webcmsolutions.de/migx.html

            Thanks!
          • mintnl, did you delete the core/cache directory on the file system? Something isn't right. I'd also suggest checking to see if there are errors or 400s in your web inspector in Chrome. This is definitely unusual behaviour.

              Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup magician. BlogTwitterLinkedInGitHub
            • discuss.answer
              Hi Jay,

              Finally got it working normally. Pheew.... Thanx

              - I cleared MODX cache
              - Flushed sessions
              - Delete all files and folders in core/cache
              - Cleared all browsercache
              - Re-installed 2.3.5 (guess that is the one that didi it smiley )

                Addict since 2012....
              • I've been having this issue since 2.3.5 as well. Today I updated to 2.4, but that did not fix it.

                I also:
                - I cleared MODX cache
                - Flushed sessions
                - Delete all files and folders in core/cache
                - Cleared all browsercache
                - Re-installed 2.4

                But am still having this issue.

                Has anybody found a reliable solution?
                • I found this issue came in 2.3.4pl for me. I'm still searching for a solution.
                  • Quote from: dave-b at Aug 12, 2016, 08:35 AM
                    I found this issue came in 2.3.4pl for me. I'm still searching for a solution.

                    I finally found a fix to this issue.

                    I updated to 2.5.1pl using UpgradeMODX extra and then deleted the manager folder, which had a custom name, and then replaced it with a fresh one from the 2.5.1pl zip

                    :-)