There is a fuel/index.php file that has the redirect to the fuel/start controller file. Are you able to get a normal CodeIgniter installation to work with .htaccess?
I'm assuming you are referring to this module correct?
https://github.com/daylightstudio/FUEL-CMS-Search
There is an "exclude" parameter you can set as either an array of pages or a regular expression string (it also honors the robots.txt file). Al…
Does anything appear when you simply just do the following:
<?php echo fuel_nav() ?>
When you say documentation, do you mean these pages:
http://docs.getfuelcms.com/general/navigation
http://docs.getfuelcms.com/libraries/fuel_navigation#func_r…
There is a property you can set on your model called "auto_encode_entities" that by default is set to TRUE which means it will convert characters like that to HTML entities. You can try setting that to FALSE, or be more specific and specify an array…
There currently is not a newsletter module. However, there is a Forms module in beta that can be found at the URL below that captures information into a database. The part missing is the sending out of emails from the system. However, we would norma…
That configuration is part of CI and it looks like the code doesn't rewrite <? tags, just <?= tags
https://github.com/bcit-ci/CodeIgniter/blob/develop/system/core/Loader.php
If you do a print_obj() on $plant, what does it return? The print_obj() function is found in the utility helper and good for debugging database records because it prevents the infinite loop due to the CI references.
Also if you just use fuel_model(…
The active class is set by specifying the active parameter which correlates to the location/id value. So if you wanted to specify the "catalog/myrecord" as active, you would need to set that as active. There is also a parameter to "cascade_selected"…
Did you merge in the develop branch? This was the change made:
https://github.com/daylightstudio/FUEL-CMS/commit/b367cf1889e4cc1d20b8b38dae62566ce50be3fd
Also, you need to add a closing quote after the ending {/if}
…
That looks to be a bug in the php_to_template_syntax function. I just pushed a fix for that in the develop branch for you to test out:
https://github.com/daylightstudio/FUEL-CMS/tree/develop
Try changing the syntax to something like:
About US
FUEL tries to change PHP code to the templating syntax when you save it in the CMS as best it can but it sometimes doesn't quite work and you need to tweak it:…
If you use the fuel_nav function, you can set the "active" parameter to uri_segment(1) like so:
<?=fuel_nav(array('active' => uri_segment(1)......))?>
Regarding the error, what was the error being displayed? Does it go away if you change $…
A few questions:
1. What are your'use_page_cache' in FUEL? The default found in fuel/modules/fuel/config/fuel.php is the following but can be overwritten in your fuel/application/config/MY_fuel.php file:
// turn on cache. Can be TRUE/FALSE or cms $c…
FUEL does overwrite the Lang class using the HMVC library and that file is located in fuel/application/third_party/MX/Lang.php. However, I think you'd run into the same problem with the native CI Lange class as well. It only loads the same language …
The "role" attribute isn't supported with fuel_nav, however, I think you can get pretty close with the following:
views/_variables/nav.php
$nav['work'] = array('label' =>'What We Wo'); $nav['people'] = array('label' =>'Get Involved', 'attrib…
Are you using the fuel/application/views/_variables/nav.php file and if so, what does it look like?
The fuel/modules/fuel/libraries/Menu.php class and the fuel/modules/fuel/libraries/Fuel_navigation.php class are the ones that changed but if you up…
The base_module_model has an export_data method you can use to get the data into a CSV format. This method is used if you set "exportable" in the MY_fuel_modules.php file for your particular projectwise module.
If you are doing it outside of the mo…
In this case, since $sections is actually the field input, you would need to add an echo fuel_edit('sections') like the following:
<?=fuel_var('h1', ''); ?> <?php echo fuel_edit('sections');?> <?php foreach($sections as $section) : …
I'm not quite sure I follow but will give it a shot.
All pages created in the CMS get passed to the fuel/modules/fuel/controllers/page_router controller (see the routes config). This works only if there is no controller specified with the same URI …