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