I have just started working on sitefinity and was replacing some documents. However I replaced the wrong document and published it.
I went into the version history for the document but when I click on the older version I cannot even open up the older file. The button is there but I cannot click on it.
I also tried reverting to an older version and then publishing but this also did not work.
There is no real code to paste so I would just like to know whether it is a bug with Sitefinity or whether it is even possible to go back to an older version of a replaced document.
Thanks in advance.
If you replace the file - then it really replaces it and there is no way of reverting it back from the revision history.
Hopefully you have a backup of the DB (or the blob storage) and you might be able to restore it.
Related
Unity forced me to switch from Collaborate to PlasticSCM. I used Collaborate to upload builds of my game to the cloud, so that I could expirement with new features and stuff that I could easily roll back if they didn't work. This has become very useful for me as my project increases in complexity, because often I'm adding methods or 1-2 lines or code in 5-6 different scripts with hundreds of lines, and if I don't like the way something's turning out after an hour of work for example I could've just, back when collab was a thing, upload the changes and then revert back to the previous version. Say I liked a few things I did when I added said expirmental feature, I could always upload the new version of me adding the feature, go back to the old version, copy for example a few lines of code, and go back to the new version. It was really handy.
If you look at attatched images, PlasticSCM does something similar with their "Changs ets", and I'm looking for a way to tell it to revert my project back to a previous one.
If you still don't get what I'm saying, let's say I added in a folder with 3 textures. Then, upload the changes. Next, I alter the texture. I don't like how I've altered it. The button I'm looking for in PlasticSCM would revert my project to the previous version with the unaltered texture.
Thank you all!
From snapshoot view you can right click and select "Switch workspace to this changeset"
You might need to update to the lates version of the "Version Control" plugin.
I have created a total of 9 sample pages for my project. I tagged three of them as templates to speed the design process. I successfully exported all nine files but upon returning to my account discovered that all nine files had some how revered to the same source code.
In other words, instead of 9 distinctly different pages I have 9 copies of the same page. How could this happen and how can I fix this? I need to continue my work but with no way to correct this problem or upload my correct files form my previous export I feel as if I need to either start over or do all of my editing in an HTML editor manually going forward.
Any guidance would be much appreciated!
Do backup next time. I don't think you would be able to retrieve your "OLD files" if you didn't back them up and without UPLOADING your previous files.
Please get in touch with support if you lost any data and we'll work with you to get it restored right away. Bugs like these are always high priority and we want to make sure your data is never lost.
In the new version of Divshot saving is now manual and with version history you now have the option to revert back to a previous version of a file at any time. All data is backed up on Amazon S3 with versioning.
After upgrading let me know if you continue to experience issues with cloning pages or using templates. We'll be happy to help!
I have a problem!
We are working on an iPhone-app and are using git. The problem is that if someone changes something in the project(adds a file and so on..) and i try to pull that change, I have to merge it.
But the merge isn't painless, I often end up getting a corrupt project file and have to spend quite some time just to fix that.
Does anybody have a solution for this problem?
(Sorry for my crappy English)
Project files are notorious for conflicting. I would enable rerere (stands for "Reuse Recorded Resolution") so that if you have to redo conflict resolutions, you can at least have your decisions cached from the previous time you did them. An excellent write up on rerere is located here: http://progit.org/2010/03/08/rerere.html
If you have the inclination, the better thing to look at is an advanced topic of writing a custom merge driver. See "Defining a custom merge driver" in http://git-scm.com/docs/gitattributes
Hope this helps.
Three important steps:
Cause git to ignore everything in the project file except for the project.pbxproj under the .xcodeproj folder - use .gitignore for this.
before you pull a changed .pbxproj close your project. One of the biggest problems you face is that if you get a new version while Xcode has the project file open it can just save its "current" version over the changed one you want.
merges will sometimes result in spurious data like ">>>>YOURS" or ">>>>THEIRS" merge markers getting included in the project file. If you have to merge do it manually with a tool like filemerge where you can inspect each change and choose whether to include it or not.
If all this fails and you get a corrupted project file anyway
accept the version someone else submitted and redo your own changes, it's almost always easier and the link errors will remind you soon enough.
learn the value of frequent commits.
My iPhone application uses Core Data and a SQLite database; versions are being tracked using SVN. Adding data to the database is not reflected in the application. I make sure I delete the project out of the simulator and that the new database is added as a file to the project. I suspect the data is being cached in another location.
Please note, SVN shows no changes to the database, even when directly edited. Also, if I copy and paste the project to a new folder, delete the hidden svn folders, delete the build folders, edit the DB, delete the project out of the simulator, then compile and run, it works the first time. After that, the data again is cached in some unknown location.
Any ideas where this could be?
UPDATE:
The solution to this was to exit my SVN Client (Versions). I am still unsure of how this affected updates to the DB; I wouldn't think it would block or revert any changes. I am now able to edit and save changes.
Thanks everyone for the help.
Could be more than a couple of things going wrong here. If you have the SQLite DB added to your project by reference, and if you haven't made any code changes, then when you click "Build" you won't see your changed DB resource copied over. Basically, Xcode has long-standing problems sensing when (referenced) resources have changed. Doing a clean build is your nuclear option, as depending on your compilation time, it can take quite a while. A better option is just to delete the .app bundle out of the build directory. This doesn't take as long for Xcode to reconstruct, although if you have a lot of resources, it also can take a while. The best option (the one I use) is to leave a "dummy" file at the root level of the folder included by reference (let's say it's a blank text file), and when I update a resource, I will make a change to the dummy file, undo the change, and hit Save (inside Xcode). This triggers something in Xcode to recursively go through that included directory to see if anything's changed.
All that aside, if you are modifying the DB file, and SVN is telling you that you haven't made changes to it, you have some other problem going on. Simply put, are you certain that the DB file has been added and checked in already to SVN, so SVN knows about it? And are you certain you're editing the same file you're checking in SVN?
Could it be that the database is elsewhere? Have you tried opening the database manually to see if the right records are there?
I've recently migrated code off of a limping SourceSafe database to a fresh SourceSafe database. We're maintaining the old database to keep our version history, but I'd like to mark those files as obsolete, so other programmers don't get confused as to which version to use.
Does SourceSafe support any feature that lets me flag files as obsolete but keep them in the database?
You yourself, check all of the files out of the old source safe,
and they will come and ask you to check them back in.
At that point you can educate them.
delete option will do this for you. The file (and its) revision histories will remain in version reporitory but file itself wont be visible from current version onwards