Problem "Records Module"

As already mentioned in another bug report, i can not use 2 different templates for the modules. All changes done on 1 module overwrite template will affect the other module template.

Some translations are also missing:

Select Section -- CSELECTSECTION

Template Overwrite --> X_DONOTOVERRIDETMPL

yep, same problem here

Yes, this is quite a limitation :(

When i apply a filter on the component (same section as the modules) the filter applies to the content of my modules and shows the same result as the search, which is obviously different than the expected output.

Fixed.

When i apply a filter on the component (same section as the modules) the filter applies to the content of my modules and shows the same result as the search, which is obviously different than the expected output.

As already mentioned in another bug report, i can not use 2 different templates for the modules. All changes done on 1 module overwrite template will affect the other module template.

Could not reproduce it even on the site with mentioned case.

When i apply a filter on the component (same section as the modules) the filter applies to the content of my modules and shows the same result as the search, which is obviously different than the expected output.

As already mentioned in another bug report, i can not use 2 different templates for the modules. All changes done on 1 module overwrite template will affect the other module template.

Select Section -- CSELECTSECTION

Template Overwrite --> X_DONOTOVERRIDETMPL

Do not know how to load Cobalt language file on module setup. Probably need to create module separate language file.

Could not reproduce it even on the site with mentioned case.

I have 2 "Record Modules" on the same page. They have different ids. I selected on both of them the same list template (example "table"). Now if i make changes on 1 modules template override, it affects the 2nd module --> the second module now has the same template settings as the 1st module.

Additional info to the setup:

The section on the page and also the section of BOTH modules is the same.

Did you copy that module or created new one? This is matters very much. If you made copy then yes it is connected. To get new template configuration key you ned to create new module.

module was copied ... hmm, ok, but that is the normal way of doing it under Joomla, right?

A normal user would not even think of creating a new module -- just copy and change the parameters ... anyway, i can create a new one, but would suggest to find a solution for it to avoid confusion in the future.

Question on the side:

How can i determine if there is a query on the side and act on it in the module ... - Thinking of using the url (query for cat_id) together with the "filter wornings".

How can i find out if there is a "filter worning" inside the module?

 Sackgesicht

As already mentioned in another bug report, i can not use 2 different templates for the modules. All changes done on 1 module overwrite template will affect the other module template. 

Could not reproduce it even on the site with mentioned case.

I solved it. The problem is default_list_blog.php template

if default_list_blog.php is being used for a module on the same page where there is already another module using a custom template

made by copying default_list_blog.php

then default_list_blog.php get overwritten by the custom template of the other module

this happens also if you have 2 modules with 2 difefrent custom templates, if the 2 custom templates have been made by copying default_list_blog.php

To solve this for now just make custom templates using different default templates

eg. to solve my problem I made a custom template with default_list.php

and another one with default_list_blog.php

I do not think it is possible. The worninigs are detected only after query is built. And since I had fixed filters in module it will not be affected anymore.

Did you copy that module or created new one? This is matters very much. If you made copy then yes it is connected. To get new template configuration key you ned to create new module.

ah... maybe then I just "thought" I found the catch :S