We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 25547
    • 61 Posts
    Quote from: Soda at Apr 16, 2008, 07:16 AM

    @rajfantastic are you knowing where you are ??:
    MODx Community Forums » Development & Coding » In Development » [snippet] Front End Document Manager (FDM) v0.1b
    I wrote many time that FDM is not ready for production !
    I think that the new one will be available for developpers only. >:(

    So we are not allowed to use it? Please release the next version openly as this is a really good snippet/
      • 6726
      • 7,075 Posts
      I’d say it’s not ready "as such" for production but can be used by advanced users & coders, I know I am not the only one using it "live"... It’s like MODx betas there are few things that need ironing out but nothing you can’t live with (at least for me).

      I sure can understand how it could make you want to selectively restrict the future release to developpers only but I think it would not make beta testing FDM better. Worst case scenario, make it available to the testing team only in the first stage...

      It’s the moderator’s role to keep people in line you shouldn’t have to do it (though you have every right to). But I sure understand the frustration (ask Coroico since he took on AjaxSearch, he’ll share yours !).

      I’ll make a note to the moderators board to enforce things a bit more strictly in the Development & Coding » In Development boards. Keep in mind we are currently re-inforcing our moderator team for the english boards smiley
        .: COO - Commerce Guys - Community Driven Innovation :.


        MODx est l'outil id
        • 27708 MODX Staff
        • 2,502 Posts
        I’ve been a little busy this week but I think that the reason people get so heated is that we all really like FDM. It kills NewsPublisher and while it is not a perfectly completed app. (Would MSFT ever release anything).

        As anything with user contributed scripts, users have to be aware that unless otherwise stated there is no promise of function or warranty. If the app doesn’t work in your application or on your stack don’t blame the dev. He/She developed it for a purpose and released it.

        Soda has built a tremendous addition and I think if someone wants to step up to the plate (read PHPdevs--not me) they would be welcomed.

        Lets all play nice.

        Cheers,

        Jay


          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. Blog ✦ Twitter ✦ LinkedIn ✦ GitHub
          • 25080
          • 175 Posts
          With FDM, can we add pictures to the document when we are created it ?
          I imagine this with a button "brows".

          I don’t find this parametter in the documentation....

          (sorry for my english)
            • 27708 MODX Staff
            • 2,502 Posts
            @Rikle_S

            I have done this using MaxiGallery on the same page. It is much easier but it is possible you just need to either use TinyMCE (see the directions on this thread) or create a TV yourself.

            Cheers,

            Jay
              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. Blog ✦ Twitter ✦ LinkedIn ✦ GitHub
              • 25080
              • 175 Posts
              I’ve just install MaxiGallerie this afternoon, and i was thinking this solution.

              I search how to tomorow.

              Thank you
                • 16892
                • 107 Posts
                I’m running MODx 0.9.6.1b under a WAMP installation.

                This is my FDM call:

                [!FDM? &parent=`27` &debug=`all` &eform_tpl=`fdmEform`!]


                I’m getting this error when I click edit or create:

                Fatal error: Non-static method CFDM::mergeFields() cannot be called statically in C:\sokkit\site\xxx\assets\snippets\eform\eform.inc.php on line 604


                Any help appreciated.

                  • 7455
                  • 2,204 Posts
                  I have a problem using the &editorpageid option, when I use it like this:
                  [!FDM? &eform_tpl=`eigenpaginaform` &canpost=`users` &parent=`9` &editorpageid=`72` &disableadd=`1`!]
                  I get hits error: FDM: When you use editorpageid parameter, you must fill the ’id’ parameter in the snippet call !
                  so I add &id=`[*id*]` the its working on the original page (source) but noting happends on the target.

                  It works if I do this: sorry it does not work I get the edit page but on saving it returns to the edit page (72) and it does not save or give any error, it does give me the button bar for that page)
                  [!FDM? &eform_tpl=`eigenpaginaform` &canpost=`users` &parent=`9` &editorpageid=`72` &disableadd=`1` &id=`343`!]

                  but what is not usable for me, I have several "source" pages all directing to editorpage 72.

                  with the previous version this worked but with the latest version it does not work without the id.
                    follow me on twitter: @dimmy01
                    • 7455
                    • 2,204 Posts
                    OK I solved some problems
                    The form does save now there was a change between the 1st version and the last version I used the name of the submit button needs to be fdmsubmit in the 0.1b version but that was not the case in the first version.

                    I left the &editorpage funktion for what it is now because its not working without problems.

                    Dimmy
                      follow me on twitter: @dimmy01
                      • 25080
                      • 175 Posts
                      Is there tutirial to use FDM with Maxiallery ? :/