How To Downgrade Npm Version
Eboni Kleifgen
If you're moving from Squarespace version 7.1 to version 7.0, you will need to create a new trial and build a new site from scratch. It isn't possible to convert an existing 7.1 site into a 7.0 site. The guide Starting over may help.
I'd be interested to know why you'd like to use Squarespace 7.0. Is there a 7.0 feature that you need to use that that isn't available on Squarespace 7.1? Personally, I only recommend starting new sites on 7.0 if a developer needs Developer Mode.
I'm considering to downgrade as well. I'm interested in the Wells template with the main menu on the left side. In 7.1 there is no easy way to change the heading to the left side of the screen. I don't have time or knowledge enough to arrange this via css and I don't have the resources to hire someone to do it for me.
Just started a trial and am shocked there's no way to change templates.
Mentioned in the site building process: "You can always explore other templates if you change your mind later." What's that about?
I've used Wix in the past & will go back.
The reason people want editable templates is... for the templates. They provide not just simplicity but design inspiration.
SS was supposedly all about "the best looking templates"... with 7.1 that kinda seems like a phony sales pitch. There might be more edit functionality so you can match any template - that's useless when there's no easy way to even see these great templates. It doesn't make sense and works against their own sales narrative.
There's a reason SS have only 2% of Wix's market share after 20 years. Not understanding the market & arguably their own product or users.
I already paid for an annual personal upgrade, trying to get access to other templates, and to learn how to disable the header lines I don't want (All Prints, About). I can't get rid of them, and they link to the demo.
Hi, I have been unhappy with 7.1 as well, I don't have nearly the flexibility that they think they are giving us. Why do I need a PLUG IN for anything in Squarespace, especially as simple as a left verticle menu. The learning curve has made me give up and to have to rebuild and redirect is even worse. Squarespace, you used to be fun and easy!
Is there a way to downgrade the version of Dropbox on the computer. I'm on a Mac (OS v. 12.6) and I just updated to the newest version today (10/25/22), and the dropbox folder has disappeared from my desktop and is only available on cloud storage. You have to go to the finder sidebar to get to your files (an extra step). Would like to find a way to return to the previous version. Any suggestions?
There was an update today (10/25/22) and after I did so, the dropbox folder on my desktop has been moved to a "secure" location, but I can't find it on my hard drive. I'm using a MacBook Pro and MacOS 12.6. NEVERMIND.
- Changing the location of your Dropbox folder is no longer supported by macOS.
- Due to the change of the Dropbox folder location, files that were previously linked in some third-party applications may need to be linked again.
- Storing your Dropbox folder on an external drive is no longer supported by macOS.
- Your Dropbox folder in Finder will now be found under Locations and no longer under Favorites.
- Individual folders can be moved from your Dropbox folder to Favorites for quick access.
Did this post help you? If so, give it a Like below to let us know.
Need help with something else? Ask me a question!
Find Tips & Tricks Discover more ways to use Dropbox here!
Interested in Community Groups? Click here to join!
I prefer the older version of Dropbox where we can move files seamlessly as if it is a local folder and auto sync to cloud storage. I am not happy dropbox takes away this feature. What is the point of using Dropbox anymore ?
I too prefer the older approach to storing files in Dropbox. This change makes Dropbox practically unusable for me in MacOS. I rely upon the fact that Dropbox replicates my files across all of my devices. If I ever lose access to Dropbox for any reason (perhaps Dropbox servers are hacked or undergo a massive DoS attack), I still have my files on my devices. I rely on the fact that I can open a text file in my favorite text editor, edit it, save it, and have it replicated across all of my devices.
Hi! I just upgraded mine and I had the same issue. I'm feeling so bad about hitting that upgrade button in the first place now.
Also, my dropbox folder won't even start syncing again as well. It just keeps saying "Indexing XX,XXX files" and the number just stays the same.
I think we're screwed.
When deploying the newest Electric Utility Network Enterprise v1 asset package it appears that it was created in Pro 2.7 which puts it at V5 and only compatible with Enterprise 10.9. I have Enterprise 10.8.1 and running Pro 2.6 so my utility networks are in V4 for the 10.8.1 Enterprise compatibility.
Is there a way to downgrade or drop the asset package to V4 that Pro 2.6 can recognize to be able to apply to the Enterprise 10.8.1 server environment? If not that any user not on Enterprise 10.9 can not utilize the Electric Utility Network Enterprise package and are forced to use the Electric Network Foundation packages which have already been moved to mature support.
In Electrical I had to delete Object ID 15, 16, and 17. Once I did this the tool ran just fine and downgraded the EnterpriseV1 to a utility network v4 to be able to work on Pro 2.6 and Enterprise 10.8.1
Lindsey, we are in the same boat as well with another project but with Water and Sewer. While we were planning for a water deployment a new sewer solution was released with Pro 2.7 which will only work with 10.9. We are thinking we may just build a UN from scratch with Pro 2.6 to put it at V4. We will then copy the guts out of the new data model and move forward from there. A lot of the dependencies seem to lie with the attribute rules which we've started deleting anyway from the asset package as they can slow down load times and usability times drastically. We then add in what we need depending on the need. If you can get this figured out please let me know. We've tried every approach less the total build out of a UN from scratch. I hope it doesn't come to that...
We have a shared internal dev environment and one dev was working on a feature branch with updated episerver nugets and when they ran their project locally and connected to the shared episerver database, it updated the database version from 7059 to 7060 (unfortunately the setting to automatically do these updates was turned on). Now we cannot run the project on that database version without updating the nugets sufficiently. An update to episerver is not going to be deployed soon to this project so we're left with trying to figure out how to solve this mess.
I'm afraid, to the best of my knowledge, there's no downgrade option so your best bet would be to roll back the database (if possible). You mentioned there's no recent backups but, depending on how your database is configured, you may still be able to roll back to a point in time. Rolling back an azure SQL database to a point in time should be pretty straightforward if you're using that. If you're using SQL server, it's not quite as straightforward but should still be possible (depending on your database recovery model). As I recall, the process involves a tail-log backup (which contains the transactions since the last backup), allowing the transactions to be replayed up to a point just before the database version was updated. I can't remember the exact process but I'm sure Google would be able to help.
I'd strongly advise against the suggestion of manually changing the database version in `sp_DatabaseVersion`. That may remove the initialisation error but basically all you're doing is masking the cause of that error. The database schema will still not match the codebase and so you'll most likely end up with many more, much harder to find errors cropping up throughout your solution. It may also cause you problems when you subsequently try to upgrade as the schema won't match the expected schema from in the database upgrade scripts.
Thank you for the helpful comments. I will have a look at using SQL Server transaction logs to bring an older backup up to speed, and at the very least configure a maintenance plan for frequent backups for the SQL server. It'd also probably be a good idea to have automatic database updates off for Episerver in the shared developer environment, like Tomas points out at the end of his blog.
My client has been pushing for the application to be updated since they are paying for the support and all from Sage. I called Sage and the procedure given was to upgrade to 15.1 and then to 17.1. I have been backing up the folder where the data files were installed but just that - thought that was enough.
I proceeded with the upgrade today by upgrading the application on the server (DC) to 15.1. Ran the data upgrade which went smoothly. Next, i did a File doctor scan and fixed one file, nothing major. Tested application and all seemed fine. I proceeded to upgrade to 17.1. rev6 went through the data file upgrade again and this time some of them failed. Complained of "unprintable control characters found". It appears some of the fields had characters which are no longer permitted (my guess), so I went along with the File Doctor fix which did work. After that I ran the data file upgrade again and this time it completed for the files that had failed previously. Tested the application, seemed fine.
c80f0f1006