Hello, if you go to https://www.fortegaragefloorcoating.com/category/garage-floor-coating/ you will see the masonry for the archives is appearing extremely thin when on full resolution. Once the viewport breaks to a smaller size it appears fine all the way down to mobile. Desktops with large resolution it is completely broken. Can you please assist?
Hi @powersnw,
Thanks for reaching out.
It seems that your website has the Mixed content issue [ HTTP and HTTPS ]. It might be a problem with migration or SSL certificate implementation. You need to replace the URL with the HTTPS URL. I would suggest you go through the migrate article especially how to Search and Replace the URL.
What you are facing in Masonry has been fixed a few releases ago. I have checked it in my local environment and found it is working fine. It seems there might be some different reasons behind your issue. I would like to suggest troubleshooting the following common issue to help us recognize the reason.
1.Theme Related Issue
2.Plugin Conflict
3.Theme Update related issue
4.Child Theme Related issue
5.CSS/JS Customization
6.Disabling Cache
7.Disabling CDN
If you discover that an issue is coming from a custom code or 3rd party plugin, kindly consult with a developer or contact the plugin author. Please note that we do not provide support for custom codes and 3rd party plugins.
If this does not help, please provide login credentials for your site in a secure note to examine it further, including:
– WordPress Site URL & Login URL
– WordPress Admin username/password
To create a secure note, click the key icon underneath any of your posts.
Thanks
I have already disabled all plugins and it does not change the issue. The http/https has been fixed and still no luck. Any other help?
Also switching from the child theme to the regular theme makes it look better however there are still issues where it changes on scroll and window sizes.
Hi @powersnw,
If you have already performed all the troubleshooting points, I would suggest you please copy your live site to a staging server so we could troubleshoot freely without breaking your live site.
And give us access to the secure note including:
– WordPress Site URL & Login URL
– WordPress Admin username/password
To create a secure note, click the key icon underneath any of your posts.
Thanks
Hey @powersnw,
The issue could be just the cache.
Please check out this documentation first:
Best Regards.
Saying that “could be” the issue is not helpful. I have already stated that disabling ALL plugins makes no difference. Something is wrong with the theme and I need help please. I have disabled the WP Rocket plugin which is not causing this as the same plugin setup works fine on other sites. I tried clearing Cornerstones cache as well and it still loads the masonry incorrect.
Hey @powersnw,
Can you please re-install the Pro theme? This must be done manually by renaming the current Pro theme folder into an “old-pro” one and then uploading the latest version of the Pro theme.
Kindly let us know how it goes.
I reinstalled both the Pro and Pro Child themes, no change.
I am going line by line in CSS and noticed at 1450 width pixels I have the break for the navbar to switch to the mobile button and thats when the blog loads correctly.
.x-nav-wrap.desktop {
display: none;
}
makes the blog function correctly and the three columns appear. However that removes the navbar. Why would this be happening?
Hi @powersnw,
I investigated your staging site and found that the child theme is the reason behind your masonry issue, which was resolved after activating the parent theme. Also, the Static Top header instead of the Fixed Top header fixes the layout shifting while scrolling.
Hope it helps.
Thanks
Ok so I have a few issues with this response. The child theme is the problem yet when using Fixed Top which is part of the Parent Theme it still causes viewing issues.
So the problem is not fixed. If the masonry items are still shifting upon scroll when Fixed Top is selected thats not a fix. I already found the CSS causing the initial display issue in the Child Theme and asked you why that code would cause this, you ignored my comment about this. Can I please get support that helps fix ALL the issues present as of now this is still showing an issue in the Pro Parent Theme. This is also a code that creates the issue as well:
.masthead-inline .desktop .x-nav {
display: block;
float: right;
margin-top: 20px;
}
The reason why a child theme is needed is because Pro and X themes have decided its a good idea to remove the blog categories and tags from displaying. I have to add a workaround in the functions.php for this as well as Google Tag manager and other tracking codes. I am starting to have quite a bit of issues with the lack of features that keep getting pushed into these themes. Removing important components by default with no easy way to enable them is bad practice.
Hi @powersnw,
The issue with the Fixed Top has been already reported to our development team and they are looking into it. The issue with CSS code is completely different, which does not solve the actual case. I also checked the child theme and a few code in functions.php is affecting the archive page. So, I would request you check the code if you still want to use the child theme.
Please remember that we don’t offer any support for custom coding or related issues.
Thanks
Ok so what is the correct code to display the blog categories and tags on the pages? The code I added was from an old post on here in the support forums so if that code is not accurate anymore can you please update it here?
Hi @powersnw,
To set up the blog properly, I would suggest you set the Header as Static Top for now. The issue has already been fixed and will be released in an upcoming update. After that, you set the Header back on Fixed Top.
Thanks
Ok…
What is the code to add to functions.php to display blog categories and tags on the blog page and posts?
Hi @powersnw,
I would request you create a new thread for this to avoid any confusion in the future.
Thanks
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.