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,799
- Last Active
- Roles
- Administrator
Comments
-
If you inherit from the Base_posts_model, you essentially are getting a boilerplate with some predefined assumptions. I would recommend creating a model that is a copy of that (but also inheriting fromBase_posts_model) and go through it to overwrite…
-
Does changing that line to the following fix the issue for you? if (!empty($field_data['max_length']) AND $field_data['type'] != 'float' AND $field_data['type'] != 'double') $this->validator->add_rule($field, 'length_max', lang('error_value…
-
I've pushed a fix for this in the develop branch
-
It's likely from this change in the code: https://github.com/daylightstudio/FUEL-CMS/commit/c81875619e4079a8205f02547197c7abc7b995f3
-
There were some recent security updates to prevent the usage of javascript in fields. Could you provide an example of what you are seeing regarding the javascript you are entering in? There may be an alternative way to include that javascript.
-
What is the code you are using to embed the form and what does the code look for the form (is it done via code or in the CMS)?
-
You many need to set the multi-selects $values manually in the model's form_fields(): public function form_fields($values, $related = array()) { $fields = parent::form_fields($values, $related); $fields['my_field_name']['value'] = //...…
-
I would try debugging in the Fuel_search library class to see if the characters are getting converted somehow. I would probably check the page_xpath() function (line 720) and see what the value of the content is after the convert encoding.
-
Sorry, but I can't really debug this type of issue on the forum easily. I would suggest perhaps working backwards from a page where it does work correctly or even simply taking the raw HTML from the database and placing it in the template directly t…
-
If you move the image to somewhere else in the content does it work? There seems to be something in the HTML that is throwing off the Dwoo parser for allowed functions. Also, what is the HTML for including it in your template?
-
Can you see what is actually saved in the database? That will tell us if it's a front end rendering issue or a CMS backend saving issue.
-
I'm not quite sure. fuel.lang() is a function loaded in the global.js file but at the bottom of the page so it sounds like maybe a field is calling that inline. Are you able to disable fields in your model's form_fields() method (you can use unset($…
-
Good to know. Wonder if this is something CI will fix too: This may help too: https://stackoverflow.com/questions/60634341/codeigniter-3-samesite-attribute-for-csrf-protection
-
The Search module works by using CURL to scan the pages using the delimiters specified in the config and parsing the HTML of the page to extract the text to be searched. As @almostcompletely said, for that to work, you'll need to make sure that the …
-
I'm not quite sure I follow. Could you explain what the data looks like that is being sent in the $values array to theon_before_save() and on_after_save() functions? Also, a few notes: 1. the on_after_save() method calls a function called proces…
-
Are you getting that error with a fresh installation of FUEL by chance (the install page uses that jquery() function)?
-
What version of PHP are you running?
-
What version of FUEL are you running? I have a project that uses select2 with add/edit and it's refreshing them. That said, select2s are a little different in that you have to destroy them and then recreate them: $("#myfield").select2("destroy").…
-
It stores a hash value in the cache directory. Am wondering if the stored cache was incorrect. Could you try deleting that cache file first in the fuel/application/cache directory (you can log in to FUEL and do a Clear Page Cache too). Modifying the…
-
Are you using the jquery() function that comes with FUEL? If so, that should be automatically creating that hash value and storing it in the cache (see Asset::jquery() line 655).
-
Yes, there are a number of plugins that rely on the older version and would take a bit of time to make that update and test as well as the need to potentially make changes to website specific code not related to the FUEL admin area. The integrity…
-
It usually works pretty well assuming you don't change FUEL's folder structure and you know what files in the app directory you purposely changed when there are conflicts.
-
No problem... I know how that is (and have been on the guilty party side as well).
-
The $related_field should be the key of the relationship that's assigned in the model's $has_many property. So hypothetically, there may be a has_many relationship defined in the model (near the top) with the key of case_studies: public $has_many…
-
So basically, when we setup a project, we have two remote sources, one to the project repo and another to the FUEL repo (https://github.com/daylightstudio/FUEL-CMS.git). When there are updates to FUEL, you just do a pull from that source. In cases w…
-
Thanks. I'll work on pushing a fix for the dev branch.
-
The doc block for that method does need to be updated. You are correct that get_related_keys() needs a third parameter which is the related model (e.g. 'Case_studies_model`)
-
This appears to be due to some DWOO library code that may need to be updated. Can you test something for me on your end? If you go to that file at fuel/modules/fuel/libraries/parser/dwoo/plugins/builtin/if.php line 41 and replace the while (list($k,…
-
We will usually have the FUEL Github as a remote and merge in from that repo resolving any conflicts that may be in the application folder that I want to keep.
-
That sounds like a good way to manage it.