Thanks for the report. That's indeed a bug. I just posted a fix. I added 'user_name' to the unique_fields model property:
https://github.com/daylightstudio/FUEL-CMS/commit/31db27c63ed3f3a48d45372274f6f1475f99b411
Does it sort it correctly if you use just find_all_array to set $song_setlist? Also, you can debug the query after you call it by using $CI->songs_to_gigs_model->debug_query() (I use that all the time).
If .htaccess works, then this link should take you to a login page (note that index.php is not in the URL):
http://localhost/test/fuel/login/5a6e566c62413d3d
Here is a link regarding getting .htaccess working on MAMP:
http://drupal.org/node/142972
…
To do it in MY_fuel.php, you would essentially reset the variable, copy over what's currently in the main FUEL config and organize it like you want. MY_fuel.php get's included in at the bottom of fuel.php and will overwrite any similar values. Howev…
You can control the layout via the variables just like you have there. However, the body of the page is controlled by the URI location / view location relationship, if you are indeed using FUEL's "opt-in controller" method (which it looks like you a…
I just posted that change to the user_lang() method to the main repo which will at least keep the error from showing up.
bbotella, as for the other errors, I'm not sure if they are related. A couple questions to help debug:
1. Did you download th…
This looks great and thanks for the willingness to contribute. I'd be interested in checking it out. I ran into this one as well that I thought I'd mention which may be of use.
http://github.com/simogeo/Filemanager/archives/master
You would need to recreate the $config['nav'] in the order you want which is found on the fuel/modules/fuel/config/fuel.php config file. The ordering is just the natural order of the the associative array.
Actually, this is a Vanilla Forums installation. FUEL doesn't have a forum module at the moment. FUEL has it's own user management system it uses to grant permissions to certain areas but it is not a separate module per se. I have seen a few out the…
I just posted a fix for this issue so please try it out when you have a moment and let me know if you encounter any more issues.
https://github.com/daylightstudio/FUEL-CMS/commit/5ed39c181172baad98d6bd4ada8212c84ef5bfff
Are you wanting $nav_params['parent'] to return just their immediate children or cascade down to their grandchildren? Also, would the render_type = 'array' work for what you need it for?
Hmm... I haven't seen that before. Could you try replacing the Fuel_auth::user_lang() method with the following and see if the problem goes away. If so, I'll make the update to the repo:
function user_lang() { $default_lang = $this->_CI->conf…
The body variable gets set by FUEL based on the location specified (e.g. contact). If you create a view file located at fuel/application/views/contact.php, it should work.
Did the HTML above get cut out (you can use the code HTML tag)?
Try adding the following to your MY_fuel_modules.php to the module name you are using:
'sanitize_input' => array('template','php'),
By default, it uses the xss_clean which may caus…
I just tried it with the following MY_fuel.php configuration change and it seemed to work (note the addition to the toolbar and the extraPlugins):
$config['ck_editor_settings'] = array( 'toolbar' => array( //array('Source'), array('Bold','…
For this particular module, I'd create an "advanced module" like the seo, or validate modules, with it's own controller and view to display the form and process the data:
http://www.getfuelcms.com/user_guide/modules/advanced
With regards to the sav…
Hmm. I'm not able to replicate the issue on the most recent version. Do you have the latest? If you do, can you use Firefox to check what comes back with the AJAX response after you click it?
You can change the $config['ck_editor_settings'] settings in fuel/application/config/MY_fuel.php. That gets converted to a JSON array that is used for the CKEditor config.
You can just set it in the MY_fuel.php file (I should have said that instead of the main fuel config file). The value in there will overwrite the default values in the fuel/modules/fuel/config/fuel.php file.
I just posted an update that will add an unsupported error message when someone tries to upload a filetype that is not supported by the particular asset folder type. The "accept" parameter is used on the front end to limit a users ability to select …
You can try using the sitevariables_model directly like so:
$this->load->module_model(FUEL_FOLDER, 'sitevariables_model'); $email = $this->sitevariables_model->find_one(array('name' => 'email_address'));
That is a Dwoo templating error message. FUEL tries to translate PHP code to Dwoo templating syntax but doesn't get it all. I'd look for something like {var(...)} in the newly importing page code.