Picture slider not showing on Community page
See original GitHub issueDescription
The slider is not visible currently.Expected Behavior
Restore the Slider on layer5.io/community
Environment:
- Host OS:
- Browser:
Contributor Resources and Handbook
The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the master
branch.
- 📚 See contributing instructions
- 🎨 Wireframes and designs for Layer5 site in Figma.
- 🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack
Issue Analytics
- State:
- Created a year ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Slider images are not showing in the page
Solved: Hi, We have created image gallery in our template but it's not showing in the pages made from that template. The thing...
Read more >images not showing in slider - WordPress.org
This is a dev page but has the same problem, the first image on the slider loads fine but the second and third...
Read more >Images not showing in slider - JavaScript - SitePoint Forums
Hi,. Am practicing my CSS and jQuery and have done a demo site here. The jQuery appears to be working behind the scenes,...
Read more >Images not displaying in Featured slider - Shopify Community
Solved: Images are not being displayed in the Featured Collection Slider. Theme - Debut Currently in Draft Preview Link ...
Read more >Slider Not Showing on Mobile Devices | Themeco Community
I am using an HTML5 Video. It simply shows the cover image and a small blurred circle in the middle of the frame....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It is due to upgrade, I will be taking a look at it.
Fixed in #3026