In your test controller, add the following code after you run the fuel_model code to output the SQL and debug from there:
$this->videos_model->debug_query();
You can access the form object by using something like the following:
$form = $CI->fuel->forms->get('my_form'); $form->add_field('my_field', [....]);
To overwrite an existing field, pass in the same name as the field you want to o…
That appears to be a valid FUEL URL so I would next check on a different server environment / browser to see if there are any differences there that may be causing an issue.
The FUEL 404 error is meant to be shown for any URI path that doesn't exist and doesn't call a redirect to go to a specific 404_error page. If you are wanting it to go to a specific 404_error page that is rendered in FUEL, you will need to add the r…
The date field type is actually just a text box with that class associated with it that the javascript looks for. You could mimic that behavior by creating a text field with your own class that uses javascript to instantiate the behavior you want. T…
So you are you saying, if you get a 404 error in FUEL, you want it to redirect that traffic to a specific 404 page instead of displaying the 404 page itself? If so, in your 404_error.php template, add the redirect code at the top.
Are you saying you are getting a validation error or you simply aren't allowed to enter in those values and it's restricting you? The datepicker field uses the fuel.fields.datetime_field function found in the fuel/modules/fuel/assets/js/fuel/custom_…
Do you have redirects setup in the fuel/application/config/redirects.php and if so, are the redirects 'passive' or 'aggressive' type redirects:
http://docs.getfuelcms.com/general/redirects
You can use the "markdown" parameter in your fields configuration to make the markItUp! editor use the markdown syntax.
http://docs.getfuelcms.com/general/forms#wysiwyg
Is the 404 page controlled by FUEL or outside of it? The .htaccess file is routing all requests that don't match folders and files on the server to the index.php which is then in charge of 404 error pages. If you don't want 404 errors to register in…
I believe the reason why that layout key isn't working is probably because it's not defined as a layout in MY_fuel_layouts.php. In that case, there is a "module" property you can specify in your layout definition as SHOP_FOLDER.
$config['layouts'…
Correct. You could also try the following:
$vars = array(); // ... add any other $vars to your page outside of the CMS $this->fuel->pages->render('my_uri', $vars, array('view_module' => SHOP_FOLDER));
If you have a lot of template coding that you want to put in the CMS, I would recommend trying to refactor them into blocks that you could then include in your templating code as simply {fuel_block('my_block')} instead that could then include that l…
This looks to be a bug in the Forms module. I've posted an update:
https://github.com/daylightstudio/FUEL-CMS-Forms-Module/commit/209a3bc8aa5a4f68599ec9ad210d80a547cd7303
The example above was referring to is a layout's fields definition in MY_fuel_layouts.php or in a model's form_fields() method that should return a $fields array. You can also specify a "style" or "class" parameter to most field types as well:
$f…
The $values array are the values saved for the record. You can use it to check for example that it even exists to see if you want to differentiate between the create and edit views of your forms. Regarding adding CSS for a particular field, you can …
There is a file found in the fuel/application/views/sitemap_xml.php which is meant to be edited to fit your needs. Be default, it merges an array from the navigation found in the fuel/application/views/_variables/nav.php and the URLs generated from …