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,800
- Last Active
- Roles
- Administrator
Comments
-
Have you checked out the "block" field type with block layouts? http://docs.getfuelcms.com/general/forms#block http://docs.getfuelcms.com/general/layouts#layouts_block_layouts
-
If you are using the file field type, it requires there to be the global jqx_config.assetsAccept variable set. In the admin, this is loaded in the header already with the view found in the fuel/modules/fuel/views/_blocks/fuel_header_jqx.php file. Yo…
-
You could do something like the following to save. $form = $this->fuel->forms->get('my_form'); $posted = $this->input->post(); $model = $this->fuel->forms->model('form_entries'); $entry = $model->create(); $entry->url …
-
Hmm... why not change the module name to 'artikel'? $config['modules']['artikel'] = array( 'preview_path' => 'artikel/{slug}', 'display_field' => 'title', 'sanitize_input' => array('template','php'), 'pages' => array( 'base_uri' => 'a…
-
There is an add_field and I just pushed a remove_field method you can use on the form object which may help too. Also there is now a pre_render method that gets executed during the rendering before the form_fields() method call to retrieve the field…
-
This may be a better demo (it's on a slightly older version but more relevant): https://github.com/daylightstudio/daylight-roasters
-
The options should be returned as HTML from the ajax method similar to the Base_module_model::ajax_options method.
-
This issue is fixed in CI 3.0 which is the develop branch of FUEL right now: https://github.com/daylightstudio/FUEL-CMS/tree/develop
-
By default, the routes loaded in the fuel/modules/fuel/config/fuel_routes.php file will expect the module key of "articles" to be used. If it is to be different, you may want to add the following to the main fuel/application/config/routes.php file: …
-
The develop branch is using CI 3.0 if you want to take a look at that. $this->load->library('form_builder'); $this->form_builder->form_attrs = 'action="'.site_url('my_page').'" method="POST"'; //..... Regarding the login template and …
-
You could use it in a controller method: http://docs.getfuelcms.com/general/pages-variables#controller
-
That seems to be a database error and shouldn't be dependent on the browser. Is this still an error for you?
-
I'd recommend a few things: 1. Try hard coding the $config['base_url'] in fuel/application/config/config.php 2. Use a host redirect to help make sure that all pages use the same domain: http://docs.getfuelcms.com/general/redirects 3. Setup your env…
-
The Fuel_pages::render method allows you to pass additional variables to a page created in the CMS: http://docs.getfuelcms.com/libraries/fuel_pages (note the second parameter)
-
Are you connecting to the correct database that has a table of fuel_pages?
-
Yes it should run OK (you'll have to use something other then .htaccess to do pretty URLS). What version of FUEL and PHP are you running?
-
Should it be "$form" instead of "$from". Also, there is no public property on the $form object of "fields". You can use $from->form_fields() to get an array of fields.
-
It sounds like you need a "pre_render" hook or something right? Something that is in the render method that gets called before the actual rendering? You could also try changing the config itself using something like (haven't tested this yet): $for…
-
Do you have the same issue if you use the markItUp! editor instead of CKEditor? If so, does the content you are trying to save have foreign characters in it by chance?
-
There is a method inherited from the Base_module_model.php called get_others which should return a key => value array for the dropdown list. You can overwrite that method in your model.
-
The $values array may not contain everything that was posted (depending on if it's an actual field on the model). To access all the posted data, there is a property on the model you can access in your model hooks called 'normalized_save_data': funct…
-
That field is automatically generated with any multi select field or select2. If you view source and look at the HTML of the page, is there an exists_mission_images? If not, I think I would go back to debugging the MY_Model::process_relationships() …
-
The $clear_related_on_save property looks in the post for a field name of "exists_{field_name}" to determine whether it should delete on save or not. Is there a hidden field with that name?
-
Yes you can and I would use something like the on_before_save or on_after_save function to save multiple data potentially to another table. The "template" field type allows for repeatable fields that produces an array in which you can iterate throug…
-
What happens if you use unset($fields['mission_Images'); in your form_fields method which will just simply not create a form field element at all (instead of a hidden form field)?
-
Gonna need a lot more information then what you've posted here to help out.
-
You can use 'order' as well as 'where'.
-
I believe this is fixed in later versions of FUEL. The master branch is 1.3.2 and still using CI 2. Usually, upgrading from 1.0 to 1.3x works pretty well if you are using GIT to do the merging (depends on if you've changed any core functionality tho…
-
Hmm...I'm not able to replicate this issue. I tested it with the following and it behaved as expected: $related = $post->related_posts; foreach($post->related_posts as $p) : echo '
thumbnail_image.'">
'; en… -
You can use a placeholder like so in the has many where clause: ...'where' => 'my_field = {field_name}'...