melody495

Hi @MagnusHenry Currently it seems like you are using the portfolio home page as your Work and Home page. You would like to have the ability to display different groups from your work portfolio on the same page, is that correct? You can make use of Summary Block. This allows you to pull in from any collection pages including blog and portfolio, and display the content. A Summary Block can be customised with a filter by category, how many to display etc. You can have one Summary Block for each groups of work. You would create a new page, and add Summary Blocks. This gives you more flexibility in designing the page. But first you would need to organise your portfolio. You can either add category labels or split your work into different portfolio collections. A portfolio can have up to 60 sub-pages, this could be a consideration.

Hi @mdemartin this plugin is by SquareWebsites, you need to contact their support. It is via their Slack channel, but see here for details and the link https://www.squarewebsites.org/contact There is no built-in way within Squarespace to view more than 30 items in a Summary Block. You would need to code something up or use a plugin such as the one you have.

@Squaredspace Oh Edge, interesting. Glad you found the issue! Squarespace does support Edge (if you wish, you can submit a ticket to Squarespace Support), but more people use Chrome compared to Edge, so it tends to have fewer issues.

You are welcome 🙂 If you want to be more specific, you can target the block id. There is a very useful browser extension called Squarespace ID Finder.

Hi @Oukside I like what you've done with them! You can try extending the button block to align with the bottom of the text block, so that the bottom of both blocks are on the same row. So that when they reach the bottom of the section, they are moved up together at the same height. Hope this makes sense. If not already, change the button to "fit" under Design. Let me know how it goes.

Hi @DTACASA possibly because your menu text colour is the same colour as the background, therefore not visible to the eye. But please share your website URL so we can have a look.

Hi, you can pick the best matching options to get through, then it should give you options to get in touch with support.

Great! You're welcome 🙂

Hi @AgnesK the block refers to the whole summary block including the left and right arrows. You can use this to target just the items in the summary block. div#block-927ca40df0644d9749a7 .summary-item-list { pointer-events: none; } Let me know how it goes.

See if this article by Squarespace is helpful About the Google Domains migration to Squarespace

Add me as a Contributor with Admin access to your website, so I can see what's going on. My email is in my signature below.

Hi @dewilson that sounds quite impossible! But if that is indeed what's happening then that is a platform issue, I suggest you reach out to Squarespace Support.

Hi @Waggit can't tell without a url, but if you're still seeing the desktop image, then this line (display: none) isn't being used. Likely the CSS selector has changed. Check that this element still exists in your site .section-background-content. Depending on the version/your site, it could be .section-background img.

Which buttons are not working? Not every button is a .sqs-block-button-element, you seem to have defined your own class sometimes. Your code above would only work on Squarespace buttons.

Hi, you shouldn't remove the display: none, as that is what should be hiding the form fields on post submit. Anyway the display: none is a Squarespace CSS, you can't remove it. Is it something else you removed? It is difficult to diagnose from the outside. But from what can see from the outside, the display: flex is overriding the Squarespace's display: none. That might be a symptom rather than the cause, can't say for sure without looking further.

The display: flex is overriding the display: none which should hide the form on post submit. The form on my test site handles the post submit differently to yours, therefore is not affected by the side-by-side code. I'm not sure why though without looking into it further. Is it a form block issue? The way the form is set up? Other custom code? Hmm is there a new beta version of form block that you are using?

I have tested the code you've linked in the blog post above, and I cannot reproduce the issue you are seeing. Do you have other code modifying the form? Just for a sanity check... what is in your post submit? in the settings.

Hi @mrs_kate_dyson, can you share the url of the page on which you are seeing the issue?

Sorry to hear that. Worth contacting Squarespace Support to see if it is an issue with the platform.

@MaryLou You are very welcome, glad it's all working! Haha, don't worry, you are not alone in this, we all make mistakes like this 😄 Thank you.

Hi @Pally Ziggy means to check your site in safe mode. This will let you know if the issue is due to a script or not. You can see how to do that in this video here by sam However, if you think the issue is from a specific piece of code, then you should test to confirm first. If you don't want to disrupt your live website, you can duplicate the page without the code, and see if that form behaves the same way. Otherwise it is difficult to find a solution if the cause hasn't been identified yet. Let us know how it goes!

You've typed in the word "PACKAGE" in all caps 🙂 You mentioned this is a template, let me know if you cannot alter the input to "Package", and we can see what CSS you need. Edit: just to add, the text-transform is already "none" currently. The all caps you are seeing is due to the text being typed in all caps.

@Backmarker91 the only thing I would suggest that you haven't mentioned is clearing your browser cache

Hi @MaryLou what is the CSS that you tried to make your h3 lowercase? If you share it, we can see what the issue is. Edit: your password is incorrect

You could wait for Google to crawl your site and see the new changes (it could take weeks!), or you could request Google to crawl the pages you have made changes to. This might be quicker, but it's up to Google. You can do this via URL inspection -> Request Indexing. Good luck!