The $config['nav']['tools']['tools/user_guide'] strictly makes the menu on the left and doesn't guarantee that the URI path exists. You need to route to make sure you can access that page. For example, the URI path fuel/tools/user_guide doesn't exis…
Ahh... the blog module handles it's variables a little differently in it's controllers. You may be able to get that to work in the blog if you change the following line in the fuel/modules/blog/libraries/Base_blog_controller.php line 34 from:
$_vars…
Hmm... I'm not able to replicate the issue yet. What happens on a raw download of FUEL, set up with your existing db information and merging in the variable like above on say the header block that comes with the FUEL download?
If your model exists in a module directory (which in your case is one called 'ads'), the foreign_keys property value for 'id_ads_categories' needs to be an array with the key being the module folder name like so.
public $foreign_keys = array('id_ad…
That isn't documented anywhere... I'll call that out. You could use the on_before_save method... actually, if you change header_upload_image to header_image_upload, it will automatically set the value of header_image to the name of the uploaded imag…
Thanks... that's fixed on the blog. There seems to be a difference in how htmlentities() is working between my local dev machine and the live server... in particular with the hex version of the single quote (numeric entity works fine). Will need to …
It doesn't work the same with layouts unfortunately. You have to create the 2 separate fields like so: 'header_image' => array('description' => 'Header Image', 'class' => 'asset_select images', 'upload_path' => assets_server_path('', 'i…
Thanks for the suggestion. I'll capture it on the todo list. Although we tried to provide a lot of documentation, it is by no means complete as you've pointed out. We tried to capture the most important stuff but in some cases, rummaging through the…
To be honest, connecting to a second isn't really "supported" meaning, we haven't done much testing with that, since it's a scenario we haven't run into. Regardless, I'd like to see if we can get it to work for you in case we do run into that situat…
Thanks for the catch. One of them should be Comment Links. I've updated the fuel_schema.sql in the install folder on GitHub. You should be able to change that permission name under the permissions section.
I posted some changes yesterday to allow you to do this. All you should have to do is set the $config['fuel_path'] parameter in you MY_fuel.php config file now. Let me know if you run into any issues.
I'm not sure. Can you send me the module code and any SQL to power the models (click on my picture to get to my email address)? Also, which branch are you using 0.9 (master) or the 0.91 branch (CI 2.0)?
That is correct. I can see how the names can be confusing. To confuse you more, there's an on_before_post hook too, which get's called before any saving or validating. It may help to look at the code where it is implemented. The on_after_post method…
I would think it would. We built it with the idea that the CMS is secondary and that you should be able to use the framework as you would with a normal projects. The fuel/application folder is intended for your code and is the equivalent to the Code…
The 0.91 branch has an example website that includes a projects_model. In that projects_model we use the on_after_post model hook to further process the image. Below is what that looks like: function on_after_post($values) { $CI =& get_insta…