There is an auto_validate property on MY_Model (which your models inherit from). This has a default value of:
public $auto_validate_fields = array( 'email|email_address' => 'valid_email', 'phone|phone_number' => 'valid_phone' );
That bas…
Can you debug the Fuel_admin::validate_user method to see what the name and type permission are being passed in the fuel->auth->has_permission call when accessing that page?
Keeping track of different changes across different environments and syncing them is a tricky business. We use migrations mostly for schema changes and not necessarily for inserts/edit changes made in the CMS. We actually just created our own "Sync"…
We currently use Beanstalk for our hosted GIT repositories and they have a wonderful deployment feature that can be set to automatically or manually push files:
http://support.beanstalkapp.com/customer/portal/articles/68162-what-are-beanstalk’s-depl…
The documentation has been improved quite a bit in the 1.0 beta if you are interested:
https://github.com/daylightstudio/FUEL-CMS/tree/1.0
https://github.com/daylightstudio/FUEL-CMS-User-Guide-Module (place in the fuel/modules/ folder and add it to …
When you generate an advanced module (e.g. fuel/generate/advanced my_adv_module), it will create a single permission based on the advanced module's name. When you generate a simple module, it will by default generate the other create, edit, publish …
I think the first error has to do with the multiple permissions needed for simple modules now. If you look in the permissions module you'll see that they have a create, edit, delete, publish and export permission in some cases for simple modules. Th…
That's a bug I just pushed a fix for. With regard to a different class, you can specify a "row_class" on your form_builder object which can be used to group the "row" of label + input.
That error is thrown in the fuel/modules/fuel/controllers/module.php constructor which is used by any simple module (line 50). It's triggered when it can't find the module name based on the uri segments. A few questions:
1. What is the URI giving …
What specifically do you mean by you can't access the advanced module? Is it a permission issue, or do you get a 404 error / PHP error, or is it something else?
With regards to the form fields, 'type' => 'text' has a "representative" assigned to…
I'm wondering if this thread may help. That error sounds like it is saying the jQuery cookie plugin isn't loaded:
http://getfuelcms.com/forums/discussion/comment/1610/#Comment_1610
1. Every project is a little different but our internal experience is pretty painless. There are a couple things to look out for. The User permissions lookup table has been removed in favor of the new fuel_relationships table which is used to do man…
Yes. You can pass a $vars['js'] variable in your render statement like so:
function index() { $vars['js'] = 'my_js_file.js'; $this->_render('exporttocsv_tpl', $vars); }
Also, are there any error messages in your browsers console when viewing…
Does this advanced module have sub modules (models), attached to it. If so, In .93, if you have a model that has a field name that ends with "image" or "img", then it will create 2 fields automatically when editing. One for uploading an image (a fie…
Based on this, I made some changes yesterday to 1.0 to the Asset library to allow you to put absolute paths as the "asset_path" value in the fuel/application/config/asset.php file. This should help with the CDN path.
To answer your first question, that would bypass the fuel cache settings since it's not being routed through the page_router controller.
With regards to the cache timing, are you comparing a normal controller view that's cached to a FUEL page? If …
Perhaps just hard code that system path folder instead of using the INSTALL_ROOT constant. I'm assuming that the fuel/codeigniter folder exists too with your installation. If that doesn't fix it, I think you'd need to debug the index.php bootstrap w…
The main controller FUEL routes things through if it doesn't find a controller in the applications directory first, is the fuel/modules/fuel/controllers/page_router.php. Is this something you can tackle in a CI hook?
http://ellislab.com/codeigniter/…
The header file you made the changes in is for the front end and not the CMS. You can include those JS files and CSS by adding them to the "fuel_javascript" and the "xtra_css" parameters in your MY_fuel.php file:
$config['fuel_javascript'][] = 'htt…
A couple questions:
1. Are you using .93 or the 1.0 beta?
2. Are you using the asset helpers to put in images, css and js (e.g. img_path(), css(), js())?
Part of the reason FUEL has it's own library is because the CI Cache library use to be pretty limited in 1.7x and was only setup to cache stuff sent to the Output class if I remember correctly. In 2.0, there was a Cache driver added. We've considere…
OK. Are you perhaps using some sort of symlink? You could try with a straight download of CodeIgniter too if you are wanting to take FUEL out of the equation.
It sounds like it may be because you have a model that's the same name as your controller (2 Classes named Offers?). Try naming your controller, Offers_module. This will automatically be picked up by FUEL without the need for a route in your fuel/mo…
That seems correct to me if your index.php is located in the /var/www/ folder. This error is happening right off the bat in the index.php bootstrap and would be a similar issue with a normal CI install. Have you installed CodeIgniter and worked with…
A couple questions:
1. What is the path and name of your controller?
2. Can you paste in the whole code or at least up to the index method?
2. Is this with 0.93 or the 1.0 beta version
https://github.com/daylightstudio/FUEL-CMS/tree/1.0
It depends on your implementation and customizations, but in general these are the steps and things to look out for:
1. First step would be to download from the 1.0 branch and place it in a separate testing folder:
https://github.com/daylightstudio…