Squarespace Problems

Touch the symbol to immediately ship it. Include your thoughts about each tweet with an answer. Identify a subject you are enthusiastic about and step right in. Immediately get an overview of what folks are discussing now. Keep following other email addresses to get immediate update on issues that matter to you. View the latest talks on any subject now.

Get instant information about the best tales that happen during their creation.

Update it.

You are not alone if you seem to have problems technically processing your Squarespace website. Although it may seem a little disappointing, there are a few things you can do to see if you can solve the or not. You' ll not only find that out, but hopefully you' ll also find out a little more about web applications (what Squarespace is) and what happens under the bonnet.

Usually the first type of problems is a small problem: you have made a modification and stored it, but it does not appear. Normally this can be fixed by clicking on the update icon of your web browsers (make sure you save everything first!). Browsers like Squarespace are not like programs that you download and run on your computer, even if it often seems so.

Thus, they execute codescripts at your end of things in your web browsers, and they return the changes you make to the server that stores your website data to it. The changes are adopted at this time and the new modified release overrides the old release.

As you can see, you are not really modifying the actual data in your web browsers; you are generating a sequence of commands for the modification that needs to be made on the servers. Pressing Update instructs the web browsers to go to the web site and retrieve an up-to-date copy of the changes made.

On Squarespace, this happens most often when you are editing an picture in the photo editor or moving pages in the Pages submenu, but it can also occur at other time. Damn, with Pixlr you have almost a reduced copy of Photoshop, free of charge, with all the complex extras and picture manipulation that take place on-line, right there in your favorite web browsers (tip: If you haven't tried Pixlr, you really should!).

Square Space is no different from this new type of in-browser manipulation, and many of the things you do when you build pages and produce or perform unusual pull -and-drop wizards are actually quite resource-intensive. There is a great deal going on in your web browsers, so you will sometimes experience problems with your system after a long processing period.

Why do you have these problems? Your common offender is your web browsing history. To speed up the loading of Web sites with limited resources, Web browsing apps save (or cache) Web pages you have visited so that the next times you view this page, they download the saved page from your Web browsing memory, rather than having to get a completely new copy.

Normally, the web browsers only use buffered editions if the web page or data has not been refreshed since your last use. When it changes, the web browsers recognizes this and ejects the old release of the repository and gets the new release to display and store in the repository. Remember, every times you size an existing picture in your Squarespace editors, you see the changes in real time--and you can see the changes in real-life.

However, what happens behind the curtains are hundred of computations that re-draw the location and dimensions of this picture on the monitor for each stage of the journey. It' a little like a little more of a digitally enhanced form of an animated notebook (that's a true over-simplification!). It tends to be that the web browsers are a little baffled about what's new and what's buffered, and they don't know what to do.

The best way to eliminate this browsing mess is to clear your browser's memory and reboot your webbrowser. Emptying the memory space is the same as emptying the web page. Here is how to empty the web browsers in Firefox, Chrome, Safari, Microsoft Edge and - God forbid you use it - IE (please stop using this browser).

The majority of my customers and I have found that deleting the browsers memory will solve the following kinds of problems: Emptying the repository will solve a variety of problems - and can often improve the performance of your web browsers on all sites - so it's a good thing to empty the repository on a regular basis, even if you haven't made extensive changes to Squarespace.

The last tip I have is to say that not all webservers are the same, and when it comes to realizing advanced features in web applications like Squarespace, Firefox is in my opinion the best webserver to use. Guess it's due to the fact that Firefox handles both Javascript and unusual HTML quickly and to a very high level (geek out about the full testing and results here).

However, this is just a weird way of saying that it is better equipped to cope with the sophisticated handling that web applications like Squarespace need. When you' re fed up with crashing, click Update and empty your memory a bit, try Firefox (it's free). For my part, I've found that it surpasses all other browser I've tried while working in Squarespace, making the whole edit a much more enjoyable and much less frustrating one.

You' ll need to update and clear your memory, but less often. Firefox is also an open plattform, so you don't have to share your information or undress the business bags of big boys like Google, Apple and Microsoft. Or write me a line if you want the help of a Squarespace queen (that's me!).