There isn't anything setup with the site_url function to automatically change the base_url like that. However, you could create your own function that does this maybe something like this:
function url($uri, $base_url = NULL, $https = NULL, $language…
That error message looks to maybe be something coming from Apache and not necessarily FUEL. Was there anything added in the .htaccess file that may have prevented access?
There is a function called parse_template_syntax found under the MY_string_helper that can be used:
http://docs.getfuelcms.com/helpers/my_string_helper
Additionally, with a static view, you can pass it the variable of "parse_view" equal to TRUE in …
In your "has_many" relationships in your model, you can use the "where" parameter to only select tags that maybe have a specific category ID:
http://docs.getfuelcms.com/general/models#relationships
If you are logged in as Admin, then you should have access to everything assuming the admin is enabled in MY_fuel.php. Are you seeing that error when simply clicking on the Assets menu item?
Are you wanting a page to redirect to an admin page or a front end page not part of the CMS (the redirect should already be happening for the CMS pages)?
So the multiple image upload issue is a bug as mentioned above and I posted a fix to it in the develop branch. If you need to store the images into separate tables as well, then you will have access to the files names field value in a model hook suc…
The site_url function derives it's domain from the BASE_URL constant that is set in the main CI config. This value will dynamically change based on the domain that the site is being served from. However, if need be you can change this value (e.g. $t…
Then in your case you want the "asset" field type since the file field type does not give you that ability to select an image. Using the "asset" field type doesn't give you the ability to do any further manipulation of images upon upload with model …
Because the field name is "image" it will automatically assume the "asset" field type unless you set the "ignore_representative" => TRUE parameter on the field. Add that and you should see the field change to file upload fields.
You could either rename the image before uploading all together, or create an on_after_post model hook to both change the file name on the server and change the file name in database table that it's being saved in. You can access all the uploaded im…
The uploaded_data is only on save and is not available on select. I guess I'm not clear as to what you are trying to do, in particular, Question 3, "when i am selecting using "select images", how can i get the array of images so i can loop."
Add this to your fields array for r_articles:
'block'=>array('type'=>'block', 'block_name'=>'about_related_article_block','display_label'=>FALSE, 'context' => 'r_articles[0][block]'),
It depends on where you are wanting to retrieve the image information. If you are saving it to your model, the value will get saved as a JSON value to the field name "image" and can be accessed on the record as such:
$my_record->image; // will re…
When a block_name is specified, the field behaves a little bit differently. With the dropdown select, it will dynamically generate the field information with an ajax call to the fuel/block/layout_fields and pass a "context" value. When you specify a…
Correct. Are you looking for a field type that will dynamically change the options based on another selection or something like that (a dependent field type)?
The multiple image upload for the "asset" field type not adding a comma is a bug that I just pushed a fix for in the develop branch on FUEL:
https://github.com/daylightstudio/FUEL-CMS/commit/6d3fed52fed35902fc41a13c61c9f8529a9af52d
When that field t…
What if you create a select element that has a display: none and a module data attribute like so:
Also, as an FYI, the logic for the inline_edit javascript is found in the custom_fields.js file "fuel.fields.inline_edit_field" method if you need to …
Its an array of arguments to pass to the method specified which by default is the 'options_list' method. Form_builder uses call_user_func_array so may need to do something like the following:
'model_params' => array('id', 'name', array('category_…
You can try adding the class "add_edit" next to btn_field class which is what get's automatically inserted and is looked for by that inline field type. However, I haven't directly tested that.
FUEL uses the img_path function to make your image paths more portable and is using the "{...}" brackets because it is using the templating syntax. If this isn't being translated on the front end, there is a model property you can set called "parsed…