responsive menu doesn't work
- GK User
- Fri Sep 23, 2016 4:22 pm
Hi
I can't find why on my website, menu is not responsive with "hamburger" style
on the demo storefront website you can see the "hamburger" menu on small screens
on mine, no way to have it working. Could you help with that issue ?
http://cgigraphicdemo.fr/expovisions/
thanks
I can't find why on my website, menu is not responsive with "hamburger" style
on the demo storefront website you can see the "hamburger" menu on small screens
on mine, no way to have it working. Could you help with that issue ?
http://cgigraphicdemo.fr/expovisions/
thanks
-
- Gold Boarder
- teitbite
- Sun Sep 25, 2016 11:39 am
Hi
I can see that even a normal menu is not showing correctly. Have You done any changes to template's style ?
I can see that even a normal menu is not showing correctly. Have You done any changes to template's style ?
-
- Moderator
- GK User
- Sun Sep 25, 2016 4:03 pm
unfortunately I didn't (as far as I remember)
I also tried to deactivate override.css
I'm lost...
I also tried to deactivate override.css
I'm lost...
-
- Gold Boarder
- teitbite
- Mon Sep 26, 2016 2:01 pm
Hi
I see now that changes was done not in style, but in php. According to validator You have an oppening tag for <body> twice: https://validator.w3.org/nu/?doc=http%3 ... visions%2F Try fix it please.
I see now that changes was done not in style, but in php. According to validator You have an oppening tag for <body> twice: https://validator.w3.org/nu/?doc=http%3 ... visions%2F Try fix it please.
-
- Moderator
- GK User
- Tue Sep 27, 2016 10:26 am
ok thanks
do you have an idea for how to find the php file that has this weird error ?
I can't find the reported line
do you have an idea for how to find the php file that has this weird error ?
I can't find the reported line
-
- Gold Boarder
- teitbite
- Tue Sep 27, 2016 12:55 pm
Hi
Unfortunately not. I also do not have an installation for joomla 2.5 any more. You will need to update Your joomla to 3.6, which is much safer than using old vulnerable to attacks version.
Unfortunately not. I also do not have an installation for joomla 2.5 any more. You will need to update Your joomla to 3.6, which is much safer than using old vulnerable to attacks version.
-
- Moderator
- GK User
- Tue Sep 27, 2016 1:30 pm
too bad.
Yes I'm upgrading to 3.6 but I still have to make some css changes for VM - and not enough time to finalize it.
That's why I search for this issue which is a priority for the current website version.
I changed site template with Beez 20 and saw that the error was not displayed with the validator
so the specified "body" tag is somewhere in Storefront... hard to find.
Yes I'm upgrading to 3.6 but I still have to make some css changes for VM - and not enough time to finalize it.
That's why I search for this issue which is a priority for the current website version.
I changed site template with Beez 20 and saw that the error was not displayed with the validator
so the specified "body" tag is somewhere in Storefront... hard to find.
-
- Gold Boarder
- GK User
- Tue Sep 27, 2016 6:03 pm
]I see now that changes was done not in style, but in php. According to validator You have an oppening tag for <body> twice:
Hi
I fixed that (a div was placed before "body" tag) so I removed it
this didn't fix the issue unfortunately.
The problem is not there..
-
- Gold Boarder
- teitbite
- Thu Sep 29, 2016 2:00 pm
Hi
Beez 20 doesn't use same module positions, so if problem is in module it would not be visible after changing.
Try unpublish all modules and see if problem is visible than, but I think it indeed can be in php, after some old changes. You may try replace some of the files with version version for joomla 3.6. Mostly files from /layout folder are what matters.
Beez 20 doesn't use same module positions, so if problem is in module it would not be visible after changing.
Try unpublish all modules and see if problem is visible than, but I think it indeed can be in php, after some old changes. You may try replace some of the files with version version for joomla 3.6. Mostly files from /layout folder are what matters.
-
- Moderator
- GK User
- Thu Sep 29, 2016 4:58 pm
okay, I've found the original Storefront 2.5 version
I gonna try to rename firstly "html" in template/storefront/ and uplaod the original html
and continue the same action with other folders till I find where's the bug.
I let you know if I find
I gonna try to rename firstly "html" in template/storefront/ and uplaod the original html
and continue the same action with other folders till I find where's the bug.
I let you know if I find
-
- Gold Boarder
- GK User
- Thu Sep 29, 2016 5:39 pm
Really weird !!
I renamed folder template/gk_storefront-bak
uploaded folder from original quickstart gk_storefront to template/gk_storefront
same issue...
I renamed folder template/gk_storefront-bak
uploaded folder from original quickstart gk_storefront to template/gk_storefront
same issue...
-
- Gold Boarder
- GK User
- Thu Sep 29, 2016 5:46 pm
OK now.
tried to reinstall the template without uninstalling first : same issue
tried to uninstall, then install the template again : It works
The DB or caching system should be affected
I know what to do now... (It's a long way to go....)
tried to reinstall the template without uninstalling first : same issue
tried to uninstall, then install the template again : It works
The DB or caching system should be affected
I know what to do now... (It's a long way to go....)
-
- Gold Boarder
- GK User
- Fri Sep 30, 2016 12:41 pm
Solved !
after configuring the template on the new install, I can see everything is ok now
my job is to finish the 3.6 Joomla version for this website and use Storefront for J!3.6
Thanks for the support
after configuring the template on the new install, I can see everything is ok now
my job is to finish the 3.6 Joomla version for this website and use Storefront for J!3.6
Thanks for the support
-
- Gold Boarder
- teitbite
- Sun Oct 02, 2016 12:32 pm
Hi
I think after replacing the files problem was solved already, but was still loading old files from cache. Template is not using database except for the one record where informations about it are stored during installation.
I think after replacing the files problem was solved already, but was still loading old files from cache. Template is not using database except for the one record where informations about it are stored during installation.
-
- Moderator
14 posts
• Page 1 of 1