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'm assuming you are wanting to do this in the CMS form for creating a services record correct? If so, the easiest way may be to just add the $foreign_keys property to your services model like so: public $foreign_keys = array('page_id' => array(F…
-
Hmm... I think I would start by grabbing the pagination code from the main blog.php controller and try incorporating it into the fuel/blog/controllers/categories.php and archives.php controller.
-
It is still in beta period while we work on documentation and testing it but are already using it for sites we do by default. It has a number of improvements and bug fixes. The modules aren't part of the core like they are in 0.93 but can be downloa…
-
That is correct. The model gets assigned in the constructor of the fuel/modules/fule/controller/module.php controller.
-
Is the upload happening from within your own module or is it happening in the Asset module? Is this with the .93 branch? If so, you may want to try out the 1.0 beta branch which has addressed a couple image upload issues: https://github.com/daylight…
-
Is there a baseurl tag in the header of your HTML? If so, try removing that. Also, you should include a return false; at the end of your click function or an e.preventDefault() at the beginning of it to prevent it from refreshing the page.
-
I think that's as good a way as any.
-
The module_view method is something that FUEL has added to the HMVC Module library we are using. There is also a load->module_library, load->module_config, load->module_helper, load->module_model. The difference being that the first para…
-
One way to do that would be in the blog modules views/themes/default/_layouts/blog.php to remove what is in that file and use the following: $this->load->module_view('app', '_layouts/main.php'); Where the "main.php" is the layout found in fuel…
-
The documentation here may help: http://www.getfuelcms.com/user_guide/libraries/my_model
-
Glad you were able to get it resolved.
-
I suppose you could Extend the Page_router controller and add your own logic to it and set that as the default in your routes config file.
-
I just found a couple issues with this function when trying to use a model and have it pass data to the view. You can also use the generic variable "$data" as well as "$poll_questions". I've posted some fixes on the 1.0 beta branch. https://github.…
-
Loading a model in your block that way should create a variable named "$poll_questions" that you can access in in your block view file and output data from it: <?=$poll_questions->question?>
-
Thanks for the report. I've just pushed a fix for this in the 1.0 branch: https://github.com/daylightstudio/FUEL-CMS/tree/1.0 Specifically: https://github.com/daylightstudio/FUEL-CMS/commit/7c403b19eeb9e3645d673c56d37275b2d86bd5dc
-
Unfortunately not. You can however, set the required message to be blank and then manually put it in your HTML code above the form. // in controller $this->form_builder->required_text = '';
-
I'm just suggesting to temporarily remove the .htaccess to see if you can get the xcache to work. FUEL can still work without .htaccess, you just need to add "index.php" as the value of the $config['index_page']; What was the error?
-
Have you tried testing it without the .htaccess or simply commenting out line 22 in that file. URIs through FUEL would include the index.php (e.g. index.php/my_page) but it would be good to test that to see if that is causing problem.
-
Try specifying the "default_order" and "default_col" parameters for you module in the MY_fuel_module.php
-
I believe that change you are wanting is in the 1.0 beta. There is both a submit_name and a submit_value (among a ton of other improvements to Form_builder).
-
the main .htaccess file that comes with FUEL is setup to route any file/folder requests that don't exist in the specified path, to the index.php CI bootstrap file which would account for you seeing the header / footer 404. You can setup a folder cal…
-
Is this with the 0.93 or 1.0 beta?
-
Try adding a variable of "fuelified" = FALSE; or defining a constant of "FUELIFY" to FALSE. $vars['fuelified'] = FALSE; $this->fuel->pages->render('about/contact', $vars); //...OR define('FUELIFY', FALSE); $this->fuel->pages->rend…
-
And you are logging in as the super admin user which has permission to everything I assume?
-
That's correct in that you will need to alter your list items function. You could try something like the following: function list_items($limit = NULL, $offset = NULL, $col = 'nav_key', $order = 'desc') { $data = parent::list_items($limit, $offset,…
-
Are you referring to moving the "fuel" folder to above the web root or are you referring to some other folder? Also, what error messages are you seeing?
-
What if you use the _remap method instead of the index method on the controller? http://codeigniter.com/user_guide/general/controllers.html#remapping
-
Does fuel_set_var() work for you? fuel_set_var('my_var', 'my_value')
-
You can set up redirects to handle the redirection of pages that aren't found in a controller or by using the "opt-in" controller method (static view files): http://getfuelcms.com/user_guide/general/redirects
-
Those views get Ajaxed in? Are you seeing any errors in your developer console from the ajax requests? What version are you using 0.93 or the 1.0 beta?