Search Results for 'composer'

Hi Vlad,

Ok, after much head scratching and page testing, there is definitely something wrong with my theme.

1) Even if I import a page or section template in tagDiv Composer and do nothing to it, except save and view. None of the rows will display as full width. This is the case in Composer and the page itself.

2) I created a new footer page, using an imported template with a similar layout to my own (1 row/3 columns for the footer, 1 row/2 columns for the sub-footer). I did nothing to it, except set the sub-footer menu and reduce the font size.
– The result: in tagDiv Composer, the columns are stacked in both the footer and sub-footer and neither row shows as stretched. When viewed in situ on a page, the rows and columns behave as they should and align horizontally. Small win…
– For some reason, the last couple of days the import feature isn’t working properly either. When I click the button to import, the confirmation box appears behind the import modal – the only way to click OK is to add display:none to the modal via Chrome Dev Tools.

3) Unfortunately, #2 only works with pages created using tagDiv Composer and WPBakery. Any pages created using Gutenberg, seem to break the footer CSS. The page structure (for the footer section/page) is the same, but some of the same CSS is being overwritten, as it appears to come after in order of specificity. In Chrome Dev Tool, the ‘winning’ styles appear above the ones being overwritten.
– In pages created using tagDiv Composer or WPBakery, I still can’t get any rows to stretch no matter what I do (believe me, I’ve tried!).
– The only way to get stretched rows of any kind, is to build pages using Gutenberg Blocks and plugins. Which is why all of my pages are showing a broken footer, because I had to go back to basics as the other 2 methods are currently unusable.

The solution:
#ti-copyright-footer .td-pb-span6 { width: 50% !important; }

I’ve added the code to the Live CSS window for the footer page and given the row an id, so it won’t conflict with anything else (hopefully). It feels like a bit of a hack, as I’m not a developer and generally wouldn’t mess with the structure of a page, for fear it’ll mess up it’s responsiveness (media queries, etc). I haven’t tested that yet, but it’s nearly 1am, so that’s it for now…

I’m hoping this level of detail might give you a better idea of what’s going on, so that you can help me resolve it properly. I’m not convinced that’s the best fix (it was way too easy), unless you can confirm it won’t effect anything else on the site. Or perhaps you can come up with a cross device/cross platform solution?

Many thanks.

Hi Vlad,

That’s what I did, it was certainly working across the site in the beginning and it still is on one page. However, on the pages that are broken .td-pb-span6 is being overwritten by .vc_column_container: 100%, whereas on the page that is displaying properly, it applies the 50% width (I can send you screen grabs, if you like).

I’ve just checked in tagDiv Composer – the outer row is set to 1 column, stretch row and content (with padding). The inner row is set to 2 columns, full width content. Shall I recreate it, as just 1 row with 2 columns? I’m worried something will break if I start messing with it.

I don’t understand why the 50% width is being overwritten on all pages, except one. Is that not weird?

Thanks

Can I use externan plugin to do the same ?. How can I integrate into tagdiv composer ?

Hi,

Thanks for the reply.

Does this mean search engines will not properly read/rank ‘pages’ made with the TagDic Composer?

Thanks

Hi Vlad,

No, I’ve seen this answer before, so it hasn’t really helped and you haven’t commented on the issue with the footer.

I don’t need the whole site to be full width, I just need the odd row to stretch to full width, ie to accommodate a background image or colour. To clarify, if I have a page with 8 rows and want one row @ full width, I must select each row individually and set it to stretch (whichever setting is appropriate, as long as it’s not the default). Is that correct?

What about the footer ‘page’? It consists of only 2 rows, both are obviously set to stretch, but it doesn’t show as stretched in tagDiv Composer – is this the way it’s supposed to work? Thankfully it does actually stretch on the page, but as detailed above, the 2 columns in the sub-footer are stacking, instead of showing inline (even though it was fine before and hasn’t been changed).

Any thoughts?

Thanks again Calin,

1) I think you’re confirming for me that when the button says “create page” the result is a page in the Pages list, not a template in the “cloud template” list. For example, when I download the Category template 22-Nomad and click on the button, which in that case says “create template”, it ends up in the “cloud template”list and I presume you can use that in creating other pages. By going through the same process with the Contact – nature love template, the button says “create page” and the result ends up as an actual page in the Page list. If that’s the way it’s supposed to work, then I’m good. I am just trying to understand the design intent.

2) I’m good on this one — it’s my photographer mentality. I actually created a pic at 1200 X 648 pixels in an attempt to ensure the subject’s face was in the center of the image area — but then I realized that I totally negated the parallax effect by doing that. Live and learn. So I totally understand this one now. Thanks…

3) In this case, the tagDiv Composer is working. I can set and move blocks around and make changes in the General, filter and other tabs. The only part that doesn’t work is when I am on my Contact page in tagDiv Composer — I click on the form and the proper left-hand controls appear, then I click on the black EDIT CONTENT button and the pop up window appears so I can edit the form short-code. That’s the part that won’t load. The field never appears that allows me to change the form shortcode. The circle just keeps on circling… Does that make sense?