I’ve just upgraded the theme – and dealt with all the child theme issues and plugin issues… That was not cool – so glad the client site is not yet public.
Anyway – even though I have reset the child theme back to defaults, my big grids are hitting a width issue, they show fine when I swap back to the parent theme, but when I view with the child theme the container width gets smaller and the subsidiary posts roll over onto a new row.
Please advise.
Hi,
Please make sure that you have also update the child theme at the latest version, because the old version will not work fine. It should work fine as it was tested and also we work to the API documentation it will be available soon. Until then you please use the main theme as only files from the root of the theme can be overwritten.
Thanks!
Child theme updated / replaced with the latest version, all caches cleared etc. Still an issue. The only Big Grid that fits is the Big Grid Slide. All others wrap over. Comparing Slide with Grid 2 – Slide is set in a 1068px wrapper div and Grid 2 set in a 1050px (inherited) width div, with 741px main and 324px additionals for both.
Hi,
We also have investigated this and seems to be an issue with the grid when the child theme is used, it will be fixed in the next update.
Sorry for inconvenience and thanks for reporting this!
-
This reply was modified 11 years by
Alin [tagDiv].
So – next update arrived – installed – same issues remain. Please advise.
please contact us and if possible give us wp-admin access. contact@tagdiv.com
It may be some kind of plugin incompatibility or visual composer and speed booster are not at the latest version
See @batman post (https://forum.tagdiv.com/topic/big-grid-1-and-2-problems-on-newspaper-6-and-6-1/#post-55067) which pushes the priority of enqueuing of the theme style to the bottom of the pile. Copied here for those of you following this thread:
Open up the functions.php from the child theme and add 1000 priority to the wp_enqueue_scripts action:
add_action( 'wp_enqueue_scripts', 'theme_enqueue_styles', 1000);
Hopefully the tagdiv team will plug this hole shortly.
