It seems many of the 3rd party jquery plugins are no longer supported or will not run on the newer jquery. The "jqx" and "fuel" javascripts under ./assets/js/ break if the newer version is used.

While 1.7.1 is fine for running a vanilla Fuel install, it's becoming increasingly difficult to build custom fields (that use 3rd party plugins) and maintain support for CKEditor and its plugins.

The repo for this is at https://github.com/croaker000/FUEL-CMS-JQUERY3
I'm happy to field questions bug fixes etc. there (or here) if needed.

Any suggestions on how to go about that? Anyone else done it?

TIA

1 - I don't think "first_class" and "last_class" fuel_nav() parameters work for the breadcrumb render_type
2 - For screen-reader Aria support, we're supposed to mark the last item on the breadcrumb line with aria-current="page"

I guess a "first_attribute" and "last_attribute" (along the lines of "first_class" and "last_class" parameters) would allow developers to add the aria support in a flexible fashion?

How can I make the date picker start on monday ?
I have tried changing firstDay to 1 in custom_fields.js, but to no avail ...

Cheers,
Xavier

How about working on an AdminLTE theme ?
It would make fuelcms responsive, and pimp up the look&feel !
I started on the login page, if anyone is interested in working on this with me, I'd be more than happy !

More screenshots (errors etc) :
https://xavierdamon.com/f/fuelcms

Cheers,
Xavier

I am new to fuel cms and would like to try it. I have added dbprefix ex "xyz_" and it wont recognise it. how to use it pleasea advise.
SQL already imported with prefix.

Regards,
Turkel.

$fields['related_entries']= array(
	'type' => 'array',
	'mode' => 'multi',
	'options' => array(
	'A' => array(1 => 'Test one', 2 => 'Test Two', 3 => 'Test Three'),
	'B' => array(1 => 'Test one', 2 => 'Test Two', 3 => 'Test Three')
	),
	'value' => array(2, 3)
);

To solve this, edit MY_html_helper.php and add this just before $purifier = new \HTMLPurifier($purifier_config);

$def = $purifier_config->maybeGetRawHTMLDefinition();
if ($def) {
   $def->addAttribute('a', 'data-toggle', 'CDATA');
   $def->addAttribute('ul', 'role', 'CDATA');
   $def->addAttribute('ol', 'role', 'CDATA');
   $def->addAttribute('li', 'role', 'CDATA');
}

$purifier = new \HTMLPurifier($purifier_config);

Then in the purifier.php config, update the HTML.Allowed stanza to include the attribute you want to allow
'HTML.Allowed' => 'div[id|class],b,strong,i[class],em,a[href|title|target],ul[class|role],ol[class|role],li[class|role],p[style|class],br,span[style],img[width|height|alt|src],iframe[src|name|width|height|class|allow]',

My $defs will need to be built up to include all the desired attributes but this is a start.

Perhaps we can improve this by creating an attribute array config item that MY_html_helper looks for and processes? That way we're just editing the config rather than the system files?

"Cookie “fuel_session” will be soon rejected because it has the “sameSite” attribute set to “none” or an invalid value, without the “secure” attribute. To learn more about the “sameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite"

I guess we need to start adding SameSite=Lax? We can do that ourselves for now but I guess it needs adding to the main build too?

I’m looking to move content from fuel to new Wordpress site.

Can you give me some pointers on whether anything can be exported from fuel? Or would it be a manual process?

Thank you,

JC

class MY_Base_module_model extends Base_module_model{
public function __construct($table = NULL, $params = NULL)
{
parent::__construct($table, $params);
//$this->get_ajax_csrf();
}
function get_ajax_csrf()
{
echo json_encode(array(
'token'=>$this->security->get_csrf_token_name(),
'hash'=>$this->security->get_csrf_hash()
));
}
}
a simple module :

class Axyz extends MY_Base_module_model{
public $boolean_fields = array('archived');
public $serialized_fields = array('precedence');
public $required = array('title');
public function __construct()
{
parent::__construct('announcements'); // table name
}

public function form_fields($values = array(), $related = array())
{   
    $fields = parent::form_fields($values, $related);
            $fields['a_file']['type']='asset';
            $fields['a_file']['upload_path']='xyz/';
            $fields['a_file']['encrypt_name']=TRUE;
            $fields['a_file']['display_preview']=TRUE;
            $fields['a_file']['remove_spaces']=TRUE;
            $fields['a_file']['hide_options']=TRUE;
            $fields['a_file']['multiple']=FALSE;
    return $fields;
}       

}

now i want to call get_ajax_csrf() through url . is their a way . i am planning to do $.getJSON() the csrf and update in window.parent.

