nathan

@bp27, I think you're on to it. I didn't realize it until you mentioned that, but the spreadsheet I was copying the text from did have a slightly off-black color. Deleting the text and pasting as plain text fixed the problem for that product. I'll use @tuanphan's recommendation as a quick fix, but will fix the description for each product in this way. I will also submit this as a bug to Squarespace. It may be helpful if you do as well.

Thanks @tuanphan, but the description text in product editor does not have a color option. And the site styles for this page is set to white. In fact, changing the color of product detail on the site style has no effect. I had tried changing .pdp-details-excerpt and it didn't work, but adding the !important with the asterisk did work! Thank you.

I'm having a similar issue where product description appears blue even though product description is set to white in the Site Styles. I tried the CSS snippet recommended above without success. See: https://wscdev.squarespace.com/tom-hyde-photography/p/mother-giraffe-calf

I've just now realized that I don't even have to edit the Markdown block. Just tapping on the block brings up the overlay with tabs for Preview and Markdown. On the first tap, it already adds the backslashes. If I then tap on the Markdown tab, it adds another pair of slashes. If I switch back and forth, it will remain as is. But, if I tap out of the Markdown block and then come back to it, the pattern repeats. In my test, I just ended up with each instance of Markdown syntax being surrounded by about 10 backslashes.

Site URL: https://nathancashion.com/blog/2018/5/the-4-causes-of-low-back-pain I've had an issue occur a few times now. If I edit a Markdown block while using the Squarespace app for iOS, the markdown gets changed. It appears that the block will add in backslashes before any markdown formatting syntax, e.g. ### Disc Likely the most common cause of back pain in our modern age, *degenerative disc disease* or *discogenic low back pain* is attributed to 40 percent of low back pain cases. will be converted to: ### Disc Likely the most common source of back pain in our modern age, \\\*degenerative disc disease\\\* or \\\*discogenic low back pain\\\* is attributed to 40 percent of low back pain cases. These added characters then show in the rendered page, and all paragraph breaks are removed. (See attached screenshot. I've fixed the live blog post, so you can see the correct formatting by visiting the link above.) If I try to fix it by editing on iOS, it only makes it worse. In fact, it will add backslashes to the backslashes. I can only correct the problem by editing on the web, completely replacing the text in the Markdown block.

Answering myself… Turns out I was using keys for reCAPTCHA v3, which are not supported by Squarespace. (Explained in Troubleshooting section here: https://support.squarespace.com/hc/en-us/articles/115013193528#toc-troubleshooting). Created v2 keys in my reCAPTCHA console and it is working now.

Answering myself… Turns out I was using keys for reCAPTCHA v3, which are not supported by Squarespace. (Explained in Troubleshooting section here: https://support.squarespace.com/hc/en-us/articles/115013193528#toc-troubleshooting). Created v2 keys in my reCAPTCHA console and it is working now.

Hi, @organic_emma, Has there been any solution to this problem? I've been having the same issue.

@ChristianKasperany resolution to this? I'm having a similar problem. Setting up the form works fine, but when I visit from any of the domains added to my reCAPTCHA dashboard, I get ERROR for site owner: Invalid key type. Hopefully you've found a fix?

Is there a particular reason why the guide recommends using setting the section ID in a <p> or <a> tag? That's how I was originally creating anchor links, but I noticed very inconsistent results with actually jumping to the target. Sometimes it wouldn't go anywhere despite triple checking the ID and spelling. Other times, it would jump well past the anchor target. I now use the ID in a <div> tag and have had much more reliable results, with the anchor link landing on the target section everytime.

Thank you! I've had the same exact problem for a couple of years and just haven't put in the time to find a solution. You'd think that this could be configured in the Font Style editor, but I appreciate the code snippet which worked well.

I use GeoTargetly to adjust site behavior (e.g. show location specific content) based on geolocation. I'm not sure how it would work in your situation, but there should be a solution.

I need to do something similar. I'm using a blog collection to store bios of members of our team which I categorize based on department, committee, etc. Then I add a summary block on each department's page and filter based on that category. But having them sort by reverse chronological date doesn't work for me. It would be great to find a work around for this.

Site URL: https://wscdev.squarespace.com I'm moving a site from Wordpress with nearly 100 pages. I'd like to have these organized in the Not Linked section in a way that has some semblance of sanity. Wordpress had parent-pages which lent a nice structure. SQSP 7 and prior had index pages, but those don't appear to be available anymore. The best option, I suppose, is Folders. The key problem I have with this is that the Folder itself takes a URL slug. So, for instance, if I want to collect our pages about Research under a folder, the folder would be /research but if I wanted to quickly direct people to an overview page about research, it couldn't be /research. Do I just name the folder something more arbitrary? Say, /research-folder, since it isn't actually visited by anyone? And if I want all pages within the folder to have a clear URL, do I manually name each page URL slug, e.g. /research/new-page? The other option I've seen is using a blank Link item to create a pseudostructure to the Not Linked section, as seen here.

I get what you mean. I use similar sections across my site, and don't want to add the individual elements or same content on each page. The only way I've found to do it so far is to duplicate the entire page and change the content that needs to be different. I'd love to hear if anyone else has found a better solution.

Hi Impega, I do this all the time. Yes, the audio file will be replaced in the RSS feed and shouldn't cause any problems. The order of the episodes is based on publication date of the blog post and the podcasting metadata that you add to the audio block. It may take some time for the new audio file to propagate to all endpoints (e.g. Apple Podcasts, vs. Spotify vs. Stitcher, etc.), and if a listener has already downloaded the old file, it will not replace that unless they opt to download again (but there is no notification on the user's end that the audio file has changed). Hope that helps!

Site URL: https://www.nathancashion.com/bigfoot I'm using Bigfoot.js to create inline footnotes that pop-up instead of link to the bottom of the page. It's working great, the only problem is that the version of Markdown on Squarespace doesn't support the syntax for footnotes. The syntax is relatively simple and similar to links: To create a footnote reference, add a caret and an identifier inside brackets ([^1]). My current workflow is to write the post in Markdown using iA Writer. I then copy the document (or, at least, the section of the document with the footnote) as HTML and paste that into a code block on SquareSpace. This obviously isn't ideal or efficient – if I want to add an image to the post on Squarespace, for instance, I have to separate the code blocks since image blocks cannot be inserted inside a code block and the code block will not simply split at a line break like a text or Markdown block will. Is there any solution to enabling the footnote syntax within SquareSpace?