This topic has 5 replies, 2 voices, and was last updated 9 years, 2 months ago ago by Jimbo
Hi,
FAO: Olga Barlow
As this problem was not solved in my other post I will start again.
My footer is not fully responsive on the iPad, columns 3 and column 4 go into each other, the blog post circles go into my Twitter feed.
Website in private.
Feel like I’m being ignored now.
It’s ok I will hit the contact a manager button!
I have sorted this with out your help.
However your theme does not support twitter widgets created through twitter and added into the footer, it breaks your theme!
My choice is to use your widget for theme which is dull and boring, no styling at all!
I am sure you will be quick enough to close the topic.
YOU GUYS ARE NOT SO GOOD AT SUPPORTING ISSUES WITH THIS THEME, AND TRUST ME THERE ARE ALWAYS ISSUES WITH UPDATES.
Thanks!!
Hello,
We are glad you sorted out problems with footer. As a rule we fix the issues related to theme functionality in every theme update. Sometimes new problems could appear because of implementation of some additional features, but we try to solve them ASAP. Theme support does not include services to modify or extend the item beyond the original features, style and functionality.
What element did you use to add twitter code? Use Raw HTML VC element. Twitter widget works without any problems on our installations.
Regards,
Olga Barlow
Firstly it was not beyond your theme, it was adding something to the footer area of your theme which was causing the footer area to break its responsive design.
Anyway I found the cause, I use the same Twitter code generated by Twitter on another theme (not supplied by you) and it works without adjusting the code which I had to do on your theme.
I had to remove no scrollbar using data-chrome attribute, funny as it works without doing this in my other theme?
I do have another issue with visual composer posted on another topic, but no doubt you wish to put the blame on visual composer?
The issue related to '‘WOOTHEME NOT FULLY RESPONSIVE’' has been successfully resolved, and the topic is now closed for further responses