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 adding the block field within the .list code. In the example above, I've used {collection.id}. But, if in the context of your .list file, you are already within the {.section collection}...{.end} scope, you would only use {id} instead of {collection.id} in the example above. Including said values in the block-field id gives the block-field its "uniqueness" on a per-page/post level. What's the difference between collection id and item id? The collection id is unique to each collection. The item id is unique to each item within a collection (each blog post, or image, etc.). It's a matter of context as to which you want to use. In your case, because you're editing a .list file and you want to create multiple galleries where each list page has a set of block-fields unique to it, you'll use the collection id. Collections don't have an item id, so item id wouldn't work. If you wanted to have a block-field that was unique to each item in a gallery, you'd edit the .item file and use the item ID (because every item in a single collection would share the same collection id). Do let me know how that works for you. -Brandon
  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'd probably go with the former for simplicity (though it may load a larger image, the difference is probably negligible). I'd estimate an experienced dev could do any of those for you in less than a couple hours.
  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 indeed copies, but are also entirely different entities from the original ones. They don't have those actions "attached" like the original elements did. Therefore, any element that has had functionality added to it before your code runs will quit working, because the element is replaced with a copy that does not have that functionality. For elements that have their functionality added after your code runs, they will work initially, but will then fail to work if your code runs again (if repeating the translation to yet another language.) The Add to Cart button is an example. I'd be surprised if there aren't many others. This can be referred to as a "race condition" and such conditions often cause a lot of confusing behavior. Solution: You'll need to take a different approach: identify and target the elements on the page that should have their text replaced. When targeting, ensure you're targeting the inner-most element that contains the text node. While not always necessary, that will ensure you don't destroy existing functionality within the DOM. For each element, replace its innerHTML/text-node, each on an individual basis. This will keep the elements intact, affecting only the text within.
  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 are much greater and include: differences between index and non-index pages, what headers (top/bottom) are enabled, whether the screen is resized, whether the announcement bar is used (and whether it's been closed), whether the header covers up content when anchor links are used, whether you want it fixed on mobile, whether you have the headers set to overlap on index pages, and more. To account for that complexity, I created Fixit - Fixed Headers for Squarespace. In my experience, many tutorials and code snippets fail to take one or more of those into account. In your case, the above should work. But I say all that in part so that, if you find anomalies in certain contexts (the announcement bar visibility being one of them), they are probably solvable. Just post back and include a link to your site and the view-only password for trial sites. Finally, custom CSS will be applied even for trial sites. Hope that helps. -Brandon
  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 corresponding logo file you were using; you don't need 'em. Related Questions Q: How do I find my collection IDs? A: Use your browsers developer-tools/inspector. It's the ID attribute on the `<body>' element. Q: Do I need to add it to just certain pages? A: No, that's what the collection IDs in the first line are for. They ensure the rule only applies to the pages you add. That way, you can add it globally via the CSS Editor. Related Posts Related post, for 7.1 is here.
  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 yes, it's possible. Having taken a quick look, I think it could be done without you having to refactor your code at all. You could leave it as you have it on the pages you want it to appear, and the code could be set to run on those pages. If you want more info or help, say the word.
  12. brandon


    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 to white or vice versa, but will work for some color logos) Using Javascript to change src attribute In general, if using the CSS Filters approach (#2), you can target the logo in 7.1 like so (using your own collection-ID as applicable). By including the collection ID in the CSS, you no longer have to worry about only adding the CSS to specific pages, because the rule itself specifies which pages to apply to. #collection-5d9e907ec1f67f503cab5fc8 .header-title-logo img { /* For black/white */ -webkit-filter: invert(100%); filter: invert(1); /* Or for converting color to white, something like this (depends on logo) */ // filter: grayscale(100%) brightness(350%); } Where to I insert this code? You add it via the CSS Editor How do I find my collection ID? You can identify the collection ID by using your browsers developer tools/inspector and viewing the ID of the <body> element. The other methods listed above (#1 and #3) are also viable. Related Links: https://forum.squarespace.com/topic/82174-tremont-template-how-can-i-keep-a-white-logo-in-the-homepage-and-a-black-logo-everywhere-else/ https://forum.squarespace.com/topic/3424-different-logo-for-mobile-nav-bar/#comment-19904 https://forum.squarespace.com/topic/2566-change-logo-for-specific-page/#comment-14932 https://forum.squarespace.com/topic/61248-changing-logo-colour-on-homepage-vs-other-pages-marta-theme/#comment-263327 https://forum.squarespace.com/topic/22800-forte-changing-black-logo-to-white-logo/#comment-211315 https://forum.squarespace.com/topic/5214-change-image-colour-on-hover-for-one-imagepage-only/#comment-29997 And many others
  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 them to). Again, that perhaps doesn't help you much (especially not retroactively) but might be valuable for you to know later, if it becomes necessary. Currently, Squarespace "...isn't optimized for importing content between Squarespace 7 sites..." (reference). And for 7.1 sites, it's not possible. Some have had some success using the Wordpress export feature (see here and here). So, it seems none of these are a great nor comprehensive solution to the issues you describe. However, it is an answer to your question: "does anyone know how to back up all of this, export it, or something", so I thought it was worth posting.
  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 your liking. Note that you have a couple spacer blocks at the top of that section that you'll want to remove if you really want to close that gap. In the future, if you want to look into how this code is generated, get comfortable using your browsers developer tools and poking around with the inspector. Do let me know how this works for you.
  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 may now escape HTML that is inserted in such areas). In the end, I would not have personally done it this way, but would instead favor using CSS background images, which you might consider.
  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 text blocks and would probably have a bit more flexibility, but I figured this was good enough to serve as a proof of concept for you so as to answer your question, "yes". #page-5d9e40adc1c17f087e491930 { background: ~"linear-gradient(#BBB, #BBB) no-repeat center/1px 100%"; /*https://stackoverflow.com/a/53551089/5338581*/ } .design-layout-card .intrinsic { padding-top: 50px; padding-bottom: 50px; } .design-layout-card.image-position-right .intrinsic { padding-right: 6%; margin-left: -6%; background: linear-gradient(90deg, rgba(0,0,0,0) 40%, #FFC0CB 40%); } .design-layout-card.image-position-left .intrinsic { padding-left: 6%; margin-right: -6%; background: linear-gradient(270deg, rgba(0,0,0,0) 40%, #FFBB22 40%); } .sqs-block-image .design-layout-card .image-card-wrapper { background-color: transparent; } Do let me know how this works for you.
  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-protected visibility, such as sites in trial mode)? That will make it much easier to provide and test block-specific CSS.
  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. --------------------- UPDATE 4/8/2020 (and 6/24/2020) In some cases, you may prefer to use this instead: .ProductItem-gallery-slides-item-image { object-fit: contain !important; object-position: middle; width: 100% !important; height: 100% !important; position: static !important; background-color: #EEE; }
  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 the block within the editor. CBET will be stripped in text blocks whether the "code" format is used or not. CBET will also be stripped in markdown blocks and code blocks (!) Using HTML entity codes doesn't seem to help (`&#123;` and `&#125;`) CBET will be preserved (not stripped) if the CBET contains a space that has a non-space character on both sides of it (not including the braces themselves) All of the above bullets are applicable to any `text`-based collection item edited via the DTPE, but does not occur in the body of image-based collection items nor event-based collection items. I personally have found no way to escape this behavior. I would report this to Squarespace. You could provide a link to this post for more information.
  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" from inside the index page to outside it, thereby making the page it's own page. But if this is a live website, better to leave the existing site intact and create new content. Then, once you have everything ready to go, enable your new home page and navigation and disable the old index page.) No, since you should be able to add pages as needed using the template you have now. In fact, if you did want to explore other templates, you can switch and preview templates without replicating the site separately. Just be sure to read up on that link, especially if this is a live website, so that you're not surprised by reorganized content or changed styles. Many templates in Squarespace are part of a "template family". In this particular case, the template 55f0aac0e4b0f0a5b7e0b22e represents the "Brine Family" of templates (also/formerly referred to as the "Wright Family"). Templates within a family generally share the same features and style options, though they are configured differently from the start (thereby distinguishing templates from each other even when in the same "family". At this time, the Brine/Wright family of templates are generally considered the flagship/best template in many cases.
  25. See answer here: https://answers.squarespace.com/questions/284397/getting-varaintid.html
  • Create New...