Jump to content

creedon

Circle Member
  • Posts

    9,484
  • Joined

  • Last visited

  • Days Won

    79

Everything posted by creedon

  1. The situation has not changed. There is still no SS option to change this behaviour.
  2. No no. Only do it if you want your blog listing page to have two columns. And, of course if you don't want two columns on the blog listing page then don't use the code provided. To have two columns in a blog post you can do that by putting two text blocks side by side. Being new to editing on SS you might find it a bit tricky. SS likes to combine text blocks that are vertically aligned into one. If you find yourself having trouble reaching the above layout, use a text block, line block, text block. Then align your text blocks side by side and remove the line block. The line block keeps the SS combining feature from happening. Let us know how it goes.
  3. The short answer is yes. The long answer. Technically FE is not relevant to the code as an SS Store page section is not FE or Classic editor, i.e. you can not edit a store section like you do FE and CE sections. I classify code that doesn't directly interact with FE sections as... v7.1 Fluid Engine Compatibility : Not Applicable
  4. An iframe element is not a void element. It needs to have a closing tag. <iframe></iframe> Let us know how it goes.
  5. It would probably be best if the feature you need was integrated into the code you have. I suggest contacting the author to see if that is something they are willing to add. I doesn't hurt to ask.
  6. That location is for individual blog posts and is different form where I instructed the code be installed. My code is for altering the blog post listing page from one column to two columns. Is your Layout set to Single Column?
  7. When you say loaded do you mean visible in the viewport of your browser? If yes it is possible to write code that won't activate until the images are in the viewport. I know of no such code to handle your specific issue.
  8. Mostly likely this can't be done with CSS only. CSS has no syntax for targeting words or text ranges. JavsScript might be able to get the job done but I know of such code. Please post the URL for a page on your site where we can see your issue. If your site is not public please set up a site-wide password, if you've not already done so. Post the password here. Adding a site-wide password does not allow anyone to alter your site. It only allows those with the password to see your site. Please read the documentation at the link provided to understand how it works. Please read the documentation at the link provided on how to share a link to your site to understand how it works. A link to the backend of the your site won’t work for us, i.e. a url that contains /config/. We can then take a look at your issue.
  9. You have some CSS that is not wrapped in a style tag. It will look something like the following. .sqs-block-button .sqs-block-button-element--medium {width: 350px !important;} .sqs-block-button .sqs-block-button-element--medium {padding: 10px 25px !i} Also note the code I could see has syntax errors. Look for the CSS displayed at the top of the page in the following locations. Settings > Advanced > Code Injection > HEADER. Blog Settings > Advanced > Page Header Code Injection for the blog page. Please see per-page code injection. Blog Settings > Advanced > Post Blog Item Code Injection for the blog page. Please see per-page code injection. Let us know how it goes.
  10. Have you updated Chrome to the latest?
  11. Have you tried looking at the page in private browsing? What happens? What OS and browser are you using? You also might try rearranging some of the parameters. [data-section-id="638be36f99d1a11c19df1661"] { position : -webkit-sticky; position : sticky; top : 0px; z-index : 9999; }
  12. Looks good to me as well. Viewed on macOS/Chrome.
  13. Add the following to Blog Settings > Advanced > Page Header Code Injection for the blog page. Please see per-page code injection. <style> .blog-single-column .blog-single-column--wrapper { display : grid; gap : 30px; grid-template-columns : 1fr 1fr; } </style> Let us know how it goes.
  14. SS's blog comment feature doesn't have an import/export feature.
  15. Please post the URL for a page on your site where we can see your issue. If your site is not public please set up a site-wide password, if you've not already done so. Post the password here. Adding a site-wide password does not allow anyone to alter your site. It only allows those with the password to see your site. Please read the documentation at the link provided to understand how it works. Please read the documentation at the link provided on how to share a link to your site to understand how it works. A link to the backend of the your site won’t work for us, i.e. a url that contains /config/. We can then take a look at your issue.
  16. Without seeing any of these files I can't say for sure. But my years of experience gives me the sense that they would need to be edited. And to be clear until someone goes through the process no one can say that even editing will work. You have one more potential option. Upload your files to a file server service like Amazon Web Services Simple Storage Service (AWS s3). Then link them into your SS site.
  17. There are many ways you can go but let's assume you want to stay with GoDaddy for the moment. Please see GoDaddy: Activate Gmail for Google Workspace.
  18. I have updated my cited code in my May 10, 2021 post.
  19. My bad. Not sure how I missed it! 🙂 Add the following to Design > Custom CSS. .count-number::after { content : '+'; } Let us know how it goes.
  20. Yes. SS updated how backgrounds are handled and I need to update my code. It may take me several days to update. If you don't hear back from me soon, please feel free to bump this thread.
×
×
  • Create New...

Squarespace Webinars

Free online sessions where you’ll learn the basics and refine your Squarespace skills.

Hire a Designer

Stand out online with the help of an experienced designer or developer.