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
-
So you are associating multiple plans with each plan feature? If so, the 1.0 beta provides a has_many property you can specify in your model which will automatically create a multi select box for you to associate multiple plans with each feature. Th…
-
Try an array like this where 'MY_MODULE' is your advanced module's name: array('MY_MODULE' => 'cart_admin');
-
That's not really supported out of the box so you may need to get creative. If you are using the 1.0 beta, one method may be to add javascript in your form_fields method that sets the display of the button to none. function form_fields($values = ar…
-
Are the plan checkbox values being saved to the same model or in a different model? If the same model, is it being saved as a serialized/json encoded array?
-
Try changing the following in the fuel/application/config/routes.php file: FROM $route['default_controller'] = 'fuel/page_router'; TO $route['default_controller'] = 'fuel/login';
-
There currently is not. You can place the template file anywhere in your views. I'll usually put it in a sub views folder called "_admin". Below is an example of one where you use the {...} as placeholders for the field names. Note the {fields} and…
-
In short, yes there is. The repo itself exists like that. Was this repo initially created with the master 0.93 branch and now you are creating a 1.0 local branch and trying to merge in the 1.0 branch from GitHub? It's highly possible that you may ne…
-
I'm not sure why you would be getting that Apache error. Is there anything in your Apache config that may be preventing access to that file? http://wiki.apache.org/httpd/ClientDeniedByServerConfiguration
-
That sounds like the right approach. Does that work for you?
-
It sounds like your thought of having a base class that you inherit from for basic functionality and then customize for model specific methods would be a good approach. There are also interfaces which a class can implement. http://php.net/manual/en…
-
No problem. For the render divs, try passing the following 'form_builder_params' parameter: ... $fields['template_phone'] = array( 'display_label' => false, 'add_extra' => false, 'init_display' => 'first', …
-
Is the Access Denied the database error being displayed? If so, make sure you have the proper user name, password and database name in the database.php config file.
-
MySQL should be able to store the newlines. Try using double quotes and change the slash to a backslash: $referralCodes = explode("\n", $referralCodes->value);
-
Is this using .93 or the 1.0 beta? Also, you are referring to the pages module correct? There is a "sanitize_input" that can be set on a module, but by default the xss_clean is turned off for the pages module which is usually the culprit for that.
-
That looks like it is caused by the initDisplay value. Try setting that value to FALSE (which I see the documentation doesn't mention).
-
If you are using the 1.0 beta try the following in your model's form_fields method where "my_field" is the field's name: $fields['my_field']['module'] = ''; In 0.93: $fields['my_field']['class'] = '';
-
By default, the permission value gets set to the same value as the module_uri. In this case it was membership/members.
-
After you hit "Add Another", if you use the DOM inspector on your browser, does the template_phone field input name look correct in that it shows a 0 index for the first row and a 1 for the second item?
-
The 1.0 beta is: https://github.com/daylightstudio/FUEL-CMS/tree/1.0
-
You mind sending me a zip file of your module to test out (can be paired down and you can leave any sensitive code out). My email address can be found under my admin profile.
-
There is a fuel_auth class that has a "valid_user" method on it. For 0.93 you can access it this way: $valid_user = $this->fuel_auth->valid_user(); For the 1.0 beta: $valid_user = $this->fuel->auth->valid_user();
-
What are the routes being used for the modules?
-
The "fuel" variable is only in 1.0. If you are using FUEL version 1.0, you can use the following from within a controller: $params['render_mode'] = 'cms'; $vars['my_title'] = 'This is my title'; // setting TRUE as the last parameter will return it …
-
I think you are wanting something similar to the blog modules setup. I believe the permissions that you are wanting are: members members/create members/edit members/publish members/delete members/export groups groups/create groups/edit groups/publ…
-
We may release it but are unsure at the moment. I'll see about sending a version to you for testing.
-
OK. How about trying the same with the Fuel_auth->has_permission method?
-
How about at the beginning of the method: function validate_user($permission, $type = 'edit', $show_error = TRUE) { echo '
'; print_r($permission); print_r($type); echo '
'; exit(); if (!$this->fuel->auth->has_permi… -
Actually, what I meant was to exit from within the validate_user method to see what is getting passed to it.
-
In the latest 1.0 beta version (as of last week), there is a hidden field that gets set of "__fuel_id__" which you could use to grab the original duplicate ID value.
-
on_duplicate is called before it is saved and therefore doesn't have the ID. To get the id of the duplicate, you can use the on_after_save model hook. It will have the id value passed to it in the $values array which is the first and only parameter …