You will have to use some custom javascript to do this. The Navigation Module actually does this to get the list of parents based on selected group. You could look at that as a reference. For a simple module, you can add a javascript file by setting…
What browser and platform are you on (MAMP, WAMP... etc). The spinning on the dashboard is an ajax call, so if you have Firebug installed it would be good to see what is happening with that request.
Pages are a little tricky because unlike the blog that has a single column to do a like search on, it can have any number of fields for a page that you may need to search on. Perhaps the easiest way would be to do a search on the fuel_pagevars table…
Could it be due to the configs load method being overwritten? You may need to merge your changes on top of what the MX_Config has. I had to do a similar thing with the MX classes to include some additional changes (e.g. the Loader class example abov…
What happens if you try extending it similar to how fuel/application/core/MY_Loader.php where you require your third party config or you could try adding it to the application/core directory but have your class extend MX_Config (not MX_Config extend…
Sure. You just need to change your values in your fuel/application/config/MY_fuel_layouts.php. Here is a page that helps explain it.
http://www.getfuelcms.com/user_guide/modules/fuel/layouts
You can create any number of layouts you want by adding t…
Yeah. As an FYI, the contact controller on the new demo branch that was posted today with the new 0.9.3 version, has an example as well:
https://github.com/daylightstudio/FUEL-CMS/tree/demo
I tend to create modules when it's code that can be reused elsewhere or may need to be logically separated. What I would do is first start using a CI Controller and then once you get it working that way, you can always extract it out into a module l…
Alternatively, you could paste in the php code that you have in your block above and when you save it, it should convert what you have to the proper template code (must be enclosed in php tags).
That's a bug in the asset_helper. I just pushed an update for it. Specifically, in fuel/application/helpers/asset_helper.php on line 167 needed to be changed to
return $CI->asset->captcha_path($file, $module, $absolute);
Is there a pencil icon button on the toolbar when you open it up? If not, would it be possible for you to send me a login so I can test out the inline editing (email can be found if you click on my profile image)?
We've thought about including a social module and have several in various forms for Twitter that we'll use for clients. But with regards to your particular issue, I guess, I'm not quite sure how it directly relates to FUEL CMS. As a side note, Ellio…
No problem... and thanks for the spanish translation efforts. That should make a few people happy I hope. As a heads up, there will be a new version coming out hopefully in a week that does have a couple minor language file additions (not many thoug…
It looks like it expects a base class to by in the system (fuel/codeigniter) folder. There was a switch from using Matchbox to Modular Extensions which is also probably part of the issue. Regardless, I don't see why it should be limited to the syste…
There is no debugging mode per se. You may need to turn off error reporting in the index.php bootstrap file on your live site though. Also, you can set the "enable_profiler" to TRUE in that same file to show the profiler information for you site. T…
It depends on how your advance module is setup. I think any of those option would work but probably the easiest would be to just include it the view file that your advanced module has. With regards to using jqx or not, I tend to use it when I have a…
Hmm... I think there is a bug if you are rendering collapsible menus from the admin (it seems to work OK with a nav.php variables file). I'm looking into it.
I have a modified version of the Menu class that will output an array if you want me to email it to you so you can test it out. I plan on adding it (or something close) in the upcoming 0.9.3 release.
There are a couple ways to do it. You could change the blog_posts_model::form_fields() method and unset or alter they type of fields to 'hidden' that are returned from that method.
Another, less obtrusive way may be to simply target those elements…