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
-
What version of MySQL are you running out of curiosity?
-
Have you looked at filtering. You can add a "filters" module parameter to your module in the fuel/application/config/MY_fuel_modules.php file similar to what is shown in the fuel/modules/fuel/config/fuel_modules.php file for the navigation module ($…
-
I'm not quite sure I understand the "upload through ftp to do extra db queries to target at this page" however, you can output the contents of the page you create in the backend by simply rendering it as shown here: http://docs.getfuelcms.com/genera…
-
No they need to be loaded. They are a shortcut to $this->session->set_userdata()
-
You are correct in the syntax. It should be: <?=fuel_edit('create', 'Create Post', 'blog/posts')?> Also, it looks like you've identified a bug. I've posted a fix in the develop branch for you to test out.
-
To have a create button you may need to add the following in the "posts.php" file: echo fuel_edit('create', 'blog/posts');
-
I've ran into issues in the past with MySQL inserting 0s for auto_increment values and had to restart MySQL.
-
What version of FUEL are you running. This looks like a bug that should be fixed in the latest version is why I ask.
-
You need fuel_users_model->find_one and not fuel_users_model>find_one (note the missing "-")
-
Hmmm... I'm not sure. I'm not able to replicate that problem. You should be able to call fuel_set_var from within your view file and it will affect variables in the layout file like "js". Maybe perhaps try it with just a simple view called "test.ph…
-
In the code above, you specified the $vars['layout'] = 'general' and not 'main'. Is that still the case? I just ran a test doing the same thing (but using the layout of 'main') and it worked OK. Is there a "signup" page also created in the CMS, or …
-
Try using the following instead of $this: $CI =& get_instance(); $CI->load->module_model(FUEL_FOLDER, 'fuel_users_model'); $user=$CI->fuel_users_model->find_one(array('id'=>$this->get('id')));
-
So you are saying that you are using a view of "views/signup.php" that has fuel_set_var('js','a,b,c'); set at the top of it. You then have in your views/_layouts/main.php layout file: echo $this->asset->js($js); // (As an FYI, you can use the …
-
You need to add a "?" in your .htaccess file and change: RewriteRule .* index.php/$0 [L] TO RewriteRule .* index.php?/$0 [L]
-
How are you embedding the variables? Are you including the $: {$page_title} Also, you can just use PHP syntax: <?=$page_title?>
-
We spent a ton a time trying to figure out the problem and figured it was in that hook somewhere but we weren't able to identify what was triggering it so we couldn't really test it. So much easier when it's reproducible.
-
Excellent!!!... I see the problem and have posted a fix to the develop branch for you to test out. Thanks for your help in uncovering that.
-
You can overwrite these in your form_fields method on your model: ... $fields['chantier_id']['label'] = 'Chantier'; $fields['chantier_id']['module'] = NULL; ...
-
Do you mean you can't do this {url('map', SECURE_BASE_URL)} in a layout field in the CMS? If so, you try adding the in the global.php file as variables that get passed to all pages created in FUEL: $vars['secure_base_url'] = SECURE_BASE_URL; Then in…
-
So are the {...} in a particular layout view file (e.g. views/_layouts/main.php). Or are the {...} in the values entered in the CMS layout fields?
-
If you look in the javascript console, there is probably an AJAX request that is returning an error. If so, what does that error message say.
-
The icon fix I believe is already in the develop branch from a previous commit (the classes cke_button__fuellink_icon, cke_button__fuelunlink_icon, cke_button__fuelimage_icon were added to fuel.css). Let me know if you uncover anything else after yo…
-
Are you able to recreate the problem following similar steps?
-
The limit value sets the max number of records to return in the array. Does the following code work for you: $CI =& get_instance(); $blogpost = $CI->fuel->blog->get_recent_posts(1, array('author_id' => 1)); foreach($blogpost as $post…
-
You'll need to add that function in the fuel/application/config/parser.php file under the $config['parser_allowed_php_functions']
-
Do you need to be logged in to view that page? If so, the crawl won't work for that page unless the page provides a backdoor access for the crawler. The crawler just does a CURL request and essentially acts as an unprivileged user.
-
I'm sorry but I don't think I'm quite understanding your question/issue.
-
What gets returned is an array of blog posts even though you are limiting it to 1. So you will still need to either loop or do something like $post = current($blogpost);
-
It looks like the page is reporting back a 500 error. If you click on that URL and are logged in, do you see an additional error message as to what may be causing the 500 error?
-
The version in 1.1 should be v4.0. There appears to be two things that need to be fixed for this to work: 1. An additional configuration setting is required for the plugins to work called "allowedContent" which can be added in the MY_fuel.php $conf…