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
edival
About
- Username
- edival
- Joined
- Visits
- 279
- Last Active
- Roles
- Member
Comments
-
Looks like I'm on version 1.0.2, and 1.0.6 is the newer version. I'll update and see if it makes a difference. Question: When updating Fuel, all I need to do is replace /fuel/modules/fuel correct?
-
Ah, now that makes sense! I didn't even think of it being a regular expression. That worked perfectly. Again, thanks!
-
Okay, so if I unset my field 'validated_email' in on_before_validate() I can't update that field, but my 'email' field works perfectly, no errors. How can I have both then? I tried specifying $auto_validate_fields = array('email' => 'valid_emai…
-
I adjusted the auto_validate_fields accordingly so it would ignore the 'email' field. I also looked for a duplicate 'email' field, I found one that had 'email' in it, but wasn't relevant. I was just trying to dig into the code to find out where it …
-
Perfect! I just found "Representatives" at the bottom of the page that I was looking on. A little confusing if you're not sure what you're looking for, but works perfect. Thanks
-
I should mention I ONLY updated the /fuel/modules/fuel folder Is there anything else I NEED to update for the CMS?
-
Perfect! I added a second $config of 'ck_editor_settings1' (for lack of originality) to My_Fuel.php Then added to $this->load->module_view(FUEL_FOLDER, '_blocks/fuel_header_jqx', array('editor_config' => 'ck_editor_settings1')); to my form…
-
So, apparently in an advanced module the module_fuel_modules.php file needs to have the 'permission' setting set for each nav item. ie: $config['modules']['members'] = array( 'model_location' => 'membership', 'module_name' => 'Member…
-
Sent, thanks.
-
my membership_routes.php file has: <?php $route[FUEL_ROUTE.'membership'] = 'membership'; $membership_controllers = array('members', 'groups'); foreach($membership_controllers as $c) { $route[FUEL_ROUTE.$route[FUEL_ROUTE.'membership'].'/'.$c] …
-
Okay, I installed the Blog module, tested it and it works as expected. I then adjusted my Membership module to match in the config/membership.php and the database/permissions sections, but I'm still missing something. I don't understand where …
-
I received the following response which looks like it's for $permission: Array ( [0] => members [1] => create [2] => edit [3] => publish [4] => delete [5] => export ) This was for both admin and user.
-
Nothing. It doesn't even touch that method for admin or user.
-
Okay, I just added exit(); at the exit of validate_user without calling it explicitly from members_module. No change, no error message, only the standard error message.
-
I added Fuel_admin::validate_user('membership/members','edit',TRUE);die(); to my members_model construct. And received no messages at all (for admin and my user). Then I added echo 'test';exit(); to Fuel_admin method validate_user() right after the…
-
So, with my advanced module I was able to get it to show up for the new user on the left nav, but when he clicks on it, it gets the following error: An Error Was Encountered You do not have access to this page. I changed the permissions as such: *…
-
So, out of curiosity, what does the advanced module generator do for permissions? I can't figure it out. I have my advanced module created already, just need to allow it to be added to a user. I noticed when I tried to add the User_manual module …
-
#1) So, the only change I "Really" needed to make was when creating permissions for a model to add the following manually after adding the model name: * Model: Edit (model/edit) * Model: Publish (model/publish) * Model: Delete (model/delete) * …
-
Here's 2. Not sure about the second one, but it seems incorrect, so thought I'd include it, plus my workaround in the meantime: * So, now that that's out of the way, I went to make sure that a new Fuel user could access all the modules appropriate…
-
Yep, that appears to have been it Thanks.
-
my fuel/modules/membership/config/membership_modules.php: $config['modules']['members'] = array( 'model_location' => 'membership', 'module_name' => 'Members', 'module_uri' => 'membership/members', 'model_name' => 'members_model', '…
-
1) /fuel/membership/members 2) yes 3) there is no membership_model.php in /fuel/modules/membership/models/ just the models that are routed: members_model.php and groups_model.php. What would go in the membership_model.php file since I don't access…
-
The message I get when going to one of my advanced modules is: An Error Was Encountered
You are missing the module membership. But the user_guide module still works fine. Just my user created one. Thanks for the tips on those form fields. … -
I've also noticed that in form_builder, 'type' => 'text' give you a 'textfield' instead of text input. 'type' => 'textarea' shows as it should. What 'type' is supposed to give you a standard input? I'm seeing the same thing with 'type' => …
-
Okay, so I think I solved it. I put my functions in my controller file outside of the class and removed the $fields[] array in MY_custom_fields.php Seems okay so far.
-
Cool. Umm, I found a problem with the way I was using custom_fields.php. Is there a specific spot to put my own custom field types, or should they just go in fuel\modules\fuel\libraries\Fuel_custom_fields.php ? It was working on the front end PER…
-
I found all my answers. I'd like to make a few notes about using Form_Builder on the front end here if I may for future reference (and since we are unable to add notes to the User Guide yet). * For using Form Builder in your controller/view files …
-
Oh! I got it now And it was right there in the instructions I was staring at... sheesh.
-
Any thoughts on the first post then?
-
On the same note. How would I be able to add a tag to the label? Ie a 'title' or 'data-title' for tool-tips? I could do it easily enough in the JavaScript, but wanted it more self-contained.