I think I found the issue and it's a bug in the code. I've posted a fix in the develop branch (which you can merge in with GIT):
https://github.com/daylightstudio/FUEL-CMS/commit/a71d525e64c562e4854621e69194ac2189a1ced5
That's correct about layouts to some extent. There are block layouts that can be used for modules. But the template field type may also be of some use for you because you could essentially create a repeatable template that has all the fields you nee…
Hmm... I wasn't able to replicate that issue exactly, however, I did notice that the $_GET parameters were taking precedence over some of the $_POST parameters on save. I've reversed that and pushed a change to the develop branch to see if that fixe…
Try adding the following to the MY_fuel.php 'max_page_params' config value:
$config['max_page_params'] = array('about-us/board-of-directors/enterprises/' => 1);
This line causes suspicion for me:
/var/www/webapp/fuel/application/tests-tu/_ci_phpunit_test/replacing/core/Loader.php:363
Fuel has it's own version of the Loader class that has the module_load methods in it. It seems that CI PHP unit is replacing…
The $config['blog']['uri'] config should be where that URI change is made. Is it possible that there is a saved setting in the admin under Settings > Blog?
What version of FUEL are you using (check fuel/modules/fuel/config/fuel_constants.php)?
Also, FUEL has it's module that leverages the built in testing CI library:
https://www.getfuelcms.com/developers
http://docs.getfuelcms.com/modules/tester
The block field will create an array variable with the name of the variable being the name of the field (e.g. menu_block), the keys being the field names, and the values being the values submitted in the form:
<?=$menu_block['page_active_top_menu…
I'm not quite sure I totally understand but will give it a shot. It sounds like you want to customize the options on the left side to be something other then the default the has_many provides you which is the options_list method on the foreign model…
There is a line (26) of code in the views/themes/default/post.php that pulls in Javascript that will need to also be moved to the footer:
<?=js('comment_reply', BLOG_FOLDER)?>
What's likely happening is that if it's unchecked, it will not be passed at all in the $_POST array. If it's not seen in the $_POST, then it won't trigger it to be 0. To help with this issue, there is a public $boolean_fields property you can set on…
What version of PHP are you on and do you have short_tags enabled? Also, are there no spaces at the top of the page and/or the fuel/application/views/_variables/global.php. The URL with the route in place should be sitemap.xml without the underscore…
The "folder" parameter is relative to the main assets/ folder and uploads target that path. So the NEWSLETTER_PATH . 'assets/images/' value won't work. If you want to target a different assets folder entirely for upload, you can try the parameter 'u…
That looks to indeed be a bug. I've posted a fix in the develop branch:
https://github.com/daylightstudio/FUEL-CMS/commit/bd0ebcfacc5330dd749094d37873a5316d17c227