› ›
CRITICAL SECURITY VERSION UPDATE:
https://github.com/daylightstudio/FUEL-CMS/releases/tag/1.4.13

Fuel for CI3

Knight_YoshiKnight_Yoshi
edited December 2015 in Feature Requests
Is there any work being done to upgrade Fuel for CI3 and is there an expected release date?

Comments

  • adminadmin
    edited 6:32AM
    The 1.4_dev branch is being worked on which is 3.0:
    https://github.com/daylightstudio/FUEL-CMS/tree/feature/1.4_dev
  • Knight_YoshiKnight_Yoshi
    edited 6:32AM
    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 noticed Fuel has it's own instance of CI, is everything suppose to go into Fuel's copy of CI?
  • adminadmin
    edited 6:32AM
    That instance is the same $CI object. It's just passed around to different areas. There is a $CI->fuel object which is a child object on the $CI object (more on that here: http://docs.getfuelcms.com/general/fuel-object-structure). The $CI object is essentially the controller object and is the equivalent of $this in a controller.
  • Knight_YoshiKnight_Yoshi
    edited 6:32AM
    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 filed a bug in GH.
    https://github.com/daylightstudio/FUEL-CMS/issues/350
  • adminadmin
    edited 6:32AM
    Correct.
  • Knight_YoshiKnight_Yoshi
    edited 6:32AM
    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 than one database and have the Fuel interface manage that?

    What I mean is, so the Users table in my existing project. To integrate Fuel to be able to manage users through that interface, does it my existing Users table need to exist in the same Fuel database/schema?
  • adminadmin
    edited 6:32AM
    The database tables don't need to necessarily exist in the same schema but they will need to inherit from the Base_module_model class in order to be used in the FUEL admin. The Base_module_model class has methods on it that the FUEL admin uses.
  • salmanaligeeksalmanaligeek
    edited 6:32AM
    What are the things remaining in FUEL-CMS 1.4 dev branch to become stable?
  • adminadmin
    edited 6:32AM
    There are no known bugs at this point but does require I feel a little more vetting by the community. Would be great if you tried it out and reported any new bugs.
Sign In or Register to comment.