CRITICAL SECURITY VERSION UPDATE:
https://github.com/daylightstudio/FUEL-CMS/releases/tag/1.4.13
https://github.com/daylightstudio/FUEL-CMS/releases/tag/1.4.13
admin
About
- Username
- admin
- Joined
- Visits
- 8,643
- Last Active
- Roles
- Administrator
Comments
-
Oh... CKEditor will automatically remove iframes. You may have to use a MarkItUp field type instead.
-
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…
-
Have you tried it without the db prefix
-
This has been updated in the develop branch: https://github.com/daylightstudio/FUEL-CMS/commit/0ec764c88e52362547f43ff8b2b3a0687fea5610
-
No line numbers huh? Have you tried it with the latest develop branch by chance?
-
Need some example code of what you done/things are seeing/not seeing etc.
-
I can't think of anything 5.4 specific, however, there is probably other things to be concerned about that server too given how old that version of PHP is.
-
There are a number of factors that could be contributing to that (e.g. DB calls, other code execution). A few questions: 1. Is the page created in the CMS? 2. Have you created a simple static page view file and does it render the same or faster (h…
-
I just pushed another update to include the "active" column but requires an "activate" permission for toggling.
-
Thanks for the report. I've pushed a fix to the develop branch: https://github.com/daylightstudio/FUEL-CMS/commit/20819072c089f3e49c9528ff8f248432f750eab5
-
It's usually an enum column named 'published' with options of 'yes','no'
-
What if you add the "publish" permission to your module?
-
Fuel treats "publish" and "active" fields similarly and it's not recommended to have both on a model for FUEL.
-
The core fuel and forms module has some examples. You can add your own in the fuel/application/config/custom_fields.php file: https://github.com/daylightstudio/FUEL-CMS/blob/master/fuel/modules/fuel/config/custom_fields.php https://docs.getfuelc…
-
I would take a look at creating a custom field in which you can import and associate your own Javascript: https://docs.getfuelcms.com/general/forms#association_parameters
-
It should act similar to a slug field in that the values from one field will be used to fill out another field (with a specified function applied to it like "mirror", "strtotupper", "strtolower", "slug).
-
There is a "linked" field type that sounds maybe close to what you want: https://docs.getfuelcms.com/general/forms#linked
-
Are the being passed to the '_admin/items' view in the $values variable?
-
Hmm... not aware of anything.
-
1.1 There is a $values array that can get passed to the template (note the $my_values): $fields['invoice_items'] = [ 'view'=> '_admin/items', 'type' => 'template', 'values' => $my_values, 'repeatable' => true, 'fie…
-
I see... this is in the fuel forms module. That indeed looks like a bug. This was the fix posted: https://github.com/daylightstudio/FUEL-CMS-Forms-Module/commit/d1c7aac84b7dca9caadc1cc58a2cafd9ff02a580 You could either patch it manually or downl…
-
Is this a "keyval" field type? https://docs.getfuelcms.com/general/forms#keyval If so, what parameters are you using with it: row_delimiter: the row delimiter used to separate between key/value pairs. The default is a "\n|," (return, pipe, comm…
-
Has anything changed that you know of?
-
Did it work at some point and then stopped? If so, were there changes made that may have caused it?
-
Sorry, I don't quite understand. A CMS page with the location value of 'home' will be the homepage unless you override it with a controller.
-
You can certainly try to do that by creating perhaps a separate login that uses multi-factor authentication and then creates a validated session for FUEL. It's built on top of CI so you can leverage that as much as you need.
-
Multi-factor authentication is not a built-in capability of FUEL.
-
The advanced module's asset folder is meant to be for specific assets required for the module. For uploading of assets, it needs to within the assets folder (which is defined in the fuel/application/config/asset.php assets_server_path value.
-
I think what you want is the serialized_fields on your model: https://docs.getfuelcms.com/libraries/my_model This is a property on the model that you can specify one or more fields in your model (in an array) that get serialized and deserialized…