We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 27708 MODX Staff
    • 2,502 Posts
    @dev_cw

    No,

    I decided I needed to move on with the project. It would be easy to remove the fURL check for the alias set by modifying that particular function to just set the name instead of checking fURL first.

    I am not a php expert and as I mentioned I haven’t time to fix it. I am already late on this project completion.

    All the best,

    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
      • 7231
      • 4,205 Posts
      Thanks for the info. I may wait to implement this once on the final server and just move on for now. I too am late with delivery. Back to work. grin
        [font=Verdana]Shane Sponagle | [wiki] Snippet Call Anatomy | MODx Developer Blog | [nettuts] Working With a Content Management Framework: MODx

        Something is happening here, but you don't know what it is.
        Do you, Mr. Jones? - [bob dylan]
        • 27708 MODX Staff
        • 2,502 Posts
        I have solved an number of problems now that I am on a production server.

        1. Alias Titles get created fine now that the fURL Check can be done. (This is a bug and needs to be dropped. Alias Titles should be set to page titles by default whether fURLs are enabled or not. Most MODx’rs dev on a local server and I certainly don’t need to set up fURLS on my local server as I don’t want to do it twice.

        2. For some reason and I am not sure if it is FDM or eForm that is the culprit but the placeholder is somehow dependent on the element’s "name" value. For instance, if you have [+content+] with name="content" it works. If you have [+content+] and name="blog_content" it won’t work. FDM can’t write the data on submit. Having these linked is doesn’t make sense but it is okay.

        3. You can use TinyMCE on a template or page that contains an element with the id #content. You can do it on of two ways:

        i) Change the TinyMCE init as it is shown in the FDM Documentation to read the following:
        tinyMCE.init({
        	theme : "advanced",
        	mode : "textareas"
        });

        This version will enable the editor on all textarea elements on the page.

        ii) Change the id and label of the element you wish to be used but make sure the name value is still "content" so you have a new label and id such as #blog_content and modify your TinyMCE init lines to read:
        tinyMCE.init({
        	theme : "advanced",
        	element : "blog_content"
        });


        This version will put the editor only on the element id #blog_content. As stated in the FDM Documentation, you can also use a comma separated list of ids for any elements you want to ad the editor to.

        @Soda,

        If you might change the TinyMCE call to the first one using the mode:textarea in the documentation that might make it less confusing and it would probably work well for most people just by installing it. For me and many others the use of a #content id is quite common to describe the main div in which we place all content on a site (this may not be an issue for designers in other languages).

        Also if you are interested in any assistence in helping with beefing up the documentation or in testing, I would really love to help you out as I know that you are refactoring but I feel that this is one of the most powerful snippets for my projects to date. Please PM me if you are interested or would just like me to send you updates to the docs and you can post them. Also I could clean up the form template (there is a some leftover French and a few formatting things that could make it a little cleaner).

        Sincerely and all the best,

        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
          • 10998
          • 7 Posts
          Hi,

          I keep getting an email from FDM, each time I add a document, saying:

          Document or chunk not found for template id= ’’

          What does this mean?

          One other thing, I’m using FDM for a blog, and I’m using Jot. It seems that when I use Jot and FDM on the same document, the word:

          @CODE:

          ...shows up just before the FDM buttons, how can I prevent this?

          Thank you in advanced
            • 27889
            • 415 Posts
            @ALL
            One baby later wink
            I’m back, I’m rewritting a new version of FDM for the ...... 0.9.6 ! It seems that this version will be in use for a long time. I have corrected some bugs and rewritting the logic to accelerate the page load. I will put here a new version soon.
            It’s difficult to satisfy everyone, but I’m trying.
            I don’t support TinyMce, there is a very good forum and documentation for this.

            @goatchild I think you don’t have a template filled, certainly, the thankyou parameter, if you don’t need email function you can disable it with the noemail parameter.
            For the @CODE displayed I don’t know have you the last version ? there was somes (solved) problem with @code, is it FDM or JOT which is displaying that ?

            @Smashingred
            Thank you for your work, can you send me your commented modifications in PM ?
            For the pubdate there is certainly a format problem, date are stored as integer in the db.


            EDIT: I’m adding an alias parameter to choose which kind of alias is used (tv, date, id...).
              MODx Sites & Prestations: http://dp-site.fr [Last MODx Site]
              MODx Repository: [HOME] [MetaTagsExtra] / Current Dev: [xFDM]
              • 27708 MODX Staff
              • 2,502 Posts
              @Soda,

              Congrats on the new addition to your family!

              I am working on a few other things but I will try to send over the rewrites/updates for you at PM when I have a chance.

              Thanks again for such a great snippet.

              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
                • 6726
                • 7,075 Posts
                Ditto : congrats and good luck with the first months wink !
                  .: COO - Commerce Guys - Community Driven Innovation :.


                  MODx est l'outil id
                  • 7231
                  • 4,205 Posts
                  Ditto?...This is the FDM post grin grin grin

                  Kidding aside, Congratulations Soda.

                  Interesting that you went for supporting 0.9.6. I agree it will be around for a while and it is a good idea. This is a great snippet and look forward to the new version.
                    [font=Verdana]Shane Sponagle | [wiki] Snippet Call Anatomy | MODx Developer Blog | [nettuts] Working With a Content Management Framework: MODx

                    Something is happening here, but you don't know what it is.
                    Do you, Mr. Jones? - [bob dylan]
                    • 10076
                    • 1,024 Posts
                    c´est super,

                    congrets and enjoy!

                      • 27889
                      • 415 Posts
                      Thanks you for your messages.
                      The new version is in the first post.
                        MODx Sites & Prestations: http://dp-site.fr [Last MODx Site]
                        MODx Repository: [HOME] [MetaTagsExtra] / Current Dev: [xFDM]