darondaron

@abhikr781

Why do think, or where do you see I have used Elementors Theme builder for creating my Header and Footer?
And if I had, why would that be a problem?

Now, I have NOT used Elementors Theme Builder. You do need the PRO version to do that, which I have not.
I was in Theme Panel>My Library and “Add new” there, to create my header&footer.

I can redo my Header and Footer, but need to understand what is wrong first, otherwise I will just do exactly as before…

Best regards
Daniel

Hi

The Footer (and Header) Template is Elementor Canvas. There is no width set. (But the pages built in Elementor is Full width with default elementor width of 1140px)

I have extracted all CSS code, and the margins in the footer do not change at all.

I have tried disabling plugins but margins look the same.

I have set up a staging site if you can take a look there? How can I contact you for that?
BR
Daniel

Hi @abhikr781

The Header and Footer are build as a template already in Theme panel > My library
And that Custom header/footer is selected already as Custom in the customizer as you suggest.

Yes, I am aware of how to work with responsiveness in Elementor.

But my issue here is/was that the Footer I have done in Elementor changes on the Archive and blog postpages, which was not created in Elementor.

I believe the page width or margins are different on the Archive and blog post pages. But I have tried change OceanWP width from 1200 to 1140 which should be Elementors, and there is absolutely no change. So if width is the problem, it’s not working to change that in Customizer.
Why is changing Main Container Width from 1200px to anything not showing? nothing happens. I use Layout style Wide.

BR
Daniel

Have experimented with ACU and AO settings to avoid conflicts, works very well now thank you!

Absolutely, done ??

Hi

Yes, thank you.

I disabled CDN, now only using Optimole with their CDN.

Still had some issues with conflicts with Asset Clean Up plugin, but now it works, and JS are deferred as they should by AO.

Thanks for follow up!

Hi

Footer used on all pages and as said done in Elementor, and works well with Elementor pages.
Link to snapshots:

1st & 2nd image: Elementor pages, margins good at footer text in the bottom and social buttons aligned. 3rd and 4th image: OceanWP/archive page, margins much less at bottom text and social buttons moved to left.

1st & 2nd image: Elementor pages, margins good at footer text in the bottom and social buttons aligned. (url: https://www.agrara.se)
3rd and 4th image: OceanWP/archive page, margins much less at bottom text and social buttons moved to left. (url https://www.agrara.se/nyheter)

In the footer, text is centered, but the buttons that are not centered on the Archive page are left-aligned, (can not center shortcodes , and icons did not behave centered, an Elementor thing)
But does it now show that the width of the page is different? since the left aligned widgets get skewed to the left on the Archive page. And margins change.
This is just on mobile, on tablet similar but worse. Computer works better, but still the margins are noticeably smaller on the Archive page.

Why do you think? have tried “a lot”.

Best regards
Daniel

Hi

Not sure how to add snapshots here.
And I thought I provided the link in the post, but comes here:
https://www.agrara.se/nyheter/

very short page, you can not miss it.

Best regards
daron

Honestly can not say. Have not tried and tested without ACU. Only found the 2 times I have activated ACU (with AO activated) that when activating ACU , then AO did not defer.
And after deactivating ACU defer worked again.
So, I would not really know if this happens when ACU is not used, both because I want to use it, and also I do not see clear warning, unless I look for deferred JS in html.

Sorry, have not investigated more.

I have never used aggregate in AO, only enabled “Do not aggregate but defer?”.

I looked through settings now, and there was some Core emoji removal that could interfere. And perhaps (not sure) “Remove query strings from static resources” that could interfere. I did not see any other overlap.

But could of course missed something. When it has happened and made it work, I never changed settings, just in order how the plugins was activated.

Ok, thanks!

Yes, regarding ACU, I only use AO for minifying. Do not want plugins to interfere.
But still, there are some glitch, and I have not seen ACU being affected by it.
Problem is for me, only way to see AO was not working properly, was when I saw JS was not deferred anymore (after installing ACU), otherwise not easy for me to discover.

BR
Daniel

• This reply was modified 4 years, 2 months ago by darondaron.

The childs css style only had the default comment section in the top with theme, author, version, it still did not work, just of not using

I found the issue, but very difficult to understand.
In my (sticky) Header for the whole website, I had not specified a Z-index, and the Header worked and was on top as long as the childs style.css was the same version as the parent version. When I changed version on childs style.css everything broke.
Now added Z index to sticky Header, so that works, and can now change childs style.css version to whatever, or just leave it on v.1.0.

Try to figure that one out! beats me. But somehow the version number seem to control certain things.

I still don’t see Childs style.css changes in the WP Customizer, or in Elementor. So if I change e.g. text color on something, in Childs style.css, I can not see that color change in Customizer or Elementor, but works perfectly on the live webpage.
Do you know what can cause this? or what to do? or perhaps it common..

BR
Daniel

I found the problem. Had in the themes Child folder been playing around with some JS files, trying new scripts, and one was named “Global” which seemed to initiate a http request on page load for a Global.js in the Parent theme.
I do not have enough knowledge to understand that…

Then what on earth can suddenly have created a request for global.js …

Not sure how I can see what made the request.

@abhikr781

Hi

Tried as suggested, but just replacing current child style.css did not work.

As I said, when the version of the childs style.css differs from what I have now v2.0.0 (same as in the parent theme), a lot of strange css breakup happens. And the template child style.css has version 1.0, so that did not work.

This is Not due to having any CSS code in the childs style.css, it’s happening on many different things on the website, that does not have any dependent code in the childs style.css . I have tried removing all css code from the childs style.css, but same problem that if I change the version of it, strange things happen.
So, putting a new child sample style.css in place gives the same error and problem as I have.
My question is how I can reset this? want to come back to a working child theme, with no version problems.
Please advice ??

Thanks!
Best regards
darondaron

• This reply was modified 4 years, 2 months ago by darondaron.