Home › Knight_Yoshi › Comments
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
Knight_Yoshi
About
- Username
- Knight_Yoshi
- Joined
- Visits
- 21
- Last Active
- Roles
- Member
Comments
-
Those variables do not exist; __antispam___field is null as well as other fields that are suppose to have variables. We already tried that, but again they are null, however, the fields exists within $fields array. To note, we dumped all the defined…
-
"Customizing the HTML There are several ways to generate the HTML for the form. The first option is to use "auto" which will use the Form_builder class to generate the form based on the fields you've specified. Fields can be specified in the CMS or…
-
You need to create your own block view, but then you have to handle generating the form yourself. We were looking at how to change it as well, because... nested tables... Ugh.
-
Yeah, it was an alternative proposal to my PR to keep it backwards compatible. I posted here after making the PR, because I wasn't sure if it was going to go unnoticed.
-
Using Fuel 1.4 In the form module models it uses require_once(FUEL_PATH.'models/base_module_model.php'); The errors go away when changing it to require_once(FUEL_PATH.'models/Base_module_model.php');
-
So I've found by using 'group_id' => 2 or 'group_id' => 'footer' I was able to change which group is used. This isn't mentioned anywhere, but in the http://docs.getfuelcms.com/libraries/fuel_navigation_model; I didn't even find it in the model…
-
Ah! I figured it out when you said mentioned the hierarchy. So the key(s) had a leading (and sometimes trailing) forward slash. I think it should take into account leading and trailing slashes as long as the rest of the URL matches.
-
I changed the /fuel/* to /admin/*, but it does work when the url is /fuel/manage/cache
-
It's the styling. We already thought about that, but we want to be able to upgrade Fuel easily without having to go back and modify any of the core. Once you start "customizing" the core it makes upgrading a little more difficult. Probably the best…
-
That's some fast work, thanks! I'll let you know if I find any other bugs.
-
Alright, that fixed that, thanks! Now that it was pointed out, I do remember changing that in another project. I guess I forgot about it. Something else I don't understand the reason for (or how to use) is in the body tab when creating/editing a pa…
-
Yeah, I figure that out. I was thinking, "wait, I haven't configured the database for ci_sessions." So I started looking for possible created files, to which I couldn't find it. Then I got really confused for a moment, but worked it all out and swit…
-
Thanks!
-
Is there an estimated date when the development branch with CI3 support will be merged onto the main branch?
-
Thanks! I couldn't find where that was mentioned.
-
I was hoping that wasn't the case. It would have been nice to use inline with Fuel and looking through all the files, it doesn't seem like it'd be easy to convert to a module either (following the MVC pattern).
-
I also have a question about my project's database. To be able to use Fuel as the content manager for the existing tables, does Fuel need to be built in the same database/schema as my existing project, or can I use CI's method of adding using more t…
-
Also with integrating Fuel into an existing project, everything in my project goes into the project_root/fuel/application/*, right? I encountered an issue when replacing Fuel 1.3.1, the one I had started to use before posting here, with 1.4_dev. So…
-
I'm glad there's working being done towards CI3. I've browsed around looking at what Fuel has to offer and I like it a lot. The only issue I'm having is integrating it with an existing project. The docs have steps that start from a new project. I …