Is the home page a view file at fuel/application/views/home.php or is it in the DB under the Pages module with the location of home?
If the latter, is the fuel/application/config/MY_fuel.php fuel_mode value set to auto?
$config['fuel_mode'] = …
That error is not a PHP error but a server error and likely caused by something in the .htaccess. Different servers may have different .htaccess abilities so you may need to check there. There is likely a line in the .htaccess that it doesn't like. …
Actually, that error is likely with .htaccess. Is it properly configured on the site? If it's not rendering the CodeIgniter error page but the default Apache error it's likely that.
Yeah... probably... although, I would highly recommend upgrading your version of PHP if possible (I know that can be easier said then done). 5.4 came out over 10 years ago and was EOF nearly 7 years ago.
What version of PHP and what version of FUEL are you running (you can see the version of fuel in the fuel/modules/fuel/config/fuel_constants.php at the top)?
I've pushed an update here to hopefully help with your issue. Let me know if that does the trick:
https://github.com/daylightstudio/FUEL-CMS/commit/9f4c0450ea734d582c18b297954373504de7fd87
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.