Virtuemart upgrade makes my css out of work
- GK User
- Thu Oct 22, 2015 1:01 pm
Hi,
to keep a personal css for Virtuemart, changes must be made into template/html/com_virtuemart. OK.
The problem is with my category pages which are displayed with components/com_virtuemart/views/category/view.html.php.
This path doesn't exist into gk_storefront/html/com_virtuemart/category/ (no "views" folder)
so each time I upgrade Virtuemart I have to replace the view.html.php file I modified.
Should I have to create "views" folder into gk_storefront/html/com_virtuemart to suit with the original Virtuemart folders ?
to keep a personal css for Virtuemart, changes must be made into template/html/com_virtuemart. OK.
The problem is with my category pages which are displayed with components/com_virtuemart/views/category/view.html.php.
This path doesn't exist into gk_storefront/html/com_virtuemart/category/ (no "views" folder)
so each time I upgrade Virtuemart I have to replace the view.html.php file I modified.
Should I have to create "views" folder into gk_storefront/html/com_virtuemart to suit with the original Virtuemart folders ?
-
- Gold Boarder
- GK User
- Sat Oct 24, 2015 11:38 am
In Short - you can't .
Let me explain it a little bit more, for example lets take this path:
/components/com_virtuemart/views/askquestion/tmpl/form.php
you will find exactly same file in our template:
/templates/gk_storefront/html/com_virtuemart/askquestion/form.php
what you need to omit is views and tmpl folders (in template structure) to create correct override.
But with files such as:
components/com_virtuemart/views/category/view.html.php
its not possible to create their override php file in template itself. And the problem is that original VM designers didn't suspect anybody would need to change that file.
Let me explain it a little bit more, for example lets take this path:
/components/com_virtuemart/views/askquestion/tmpl/form.php
you will find exactly same file in our template:
/templates/gk_storefront/html/com_virtuemart/askquestion/form.php
what you need to omit is views and tmpl folders (in template structure) to create correct override.
But with files such as:
components/com_virtuemart/views/category/view.html.php
its not possible to create their override php file in template itself. And the problem is that original VM designers didn't suspect anybody would need to change that file.
-
- Moderator
- GK User
- Mon Oct 26, 2015 10:31 am
Ok thanks Cyberek.
I had to modify the file to add div for my customer needs
I will take care to overwrite the file at each upgrade
have a good day
I had to modify the file to add div for my customer needs
I will take care to overwrite the file at each upgrade
have a good day
-
- Gold Boarder
- GK User
- Tue Oct 27, 2015 10:28 am
Maybe you could use tmpl files instead? It's the place where div should appear, not "controller" files.
-
- Moderator
- GK User
- Tue Oct 27, 2015 10:45 am
I just checked this file, could you please post an info on what do you change in this file?
-
- Moderator
5 posts
• Page 1 of 1