This sounds like it may be something in your HTML code. If you are able to see 4 in the source code, perhaps there is a javascript or open HTML tag preventing the other ones from loading? Or is there some other PHP error being displayed on the page …
Basically you have your header file look for a variable called $css (first piece of code above). This should be located under the html -> head tag. That variable's value will be the name of the CSS file you want to include and should be located i…
FUEL will automatically detect if it's a serialized/JSON data and decode it. Certain field types, such as the "template" field type need an array structure to render. you could try adding a pre_process parameter:
'pos_size' => array('label' =>…
You can set a variable called $css and then in your header.php file do something like the following:
<?php if (!empty($css)) : echo css($css); endif; ?>
In your specific view file you can use fuel_set_var at the top of your view file:
<?php…
Are the slug values different for each record and am assuming the preview_path is different between the modules correct? If you call the following in one of your view files, what gets displayed:
$module = $this->fuel->modules->get('news'); …
It uses the directory_to_array function which may return the files in a different manner. In the Fuel_assets::dir_files() method, does it work if you do the following:
public function dir_files($folder, $recursive = FALSE, $append_path = FALSE) { $…
What is the preview path being used (e.g. news/{slug})? The Fuel_module::pages() method is what is used to determine the page list for a module (fuel/modules/fuel/libraries/Fuel_modules.php).
Is it just being outputted normally in your view file:
<?=$record->spec_fr?>
If so, is spec_fr overwritten in the record model at all and I'm assuming it's inheriting from the Base_module_record class correct?
Sure. This can be added as a separate module to your FUEL installation. You can download the module here and install it in the fuel/modules/user_guide folder (or follow the installation instructions):
https://github.com/daylightstudio/FUEL-CMS-User-…
That would require some modification to the core files in particular the jquery.markitup.set.js file and the CKEditor fuel/modules/fuel/assets/js/editors/fuellink/plugin.js file as well as the fuel/modules/fuel/controllers/pages.php file under the "…
Hmm... I'm having a hard time replicating this issue. In the Fuel_navigation::render method on line 225 should automatically do the lookup in the CMS for the appropriate active ID and use that instead of the nav_key value. Is that happening in your …
It could be the "sanitize_input" setting which by default uses xss_clean. Try adding this to your module configuration:
'sanitize_input' => array('template','php'),
If you are using the foreign_keys property on the model, it requires it to have the suffix of "_id" to automatically work. You can always set up a property in your record model to lazy load in the object like so:
function loc_parent() { return …
How are you generating the menu? If you use the fuel_nav() function, it maps to the Fuel_navigation::render() method and in it it uses the fuel_navigation_model::find_all_by_group() method which returns the nav_key as the array key and not an intege…
If you are using the CMS to generate the menu structure, you need to grab the ID value of the menu item to set as the "active" value. Using something like $this->fuel->navigation->model()->find_by_nav_key('mylocation') should return the …
Load the fuel_schema.sql into a new MySQL database. You can use phpMyAdmin or Sequel Pro to setup the database. Then set the configuration accordingly in the fuel/application/config/database.php file.
Unfortunately there currently isn't a way to cache the data. If your assets can be broken into sub folders, I would try doing that and then in your models or layouts, specify the "folder" parameter in your form_fields method so you only target that …
What version of FUEL is it? There was an issue with this a few patch versions ago that should have resolved something that sounds similar to your issue.
Unfortunately "active" and "published" are reserved field names that have special meaning in FUEL. Can you change the fields in your model? You could create a record model method to act as an alias of "active" that could return to the new active fie…