The Grid not working / displaying

Hi! I’ve encountered problems with the Grid. At first it displayed only one of the items (and somehow with the wrong skin etc as well), after trying to alter the grid settings it’s not displaying anything at all anymore.

What I want is to display four random items (right now I got 4 test items created) on my frontpage from a custom post type.

Site is www.songdans.no

Plugins installed and activated:

  • Custom Post Type UI
  • Disqus comments (bundled plugin)
  • Global Blocks for Cornerstone and X Pro
  • Google Analytic (bundled plugin)
  • Loco Translate
  • Modern Events Calendar (bundled plugin)
  • The Grid (bundled plugin)

Hi There,

Thank you for the URL. I am able to check your setup and I can’t see any error on the console. Though when I check the source code, what I found was the height and position of the grid element that is supposed to be added on the fly was not there. I can see you are using brasilia skin, so I made a comparison on what was missing. See this: https://screencast-o-matic.com/watch/cb6QiMIpCz
Most of the CSS that is added on the fly like height, width and position is missing. The html markup is there, there’s just conflict somewhere. Let’s do basic troubleshooting first. You could try testing for a plugin conflict. You can do this by deactivating all third party plugins, and seeing if the problem remains. If it’s fixed, you’ll know a plugin caused the problem, and you can narrow down which one by reactivating them one at a time.

Let us know how it goes!

I deactivated all plugins except the Grid, and it’s still not showing. Interestingly enough it works fine on http://www.songdans.no/songdansar/

Hi There,

What you have here: http://www.songdans.no/songdansar/ is a different grid. Can you try displaying/adding the grid on that songdasar page to your homepage? If that other grid display fine on homepage, we can say that the issue is either on the skin or settings of that specific grid. If the songdasar grid did not show too, means there’s something from homepage content that is conflicting with the grid and we can start digging why is that. Let us know how this goes.

I switched which grid is shown where. It displays weirdly on the frontpage and normally on /songdansar/…

None of my “The Grid” grids are displaying in Cornerstone either. They display fine on the front-end of the site. Just thought I’d add that this looks like a bug.

Hi @tlauen,

Have you tried disabling the cache before testing? I can see that your site is sending cache headers and the browser might be rendering an old copy of your site. Would you mind providing your admin login credentials in a secure note?

Thanks!

Done. Dunno if it’s relevant, but I’m using ThemeCo hosting.

I saved your home page as a template and inserted it in this test page http://www.songdans.no/x-test/ I created. I removed all sections except the grid section and it still didn’t work so we can rule out content conflict. I then compared the page from the page that is working http://www.songdans.no/songdansar/ and found that when using The Grid element, it doesn’t render correctly or render at all using your other grid (framsida) in the front-end but if you insert the grid shortode in WordPress Text editor, the grid works.

I replicated the setup in my test site and this does not happen so we could not yet consider this as a bug.

In a staging server, please try the latest Pro 1.2.3 (use the parent and not the child theme) and The Grid 2.5.0. You’re currently using The Grid 2.4.0. You might need to deactivate The Grid for the update notification to show up.

Thanks.

I tried what you said and made a staging site (http://songdans.no.staging.yourhost.co), changed to the parent theme Pro 1.2.3 and updated the Grid to 2.5.0. Still the same :confused:

Hi there,

It’s currently asking for login (popup authentication), from what apex account your hosting is attached to? I checked your current account and there is none. Or please provide all login credentials in a secure note.

Have you tried deactivating framsida plugin before testing?

Thanks!

It’s on this account. I’ll update the secret note thing.

What do you mean deactivating the framsida plugin? Framsida is the front page, not a plugin?

Hi there,

Ah,I thought it was a plugin from previous reply. Are you sure your domain is already pointed to our hosting? This is the DNS record I can see

NORID Handle...............: SON1532D-NORID
Domain Name................: songdans.no
Domain Holder Handle.......: TBL146P-NORID
Registrar Handle...........: REG42-NORID
Tech-c Handle..............: DH38R-NORID
Name Server Handle.........: NSYO100H-NORID
Name Server Handle.........: NSYO101H-NORID
Name Server Handle.........: NSYO102H-NORID
Name Server Handle.........: NSYO103H-NORID

And attached is the screenshot of what I’m seeing (http://www.songdans.no/ VS http://songdans.no.staging.yourhost.co/)

I’ve been clearing it over and over with no effect, and it doesn’t take effect on a live domain. Or perhaps you’re using external caching and CDN where your domain is pointed?

Thanks!

I changed the name servers to the following when I signed up for your hosting service:
ns1.yourhost.co
ns2.yourhost.co
ns3.yourhost.co
ns4.yourhost.co

The domain is registered at domeneshop.no because I couldn’t register a .no-domain with you guys.

Was I supposed to change something else? I see the staging site now works which is weird. I’m not using any other caching or CDN other than what you guys include in the package.

Glad it’s working now.

It’s not working on the original site…

Hi there,

I can verify where it’s pointed now, and yes, it’s directly pointed to our hosting. I’ll escalate this for further checking as I already tried clearing them. We’ll let you know once we get a response.

Thanks!

Hi there,

Could you try pushing your staging back to live? It works with the staging so maybe pushing it live will overwrite the issue in live domain. But since there is no backup functionality in the staging, please do a manual backup. Like using Blogvault or backup plugin then push it live.

Thanks!

Looks like that fixed it. Hopefully it’s all O.K. now :slight_smile:

Glad to hear that.

Cheers!