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
-
That makes sense to add so I've added it to both branches. The MY_Model.php find methods however, still does not have a select attribute but you can use $this->db->select(...) within the models to affect that.
-
I've been working on localization off and on the past couple weeks. There are some parts of it in Russian that have been translated already but will need to be re-addressed once I'm able to extract all the text into lang files. I'm hoping to have al…
-
That should be fixed now.
-
Looking into this
-
I've just posted some fixes for that. To do it you can specify the location value to an empty string like so: $nav['home'] = array('label' => 'Home', 'location' => '');
-
I just posted a fix for that issue (hopefully). It appears that you have to set the cookie again before rendering just to be sure the cookie is there on the initial page load. I'm wondering if this is an issue with the CI's native form_helper as wel…
-
I'm looking into this issue. If you go to the form and refresh the page and then submit, it looks like the csrf cookie value will match (which is what I was seeing), but with an initial view of the page and a fresh cookie, it is causing a problem.
-
That is a bug that krept in a couple commits ago when trying to fix the safe_htmlentities() function for older versions of PHP. I've fixed that function on both branches now.
-
The reason there is a redirect and a flash data is so that you can't hit the refresh button and resubmit the page after success. Does that make sense?
-
What's the error you are seeing (when you say errorring out)? Also, if you are using the Form_builder class, there is a display_errors property you can set to TRUE, which will display any validation errors generated by the Form_builders Validation …
-
I think that error may be unrelated. What happens if you add $vars['CI'] =& get_instance(); to the fuel/applications/views/_variables/global.php file so that variable is set (if it isn't already). That error likes to appear in layouts when the C…
-
The span fields should be OK because they are markers for the inline editing and shouldn't appear in the rendered page. The last one for gt IE 9 looks like it may have some issues with the comment. What issues on the front end are you seeing?
-
I think the problem is due to the multiple body tags. The regular expression I had in fuel/modules/fuel/libraries/Fuel_page.php class originally didn't check for multiple occurrences. I just posted a fix so that it will just limit it one if more the…
-
You will see those error messages at the very top of the page only if you are logged into FUEL because it has an area where it captures all error messages. The error messages should also be replicated in the main view of the page just above the form…
-
After thinking about it a little more, I reset the body_class variable to be blank in the 404 page to prevent the issue for page names that may be the names of other CSS classes.
-
I've just posted a fix for this to the Form_builder class to work just like the form_helpers. It leverages the existing "key_check" parameter which was intended for something similar and adds an additional parameter for the hidden fields name ("key_…
-
I just pushed a commit to namespace the error class in the CSS to prevent that issue. To answer your question, there is no is_404() function, however, you could set a variable or constant in the error_404.php page that could be used.
-
Thanks for the report. I'm looking into that.
-
Yes, that is true. I guess it depends on what classes you are wanting to extend. If it's the core fuel classes and helpers, then it would be a little more work each time you want to upgrade.
-
You could perhaps create a separate module folder and store your extended libraries in that module. Then you could load those in you code like so (where 'my_code' is your module folder name): $this->load->module_library('my_code', 'Menu'); Al…
-
It appears the problem occurred because the URI_PROTOCOL being used was QUERY_STRING and the preview page has query string parameters passed to it which was causing an "The URI you submitted has disallowed characters." error to be displayed. Changin…
-
That is strange. I think to diagnose, it may require putting in some Firebug console.log statements in the fuel/modules/fuel/assets/js/fuel/controller/BaseFuelController.js file. In particular the tableCallback and redrawTable functions to test when…
-
I'll email you directly so I can attach an image.
-
It doesn't look like the example you pasted in above came through. Try putting 'code' HTML tags around it.
-
Unfortunately not. We are using a Vanilla forum. Although I'd love to have a module for FUEL, we don't have any immediate plans to create one simply due to the time involved... perhaps down the road (or perhaps a community member may take this initi…
-
Glad to hear it! Looking forward to it.
-
The fuel/modules/fuel/controllers/login.php file on line 96 is where the redirect to the admin dashboard is. You can change that to the page you want it redirect to. You could also try doing a 301 redirect in the .htaccess file. You could also try …
-
Do all ajax requests finish without error and is there content being returned by the ajax requests? What branch are you using "master" or "0.91" and what platform/stack are you using (e.g. MAMP, WAMP, ...etc)?
-
Could you try restarting MySQL and Apache? I haven't seen this issue before. Let me know how it goes.
-
Do you have FireBug installed...? If so, do you see any content coming through after you click the checkmark (it posts the data of the field to the /fuel/modules/controllers/preview controller and uses the _fuel_preview.php file to render the output…