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
-
I've posted a fix for that in the develop branch if you want to pull from there.
-
The routing process happens before any database can be loaded (it happens when determining which controller to use). So this doesn't work? $route['404_override'] = 'innerpage'; You may need to use the "_remap" method in that controller to route requ…
-
A few questions: 1. Do you have errors turned on in the index.php bootstrap file (should be automatically if you are using the development environment)? 2. Is this on your local environment and if so, what's the setup? 3. Also, which pages is the e…
-
You can put them in subfolders and just reference "myfolder/myblock": echo fuel_block("myfolder/myblock"); If this is more for the CMS side of things and you are using the "block" field type and only want a certain group of blocks to appear in the d…
-
Are you trying to route all your requests to "innerpage" except for requests the FUEL CMS? You could try using the 404_override route. FUEL uses this to automatically display pages that don't have controllers defined.
-
This section may be helpful: http://docs.getfuelcms.com/general/pages-variables#specifying_a_view In your case the "view" file would be the "layout" file (e.g. fuel/applications/views/_layouts/personnel.php:
-
Can you display the code you are using for your model for the hook?
-
You will need to create the page in the CMS. Then in your controller method, call: $vars = array(); // array of variables to pass to the page $this->fuel->pages->render('about/contact', $vars, array('render_mode' => 'cms')); The first p…
-
Here is the source code. It is currently out of date though and is not built in 1.0. However, many of the same things will still apply in 1.0. https://github.com/daylightstudio/FUEL-CMS/tree/demo
-
Yes. You can read more about that here under the area where it says "Controller Page" http://docs.getfuelcms.com/general/pages-variables
-
That database error you are seeing is actually different and is generated deeper inside of CI. I'd check out around line 1168 in the fuel/codeigniter/database/DB_Driver.php file. I think the only way to avoid it is to fix the database error.
-
You could try just overwritng the export_data method that's inherited by the base_module_model: public function export_data($params = array()) { $data = parent::export_data($params); $data = mb_convert_encoding($data, 'UTF-16LE', 'UTF-8'); …
-
That controller is located in the fuel/modules/fuel/controllers/ folder. FUEL will look for controllers in the fuel/modules/{module}/controllers folder. For example, you can create an advanced module named my_module and have a corresponding controll…
-
There is a property on the model called "auto_encode_entities" that you can try setting to FALSE.
-
If you are using FUEL 1.0, try the following syntax instead: $this->fuel->pages->render('register, $vars);
-
Did you look at the fuel/modules/course/config/ folder? Those files should all have "course" changed to "courses" and I'd check the config, constants and routes files in particular for values to change in there.
-
There is a "salt" value that needs to be saved with the password. You can use fuel_users_model::salted_password_hash() to generate the password with the hash.
-
Add this to your main css file for the page (e.g. assets/css/main.css). Usually it's included in the header using the "css" function.
-
Is the form being rendered in the front end, like for a contact form, or back end (CMS)?
-
That's how you do it. What's the error in the view?
-
It would become available in that reindex list because the search module itself has the "preview_path" => "{location}", set and since you created a new record with a location of "personnel_index/all", it will appear in that list. However, if you …
-
The documentation for that class is a bit thin. However, looking at the source code should be pretty helpful. It's found in fuel/modules/fuel/libraries/Fuel_base_controller.php
-
This can actually be handled with CSS. Try adding the following CSS: form input::-webkit-validation-bubble-message, form select::-webkit-validation-bubble-message, form textarea::-webkit-validation-bubble-message { display:none; }
-
Is "kam" the sub folder on your webserver in which you installed FUEL. Does kam/index.php/fuel/start work. If so, it may be an issue with .htaccess not being enabled.
-
I see. That looks to be a bug. I've posted a fix on the develop branch for you to test out.
-
What is the URI location relative to your web folder that is causing the problem? You may also want to add "render_mode" => "views" next to the "view_module" => "registeration".
-
Hmm... I'm sorry but I've never used litespeed.
-
Try creating a "/modules/myModule/views/_layouts/myView.php" folder and then adding "view_module" => 'myModule' in the array of parameters (3rd parameter)
-
I'm not quite sure I understand the question. When you use an "asset" field type in your module, it actually stores it in the same place as the main FUEL assets module.
-
So are you saying that the module data you are wanting to index doesn't exist on a page somewhere on your site?