also i am planning to do it from $.fn.jqmHide function but is their a better place to coll .. i cant find the function while upload a asset is triggered .

I Just did set to true this:
$config['csrf_protection'] = TRUE;

at fuel/application/config.php

Thanks,

class Blocks_model extends Base_module_model {

    public $language = 'en_EN';

    (...)
}

class Block_model extends Base_module_record {
    
    function get_language()
    {
        return $this->language
    }
}

class Block_model extends Base_module_record {
    
    function get_language()
    {
        $CI = &get_instance();
        $CI->load->module_model('fuel', 'blocks_model');
        return $CI->blocks_model->language;
    }
}

$fields['image']['type']               = 'file';
$fields['image']['upload']             = true;
$fields['image']['multiple']           = false;
$fields['image']['multiline']          = false;
$fields['image']['overwrite']          = TRUE;
$fields['image']['display_overwrite']  = false;
$fields['image']['display_preview']    = true;
$fields['image']['create_thumb']       = FALSE;
$fields['image']['width']              = 1280;
$fields['image']['height']             = 1280;
$fields['image']['maintain_ratio']     = TRUE;
$fields['image']['resize_and_crop']    = false;
$fields['image']['resize_method']      = 'maintain_ratio';
$fields['image']['master_dim']         = 'auto';
$fields['image']['file_name']          = '{slug}'; // '{id}-{slug}' isn't working?

I end up with small images being blown up to 1280px, which is kind of weird, because it needs more space and quality gets worse.

Right now, I'm overwriting Fuel_assets::upload - but I don't like to keep track of this complex function if something changes later. So I wish there was a parameter to tell fuel "only resize if orig image if larger than $fields['image']['width']

Here is my fuel\application\libraries\MY_Fuel_assets.php

<?php

// in Events_model.php I do this:
//$CI->load->library('MY_Fuel_assets, array(), 'fuel_assets');

require_once(FUEL_PATH . 'libraries/Fuel_assets.php');

class MY_Fuel_assets extends Fuel_assets {

    public function upload($params = array())
    {

            // ... all the code of the original Fuel_assets::upload() method

                $this->CI->image_lib->initialize($params);

                // check for if they want just a resize or a resize AND crop
                if (!empty($params['resize_and_crop']) OR (!empty($params['resize_method']) AND $params['resize_method'] == 'resize_and_crop'))
                {
                    $resize = $this->CI->image_lib->resize_and_crop();
                }
                else
                {
                    $resize = true;
                    // resize only if image is wider than $params['width']
                    if ($this->CI->image_lib->orig_width > $params['width']) {
                        $resize = $this->CI->image_lib->resize();
                    }

                }

                if (!$resize)
                {
                    $this->_add_error($this->CI->image_lib->display_errors());
                }
            }
    }

}

Could this become an option in a future version?

I learned a great deal by finding solutions here on the forum, especially in answers by @admin, but they are quite hard to find (I'm not using the internal search, but the google index with site:forum.fuelcms... and hard to parse (people just dropping in large chunks of code without formatting, the yellow background of code blocks are weird etc).
Sometimes I bookmark issues, but rarely go back to them - instead I refind them via google.

Another issue is to contribute to the docs, by cloning a full instance of FUEL via Github, change HTML and send pull requests. I know this is how Fuel grew and the docs are partly generated from the sourcecode, but... maybe there is a better way to move forward?

1. So I wonder if it's worth to explore the possibility to create a community wiki on github to let people share their solutions. I know this has to be moderated, on the other side, with a strict guideline this could be possible, since it's a small community.

2. Also, without reinventing the wheel, do you think it's possible to move/export the docs to markdown in a separate repo, just one branch, so "everybody" can quickly fix or enhance the docs via Github's Webinterface and send a pull request, that you decide to take in.

These are just loose thoughts, none of this has to happen, since it needs resources that nobody has , but if...

Thanks

** Any ideas? **

Thanks!

I was able to add and extend the Fuel Postgre Drivers by trial and error. (I think it comes down to rewrite some queries that are not written in strict sql like this:

// mysql LIKE "%xo%"
array_push($$joiner_arr, 'LOWER('.$key.') LIKE "%'.strtolower($val).'%"');
// vs.
// postgre LIKE '%xo%'
array_push($$joiner_arr, 'LOWER('.$key.') LIKE \'%'.strtolower($val).'%\'');

My question is:

1. did you already try to make it work for postgre?
2. if not, what's the best way to go through the code, without trial and error?

In the postgres post from 2011 there were talks about writing tests, but that's unknown terrain for me.

Best, Marcus

if there is not built-in function to do so. can I create a custom button in the list view and check that which rows are selected?