I would test to see if it's making it to the forms controller on submit and then debug from there. The forms controllers is located at fuel/modules/controllers/Forms.php.
Also, is the form embedded on a page created in the CMS. If so, turn of page …
Is there a "error" flash data being sent to the page that you can display or do you have something like the following a the top of your page:
<?=display_errors()?>
Is this line the one causing the blank screen:
$cheeses = array_chunk($cheeses);
Or is it a different line? If you are able to get a count value then it sounds like it's an array value that could call array_chunk. Is the error further down?
The model records have a reference to the $CI object in it which causes a recursive loop when printed out to the screen and may explain your blank screen. Does echo count($cheeses); display anything?
The xss_clean function is a CI function that is suppose to remove potentially dangerous cross-site scripting code from strings (e.g. javascript, iframes...etcs). Sometimes it goes a little too far.
The fuel/data_backup has a .htaccess file in it with deny from all. That folder can actually be moved if you want because it's not directly used by FUEL but more of just a place to store database backups.
FUEL has changed the "system" folder and moved it under the fuel/codeigniter. There are .htaccess files to help prevent external access but the fuel folder needs to exist in the main web directory.
I'm assuming this is for a simple module you've created? Can you try adding the the following to your module config in fuel/application/config/MY_fuel_modules.php
'sanitize_input' => array('template','php'),
By default the value is 'sanitize_inpu…
It does indeed appear to be hitting the framework side of things and is returning a CI 404 error which looks like it is getting hung up in the fuel/codeigniter/core/CodeIgniter.php file somewhere.
Are you able to deploy a regular CodeIgniter websit…
What's the URL you are trying to get to? Is it the fuel admin (e.g. /fuel)? If so, do you have the fuel/application/config/MY_fuel.php $config['admin_enabled'] = TRUE? Also, does your server support .htaccess and mod_rewrite? One way to check would …
Line 5 of the fuel/application/third_party/MX/Ci.php class should be loading that it. if you add this to line 6, what gets output?
echo dirname(__FILE__).'/Config.php'; exit();
This looks like the Fuel_advanced_module::attach method isn't attaching the appropriate "modules" object and is instead. I'd be curious what line# 389 outputs for the file path and whether that file exists on your server (it should be hitting fuel/m…
This doesn't sound like a FUEL related issue but more of a database connection issue. To rule out FUEL, I'd create a test script:
http://php.net/manual/en/function.mysqli-connect.php
The preview_path is specific to the CMS side of things. You can add a "preview_path" method to your model to handle more complicated URI routing for your preview path which get's passed an array of record values. With regards to setting up routing f…