Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Advanced Search


Circle Member
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by brandon

  1. Yeah, that's right. I've updated my answer to clarify, and to make the distinction between collection id and item id more clear.
  2. Hi @Geekless. This occurs because the "id" attribute, as you have it, is static, and isn't unique to each page. It's that 'id' attribute to which a block field's layout is connected. To remedy this, add some JSON-T value that is appropriately unique. For collections/pages, that's the collection ID. But for posts/items within a collection, it's the item ID (because the collection is the same for all items within it). For example: <squarespace:block-field id="residential-{collection.id}" columns="12"/> Note: One thing you should watch for is what "scope" you are in when ad
  3. Hi @MattSeneca. It's possible by Googling around (using your template name, "squarespace" and "blog thumbnail banner" keywords) that you may find some how-to or code snippet that'll plug in easily. Otherwise, while it's possible to do, the ease with which it can be done depends on the template you're using and other factors. Here's a recent, related post where I mention some execution details/methodology. I hope that helps. -Brandon
  4. Hi Devon. You could instead replace the header image on blog items with the post's thumbnail, if that's the effect you'd prefer. The other alternatives you mentioned are also possible. Thumbnail and meta info is available via each page's JSON data, which can be accessed via JavaScript, added to the page as desired, and styled with just CSS. Such meta may also be available in attributes within the DOM as well. When dealing with thumbnail images, you could either set them via JS using the "background-image" CSS property or by using an <img> element loaded with ImageLoader. I
  5. Hi @scubascuba. In most cases, it makes it easier for others to provide answers and insight if you provide a link to the site/page in question, along with the view-only password (for sites in trial mode, set visibility to "Password Protected"). Someone may have an answer without looking, and it's possible someone may setup their own demo just to help answer the question, but it increases your odds of getting quality answers if you can provide the link.
  6. Hi @equites. When you set document.body.innerHTML to be equal to something else (even something only slightly different) , you're effectively replacing the entire contents of the body element, not just the text you're seeking to replace via the .replace() method. In other words, it's a destructive action, destroying the entire document and replacing it with a (slightly modified, in your case) copy of it. Problem: the elements you're replacing (every single element within the body) may have had event listeners and other functionality "attached" to them. The replacement "copies" are in
  7. Hi @Kassaundra. This can be done by adding CSS via the CSS Editor. .mobile-bar { top: 0 !important; bottom: auto !important; border-bottom: 1px solid #ddd; } #navCloseToggleWrapper { top: 0; } @media screen and (max-width:768px) { .site-container { padding-top: 70px; padding-bottom: 0; } #navCloseToggle { margin-top: 20px; margin-bottom: 0; } #sideTrayWrapper { padding-top: 60px; } } Give that a shot and let us know how it goes.
  8. Hi @KarinaNa. In the case, of Bryant, it should be fairly straightforward. If you're primarily concerned with modern browsers, something simple like this, added via the CSS Editor, should do the trick: #header { position: -webkit-sticky; position: sticky; } If you want broader compatibility with older browsers, and if you don't mind some overlap of your header image, you can instead use: #header { position: fixed; } On a related note, on other templates based on Brine (not yours, but others may end up here looking), the number of concerns when creating a fixed header a
  9. Hi @codeexist. What you're encountering are dynamic IDs generated by YUI, a JavaScript framework that Squarespace uses. As that implies, such IDs will change on each page render. The first time a designer/dev runs into this issue, it definitely tries one's patience. To resolve this, checkout this related answer over on SO, but you can find a whole bunch more posts/pages on this too. Take a look at those and you'll find what to do. In summary: use block IDs instead.
  10. Hey @basakatac. Your site seems like a good candidate for the CSS-only, modern-browser-only approach. // Invert logo color on specific pages. // Uses Squarespace-compatible LESS CSS, not standard CSS. #collection-5d4b424a4895d9000187f302, #collection-5d64262299293800015e0292, #collection-5d4b4ab4d01eac0001327bb7 { .Header-branding-logo { -webkit-filter: invert(100%); filter: invert(1); } } Basically, add a list of comma-separated collection IDs to that first line, and you're good to go. You can add that via the CSS editor, then remove the previous JQuery and correspondi
  11. Hey @alicroft. This can be done. It requires a short bit of JavaScript to look for the "updated-at" div, query the page's JSON data, find the latest updated collection for the page (or series of pages in the index page), format the date to your liking, and then write the HTML to the "updated-at" div accordingly. I'd guess it'd take a good dev. and hour or two to write and test an efficient and resilient script to do that (the first half hour to get the "gist" done, then maybe another hour to mess with time formatting, which takes a bit of time without using 3rd-party libs). So y
  12. One possibly-not-so-helpful option is to search your email instead (assuming you're getting all of the order notification emails). If you happen to be receiving them to a gmail email addresses, you could create a search template for yourself that could be quite fast/efficient at locating orders based on order form content. It doesn't solve the problem within Squarespace, but simply sharing ideas that might get the job done for you.
  13. @AustinRandall: Tuan is correct that it is easiest to provide (and test) solutions if you provide a site/page URL and the view-only password if applicable @basakatac: You might consider asking a new question instead (and providing the info mentioned). You may also find the following helpful, since this question has been asked quite a number of times before. Although the exact CSS used varies based on template, version and your logo, the methods still apply. Methods used include: Using :before and/or :after pseudo elements Using CSS Filters (best if simply inverting black
  14. For what it's worth, I'm not sure that Squarespace restors a "backup" of your configuration so much as it executes a standard set of instructions during the restoration of a template to its original state (while attempting to save as much of your "main content" as possible), in a similar manner as what happens when one switches templates. However, I've not tested this, so I can't speak from experience. Also, it is possible to work with a Circle member to export/import Style Editor settings (with some limitations...if you're switching templates then things might not work out how you'd want
  15. The answer is to add CSS via the CSS Editor in order override your general setting for just that section. It's quite simple, but it does require some understanding of how Squarespace generates the underlying code for index sections such as that. Simply put, in your template, Squarespace creates a "section" element for each index page you create, and gives the section an "id" attribute based on the URL you assign to the page. Taking that all together, we have: section#video .Index-page-content { padding-top: 20px; padding-bottom: 20px; } Insert that via the CSS Editor and adjust to y
  16. Right. What's probably happened is that, because the developer used bit.ly to point at URLs from the CDN, those URLs have probably changed, but the bit.ly redirect is still pointing to the old path. You're going to have to find the asset URLs or upload new images. See "Uploading and Managing Files" and "CSS Files". As an aside, the bit.ly images are added by inserting HTML into the title of that particular index-gallery-item. Once you upload the new image (or locate the old URL), you'll need to update the title of that index gallery item (that is, if Squarespace even allows that anymore...they
  17. Hi @Julita. For starters, the src path for the images in question aren't valid...as in the images don't exist. Do you happen to know why these src attributes are using bit.ly links? Following one of the paths leads here, which is quite strange. I think the most obvious answer, then, is that the images don't exist anymore.
  18. It's almost always best to provide the URL to the site/page in question along with the view-only password if necessary (for sites in trial mode, etc.). However, in this case you may not even have an example page setup. Here's an example in Brine which I whipped up. It uses "card" style image blocks in a single index section/page. Of course, your page ID would be different, and you'd probably want to more specifically target the section. You'll also want to mess with the padding on the text in order to get it where you want. You could do the same thing with regular 'ol image and
  19. Ok - that makes sense. In that case, we don't need to target each block, we'll just target the home page by using the ".homepage" class. That way, image blocks on your other pages won't be affected. .homepage .sqs-block.image-block { margin-right: -18px; margin-left: -18px !important; margin-bottom: -17px !important; } @media screen and (max-width: 640px) { .homepage .sqs-block.image-block:last-child { padding-top: 0 !important; } } Do let me know how that works for you.
  20. Hi @Domanique. You might consider targeting blocks more specifically using each block's block-id. By using the CSS as you have it, it'll apply to every block on the site (or on the page if using page-specific code injection). Are you sure you want to apply that CSS globally to all blocks? Secondly, the horizontal gutter can be closed using a similar approach as you used to close the vertical gutter. However, as I said you'll probably want to target specific blocks for this. Can you provide the view-only password to your site (necessary for others to view sites with password-prot
  21. Hi @fantasiummedia. Here's how I'd approach it. Note that object-fit is focused on fairly modern browsers. .ProductItem-gallery-slides-item-image { object-fit: contain !important; object-position: top; width: 100% !important; height: 100% !important; position: static !important; } .tweak-product-item-gallery-aspect-ratio-11-square .ProductItem-gallery-slides::before { padding-bottom: 0 !important; } .tweak-product-item-gallery-design-slideshow .ProductItem-gallery-slides-item { position: relative !important; } Let me know how that works for you. -
  22. Hi @fabrguer. Nice work on this. I can confirm this is an issue just as you describe. To summarize what I see: Editing a blog post via the "edit" button (a.k.a., via the "dialogue text post editor" ("DTPE")) will result in the stripping of curly-brace-encapsulated-text ("CBET"). Editing a blog post within the context of the website (a.k.a., via the "yui3 text editor") will not strip the CBET. The text will initially be saved and displayed properly on the website upon initial input. However, if the post is edited via the DTPE, the CBET will be stripped upon initialization of t
  23. Hi @HSRA2020. There are various form-specific services out there. One which I am most familiar with is JotForm. You can add a progress bar widget to a standard form. Or, their "card style" forms use that component by default. You can view the various templates at that link (many of which let you accept payment too), but it's pretty easy to make your own form. There are various methods you can then use to embed the form in Squarespace.
  24. Hi @dawsonski. To start with, you can view your template and version number by logging into your site and clicking "Help". Yes, it is. Since you are seeing pages organized as sections within a single page, you are most likely viewing an "index page". These pages are actually a special type of page, whereby "child" pages placed inside of the "index page" become "sections" rather than separate page. To add separate pages (instead of sections), you can add pages to your navigation for those sections outside of the index page. (In theory, you could also drag and drop the index "section" fr
  25. See answer here: https://answers.squarespace.com/questions/284397/getting-varaintid.html
  • Create New...