Avatar

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

admin

About

Username
admin
Joined
Visits
8,800
Last Active
Roles
Administrator

Comments

  • The importing logic first checks the timestamp of the block (or page) file (e.g. views/blocks/header.php) and compares it to the last updated value of the block that's saved in the database. If the timestamp of the file is more recent (greater), the…
  • FUEL injects the inline editing CSS upon rendering the page if you are logged in so you won't see it in the header block.
  • Also, I neglected to point out that there is a 0.91 branch that has a working demo and code examples if you didn't know that already (could quite tell if you were using that branch or not). It uses CI 2.0 instead of CI 1.72 as well: https://github.c…
  • FUEL is really targeted towards folks using CodeIgniter and wanting CMS capability so having a good understanding of CI definitely helps. Luckily, they have some of the best documentation and community out there which is one of the main reasons we c…
  • Are you using the header and footer blocks within a layout (e.g. views/_layouts/main.php)? If so, if you are wanting to make your header and footer block editable in the admin, make sure your layout uses fuel_block() instead of $this->load->vi…
  • As an FYI, if you were using the 0.91 branch, there was a key file that was missing at fuel/index.php which was simply a header redirect to fuel/dashboard. That was fixed a couple days ago.
  • Make sure the assets/images/projects folder is also writable. And it's possible that the sanitize_images option for the projects model may need to be added set to FALSE (by default it is TRUE) in fuel/applications/config/MY_fuel_modules.php. This re…
    in Projects Comment by admin December 2010
  • Page creation is fixed now. Had to do with some changes from Matchbox to Modular separation. There should also now be a view button at the top when creating/editing modules.
    in Projects Comment by admin December 2010
  • Both issues 1 & 2 should be fixed now and can be downloaded here: https://github.com/daylightstudio/FUEL-CMS/tree/0.91 Specifically, I changed $this->input->xss_clean to just use the xss_clean function instead (because it no longer exists…
    in Projects Comment by admin December 2010
  • OK... that is fixed as well as the issue of accessing /fuel/ (it was missing the fuel/index.php file) on the 0.91 branch. The reason for the error is that CI 2.0 added the Security class which only gets loaded if you have xss filtering or csrf prote…
    in Projects Comment by admin December 2010
  • Where are you seeing that issue so I can try and replicate it locally? Thanks.
    in Projects Comment by admin December 2010
  • Sure, let me know if you run into any other issues.
  • The fixes have been pushed to GitHub for you to test out: https://github.com/daylightstudio/FUEL-CMS/tree/0.91
  • I found the issue (and a few others I'm cleaning up). FCPATH is different between CI 1.72 and CI 2.0. I'm hoping to do a post later tonight to address that and some issues found with regards to assets. Also, make sure you set the $config['admin_enab…
  • OK... I'll download XAMPP and try it out (I have WAMP for my windows test server)
  • And you are able to browse to http://127.0.0.1/fuel/index.php? What about http://127.0.0.1/fuel/index.php/fuel/login?
  • Sorry for the delay in getting back to you. The FCPATH should include index.php at the end like so. C:\xampp\htdocs\fuel\index.php CodeIgniter sets that constant on line 94 in the index.php bootstrap file. I'll need to do a little research into why…
  • Welcome to the small (but growing) FUEL CMS community. Look forward to your input and contributions. And as always, please let us know if you have any issues.
  • The .htaccess file should be at the folders root level. My guess is you need to turn on hidden files (which may be good to point out in the docs to prevent confusion). The $config['index_page'] parameter is in the fuel/application/config/config.php…
  • That sounds like an Apache specific error. Are you sure mod_rewrite is enabled on your server?