That seems more like a module specific permission error. I can't think of anything that FUEL is to prevent iframes like that. You will need to have a proper session and permissions to view the page though (which it looks like based on the error, is …
It looks like the paths are relative. When you view source, what do you see for the paths? Is there a reason you didn't use the css and js properties in the image_selector array? In your case, you should be able to do something like the following:
…
You can try something like the following within your list_items method:
if ($this->input->get_post('country')) { $this->db->group_start(); // <- Optional but ensures that the query condition is contained $this->db->wh…
You should be able to put the folder at your web root and browse to it like any static website in a subfolder. If you are using Apache, the .htaccess rule will first look for a folder/file path and if it doesn't exist, it gets routed through FUEL. …
That makes sense. The _session_csrf uses native $_SESSION instead of CI's session (see Fuel_base_controller). Could potentially be ported to use $CI's session.
One potential workaround may be to create a safe_htmlentities() function in your fuel/application/helpers/my_helper.php which should overwrite the built-in function but in your case removes the $sanitize section:
/** * Safely converts a string's…
The disabled method reverts it to essentially how it was before where it would just disable scripts. Are you needing script tags to be inserted in your input form fields in the CMS? If so, I would recommend putting that logic in your template (which…
Yeah... Purifier is like that aunt at Thanksgiving... you love her and glad she's there but she can be a bit obnoxious and annoying. I've pushed an "enabled" feature to the config on the dev branch if you wish to essentially revert it to before puri…
The CMS page should take precedence over the home.php view file. Also, regarding the nav, if you have a single entry in the CMS then that will take precedence over anything in the _variables/nav.php file.
The index of the styles array indicates the nested depth to apply the styles:
<?php echo fuel_nav(array('container_tag_id' => 'topmenu', 'item_id_prefix' => 'topmenu_', 'styles' => array( 0 => 'level1', 1 => 'level2'))); ?>
Did you set this up in a fuel/application/views/_variables/articles.php file?
$vars['view'] = 'articles';
Also, is the page redirecting or displaying the wrong view?
I'm not quite sure I follow. For FUEL to work, you would need to have a database table setup specifically for the module. In this case using an external REST/JSON API, you would need to sync your external data to and from it. You could using the on_…
Maybe there is something with the Session expiring. Have you tried setting the $config['sess_save_path']=... in the CI fuel/application/config/config.php file? This sets the path to where sessions are saved (must be writable).
Is this field in the Pages module or your own Simple Module? If it's in your own Simple Module, you can try setting the sanitizing options like so:
In MY_fuel_modules.php
$config['modules']['my_module'] = array( .... 'sanitize_input'…
Take a look at the fuel/application/config/purifier.php settings. By default, there should be a couple iframe specific rules that are commented out:
'HTML.SafeIframe' => TRUE, // For iframes 'URI.SafeIframeRegexp' => '%^(http:/…
When you said tried changing it did you mean to the following:
$fields['url_select'] = array('type' => 'select2', 'value' => $this->input->get_post('url_select', TRUE), 'label' => $select_label, 'type' => 'select', 'options' =&g…