I would try debugging in the MY_Model::process_relationships() method. You'll see the logic there that will first clear any related items and then save.
The issue may be because a checkbox or multi select that doesn't have anything selected will not send anything in the POST so FUEL doesn't know whether it should process it. So the solution is to setup a hidden field with the name of 'exists_{field_…
Because fuel_var will by default also add additional code for inline editing, I'd use the raw variable and manipulate it as above.
echo date('h:ma', strtotime($start_time)) .' - '.date('h:ma', strtotime($end_time));
Are you familiar with the differe…
So when you execute that foreach loop above, does it loop through all the related posts for the selected post and output the main_image for each related post or does it output something different and if so what does it output for each related post m…
If you using the fuel_var function it will output the variable along with code to make it inline editable as well as apply a default parameter. You can always access the variable like so:
$formatted_date = date('m/d/Y', strtotime($event_date)); // c…
The FuelCMS.sql does NOT contain the database table for that:
https://codeigniter.com/user_guide/libraries/sessions.html?highlight=session#database-driver
What version of PHP and platform are using and do you have the latest from the develop branch?
You meant CI 3.x in your first post correct? If so, then yes the develop branch has the 3.x version of CI. If you are integrating, there are a few gotchas to be weary of:
1. Controller and Model names need to be upper case. This can be a pain when …
You could definitely create your own advanced module. In your advanced module, you can create a fuel/{module}/config/{module}_routes.php file that has the routes you want including one that can overwrite the fuel/controller/assets route (advanced mo…
Most of that work happens here:
fuel/controllers/assets.php (could change the route for this to be your own controller)
fuel/libraries/Fuel_assets.php (could create your own class and use FUEL()->attach('assets', $my_asset_obj_instance);
fuel/mod…
Tough to say what may be going on. I would recommend starting to debug in MY_Model::process_relationships() method which handles the saving of the relationships to see if there may be in issue in how it's saving.
Try adding your class to the fuel/application/libraries/My_fuel_form. Then in your fuel/application/config/MY_fuel.php there is a $config['attach'] parameter you can use to attach it:
$config['attach'] = array( 'forms' => 'my_fuel_form' );
You would have to extend the Fuel_forms class and overwrite the clean_posted method and then somewhere in your code you'll need to overwrite it by calling the attach method on FUEL:
$form= new My_fuel_form(); $this->fuel->attach('form', $form…
On the model, there is an "auto_validate_fields" property that by default is set to:
public $auto_validate_fields = array( 'email|email_address' => 'valid_email', 'phone|phone_number' => 'valid_phone' );
You can change it to:
public $aut…
Unfortunately not. Only simple modules within an advanced module.
Regarding the navigation, a menu item must exist under a specified section (e.g. Site, Modules, Admin...etc)
That sounds like you are wanting site_url to be able to look at a list of aliases and generate the proper URL. FUEL does currently overwrite the site_url function to allow for things like language parameters in the URI, however, it doesn't currently…
When was the last time you pulled. This should be fixed in newer versions but if not, let me know. It is now in the develop branch and the 1.4_dev branch is no longer.