Small Bug in EJuiAutoCompleteFkField

As I’m new to the community I suffer from certain limitations, e.g. I can’t comment on ejui-autocomplete-fk-field extension. As it didn’t work for me out of the box I was looking into the source and found one small bug (at least I think so) and here it is:


parent::init();

should be called in public function init(). Otherwise necessary assets will not be loaded.

Hope, this helps.

Furthermore IMHO it would be more convenient to call the class EJuiAutoCompleteFkField as filename suggests (Fk instead of FK) or the other way round.

Bests, mubo

Thanks for the info. Was looking for a way to include the js file manually, but this is much better.

Yep. Just tried to post this at extension comments area but I’m too young for comment there :mellow:

Thank you everyone for commenting. Yes, parent:init() is missing. The reason why it works for me (and I didn’t notice this previously) is I have published a lot of assets in my views/layouts/main.php. I will post an updated version to the Extensions directory soon. For now, anyone with this problem can simply add




parent::init();



as the first line of init() in the extension.