Are you referring to the 1.0 beta? If so, you can do that by adding a "settings" array that uses Form_builder syntax for form fields in the settings area. The blog.php config file for 1.0 has an example:
https://github.com/daylightstudio/FUEL-CMS-Bl…
That would be great. I've used Mustache before and Twig is pretty popular (do people use Smarty anymore)?.
To be honest, I only use the templating syntax when I really need to and extract out more complicated logic into blocks that I can pass param…
Not immediately but it looks like we'll need to. Out of curiosity, do you have a preference for templating languages (trying to get a gauge as to where to make the investment)?
Does the inline edit work correctly for the publications module if you access it directly? If not, what does your console say in terms of the URL it is trying to access?
You would most likely need to create your own javascript to trigger a modal. FUEL uses the jqModal jquery plugin to do it's modal windows. That means you have access to use it in your custom javascript code though:
http://dev.iceburg.net/jquery/jqMo…
There currently isn't a way to prevent nested inline edits. However, I am having trouble replicating that here. It should give you another window, slightly smaller, but nested on top of it (it could be done with Javascript though by testing if the c…
Try this syntax (note the slight difference in the array):
public $has_many = array( 'articles' => array('model' => array(NEWSLETTER_FOLDER => 'articles_model'), 'order' => 'precedence ASC'));
The clearing on save should be fixed now. That is a recent regression bug. With regards to the sorting, I'm having a tough time replicating that error. Does it work if you use a different column?
The validate advanced module may be helpful to look at. It has a fuel/modules/validate/assets/ValidateController.js file which is call from with the fuel/modules/validate/views/validate.php view file. The "validate" method in the javascript controll…
There are a few other things in the application directory like the extended core, library, and helper files as well as the config files (e.g. MY_fuel.php, MY_fuel_layouts.php MY_fuel_modules.php). The core fuel files are in the fuel/modules/fuel fol…
For that to be run in 0.93, the "add_edit" method on the BaseFuelController.js file needs to be run. This is the default method run if you are adding or editing a simple module. Have you created your own controller for your advanced module? If so, y…
Where would the index.php bootstrap file point to... to the fuel installation or the existing CI installation? If you are doing something in the .htaccess or index.php file to route things through a single bootstrap, it's possible that you could get…
You can set the "icon_class" parameter for the module. However, by default, it should be using the module_uri value to generate the icon class just like the blogs does. Did you change the other module's module_uri's respectively?
'module_uri' => …
I misread what you stated and interpreted it as a form being rendered on the front end. For the back end, The 1.0 beta uses a newer version of CKEditor and has improved integration with asset uploading and links. Adding the class "wysiwyg" should wo…
The model_location value is indeed incorrect and should be set to "newsletter". I'll look into that issue. It looks like you may also need to change the module_uri value:
'module_uri' => 'newsletter/publications',
The wysiwyg class only works in the CMS and not on the front end because the javascript code to render the CKEditor box isn't loaded. You would need to add your own code for the front end to have a CKEditor field work.
Image uploads aren't supported by the blog settings controller (neither are they in the FUEL 1.0 beta). The image uploads work for controllers that extend the module controller and the settings controller does not.
So if you debug the $_POST value on line 22 of the settings.php controller file, do you see that value in there? Also, I believe the 'type' value should be removed from $fields['top_image'] so as to give you a text field.
Also, as an FYI, in the 1.…