Please use our Google Group for support requests. (https://groups.google.com/forum/#!forum/joomla-dev-general)

This is the issue tracker for Joomla core.

It is not a support request. I got everything to work but only if I change the class names to VehicleMdel instead of VehicleModel. This is a problem with how Joomla core processes model names that contain the legitimate use of the word 'Model' like 'Vehicle Model' or 'Bikini Model'.

As mentioned, the problem is very case specific. Was just pointing it out. Again... not a request for support ;-)

I can reopen it.

Are you using a view class named "VehicleModel" then? Because by default our MVC will try to guess the model name based on the current controller name and the view name. So usually you would have a model class named "ComponentModelView", while "ComponentModel" is the "model prefix". You got a part to much in there somehow anyway.

Shouldnt it be VehicleModelModel because Vehicle and model are the name
and the final Model the MVC

On 9 August 2015 at 13:15, Thomas Hunziker notifications@github.com wrote:

I can reopen it.

Are you using a class named "VehicleModel" then? Because by default our
MVC will try to guess the model name based on the current controller name
and the view name. So usually you would have a model class named
"ComponentModelView", while "ComponentModel" is the "model prefix". You got
a part to much in there somehow anyway.

—
Reply to this email directly or view it on GitHub
#7665 (comment).

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

My component name is 'Arms' (com_arms) and the:

ArmsModelVehicleModel extends JModelAdmin
was the model that caused the problem.

I noticed it trying to get the list view to display a filter. The second 'Model' in the model name seems to break something because the Joomla core picked up the incorrect 'option' (should have been 'com_arms', but was 'com_armsmodelvehicles') when I did a var_dump in the view. Core could then not find the filter.xml for the view despite the file being correctly labelled. That then caused the error 'Call to a member function getGroup() on a non-object bar.php'.

It cleared up as soon as I changed everything that contained 'vehiclemodel' to 'vehiclemdel'.

I experienced no problems with any of the other models.

@brianteeman As I said earlier, I'm new to Joomla component development... Perfectly prepared to accept this as my own daftness and have the report closed ;-)

What is the name of the view? Because as explained the model name consist by default of three parts, and yours is four (Arms, Model, Vehicle, Model). If the viewname is indeed "vehiclemodel", then the model should be named "ArmsModelVehiclemodel" instead.
I'm not saying this is the source of the fault (probably it isn't), but it certainly is something which doesn't follow the norm.

The view name was

class ArmsViewVehicleModels extends JViewLegacy

The strangeness is all the other views and models that follow a similar pattern work:

class ArmsViewVehicleManufacturers extends JViewLegacy
class ArmsModelVehicleManufacturers extends JModelList
class ArmsModelVehicleManufacturer extends JModelAdmin

And I'm going to fess up here and say I totally cheated by using a component builder ^_^. But I have taken a note of the naming convention you pointed out - thanks!

I have the component package with just the 'vehicle model' class if you'd like to have a look.

Just try to lowercase the last bit, making it a three part name. It will reduce potential issues in future for sure and maybe even solves the issue at hand.

I thought this was fixed already: https://groups.google.com/forum/#!topic/joomla-dev-general/IWVqNQYjSAY

I am quoting Don’s solution here, that worked for me back then:
To fix it, you need to set the $option and the $name parameters in your model.

class TestModelModel extends JModelAdmin
{
    protected $text_prefix = 'COM_TEST;
    protected $option = 'com_test';
    protected $name = 'model';

The lower case 'model' resolves the list view issue, but it does not appear to resolve the individual edit view problem - although I don't know why that is. I have attached screen shots of both 'Vehiclemodel' (warns that it can't find component, although it saves the item fine) and 'Vehiclemdel' (works without issue).

I'd say raise it on the Google Group I mentioned earlier with all the error messages you get.
I'm quite sure it can be solved in code.
If not and there is indeed an issue in core, you can always create a new issue.

@dgt41 Thanks for that code snippet - will be sure to use that fix if I face this situation again. Otherwise, everything works fine with Mdel and not Model. Going ahead with that for now. Thanks!