I installed Umbraco 7.2.2. from the latest nuget package. However, annoyingly I just clicked install from the initial install wizard, as shown below.
Unknowingly it wouldnt ask me for the DB connections. So my question is. Is there a clean way to revert the installation and start again. Or am I just best to delete the project and install the NuGet package again?
Im aware of earlier versions that I could just remove the appsetting value below and it would start the installer again.
<add key="umbracoConfigurationStatus" value="7.2.2" />
EDIT:
This is no longer the case. Removing the value from the above app settings only looks to upgrade the installation.
However I dont want to be left with a bloated Umbraco install with redundant files, like the .sdf DB etc. Or is it the case that the normal install doesnt actually include many additional files than the custom install? And its just the SDF?
The more I write this the more it makes sense to just start again with a fresh project. :)
Keen to hear an opinion regardless.
Start with the current site as it is installed now and go to the backoffice (http://yoursite.local/umbraco). Go to the developer section > Packages > Installed Packages > Fanoe. Go to the Uninstall Package tab and confirm the uninstall.
In your web.config set umbracoConfigurationStatus to an empty string:
<add key="umbracoConfigurationStatus" value="" />
And set the connection string to the default empty values:
<remove name="umbracoDbDSN" />
<add name="umbracoDbDSN" connectionString="" providerName="" />
After saving this file, your application pool will recycle and you can delete the umbraco.sdf file from the App_Data folder. In fact you can delete everything in App_Data.
As you said, it would be much easier to delete the current site and just start over, choosing "Customize" during the next install.
Related
I am new to MongoDB and is trying to get this new Database connected with my Web api application ..But i am not able to add MongoDB.driver nuget for my Webapi project.Please refer screen shot.
My search is struck on this window for like forever.,have even restarted my project for a couple of times now.
I also tried installing this package through
PM>Install-Package MongoDB.Driver
But then this is shown
Am I doing something wrong ..?
i tried opening this url"api.nuget.org/v3/index.json"...but it says this site cant be reached..what does that mean?
Since the you could not open the url in browser directly, there should be some internet limitations in your internet environment. If you are work in the company, I suggest you contact your office IT to confirm whether they add any limitations and whether used any proxy. If they are using some proxy, you need to set the proxy settings in NuGet.Config file which store in C:\Users\user name\AppData\Roaming\NuGet as below settings. Detailed information please refer to the Proxy settings part in Nuget Config Section & Nuget Proxy Settings.
<add key="http_proxy" value="host" />
<add key="http_proxy.user" value="username" />
<add key="http_proxy.password" value="encrypted_password" />
Besides, you can chech the proxy in your machine: Open "System Properties" > Advanced > Environment Variables. Find the http_proxy var (in System variables), select and delete it.
I have a file_B.jsp that is quite happily referenced to in the web.xml file
<action name="File_B" helper-class="name.of.helper.fileHelper">
<result name="default" web-page="/path/to/jsp/directory/file_B.jsp" screen-name="File B" screen-id="file_b" />
</action>
And it is safely within C:\Users\myDirectory\workspace\webusr\WebContent\WEB-INF\conf\sub\directory
[Trust me - there are several dozens of other jsp files mapped out this way :-) ]
But come runtime the browser throws up a 404.
I checked in the directories under Catalina and there is no file_B_jsp.java nor file_B_jsp.class.
Now, I know the mistake I made. I did a copy/pasta from file_A.jsp (80% of the code and structure is the same).
I did a simple test and had eclipse make a NewFile.jsp and changed web.xml to
<action name="File_B" helper-class="name.of.helper.fileHelper">
<result name="default" web-page="/path/to/jsp/directory/NewFile.jsp" screen-name="File B" screen-id="file_b" />
and sure enough the browser could find it. And there were a NewFile_jsp.java and NewFile_jsp.class inside Catalina
So I copied the code from the file_B.jsp. Deleted the file_B.jsp, had eclipse make a new file_B.jsp and pasted the code back in. Put web.xml back to pointing to the file_B.jsp. Stopped the server. Cleaned it and started it again.
But still the browser says 404, as there is still no file_B_jsp.java nor file_B_jsp.class.
I absolutely need to have file_B.jsp named "file_B.jsp". The whole system is based on this naming convention (decades old legacy at an electrical power company)
What file inside of eclipse needs to be manually edited? Or can I just make a new Tomcat server on the development machine?
It seems some inside eclipse was misaligned. Either building a new server or running yet another clean or switching out of the workspace and switching back into the workspace got eclipse to start compiling the file_B_jsp.java and file_B_jsp.class inside of Catalina.
My aim is to have package restore working on a build server so that I don't have to check in binaries. At the moment, I'm simply trying to get it to work on my own machine using Visual Studio.
Here's what I've done so far:
Followed the instructions here http://docs.nuget.org/docs/workflows/using-nuget-without-committing-packages, including both setting the Tools-Options flag and the environment variable (belt and braces)
Installed the NuGetEnablePackageRestore package as suggested here NuGet package restore consent without NuGet
Checked everything in (the .nuget solution folder and its contents), but not the binaries I want to reference, because that's the whole point of the exercise
Here's what I'm doing:
Check out solution
Verify that nunit.framework.dll and moq.dll are not present in the checked out solution
Build the solution
Visual Studio complains that Moq is missing. I search for the dlls in the solution directory and find that:
nunit.framework.dll is present in the appropriate bin folders
Moq.dll is nowhere to be found
But there's more. This is truly mysterious, but if I do a fresh checkout, disconnect from the internet and build, I get precisely the same results - nunit.framework.dll is there, but moq.dll is not. The build process has conjured nunit.framework.dll literally from nowhere.
So it's something of an understatement to say that I am completely baffled. Can anyone suggest answers to the following questions:
Why is package restore not downloading Moq?
Where on earth is the build process getting nunit.framework.dll, if not the internet?
In vs, Options, Package Manager... there's a section "Package Cache", if you click on the "Browse" button it will take you to the location of the nuget cache in your machine.
Okay, I noticed in the documentation that enabling package restore was supposed to modify project files in order to add a new target. My project files did not have this change. Right-clicking the solution title in VS and selecting 'Manage NuGet packages...' then added the required changes and everything built as it should.
I checked, and package restore still appears to work when I have no internet access, so I'm still mystified about that. Does NuGet maintain some kind of cache of binaries outside the solution?
I'm producing plugin's for eclipse - but for some reason when I build a new version of the plugin - the update site isn't noticing it.
The build process says that the plugins should be at version 1.1.0.201209191506, but when I access to install I'm shown these versions:
The XML file looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<site>
<feature url="features/supportStructuresForCSFEditing -_1.1.0.201209191506.jar" id="supportStructuresForCSFEditing -" version="1.1.0.201209191506">
<category name="plancomps"/>
</feature>
<feature url="features/supportStructuresForCSFEditingTest -_1.1.0.201209191506.jar" id="supportStructuresForCSFEditingTest -" version="1.1.0.201209191506">
<category name="plancomps"/>
</feature>
<category-def name="plancomps" label="plancomps"/>
</site>
and this happens if I'm installing from local or from the web - any idea what might be happening? Or diagnostic tricks I could try?
EDIT - there have been restarts of the machine - and attempts from machines that have never seen the plugin's before - all have shown the old versions. :(
I'd check two things.
1) I think that due to a bug, sometimes features are removed from category (if you use GUI to update your site). So you might be looking at your plug-ins in your category, when latest version is at top level or vice-versa.
2) Eclipse caches current state of update site. So you need to restart, to make it show newer versions.
Most likely, your cache is not being updated. p2 will often cache update site content information. It looks like you are using old style update sites and that you do not have a content.xml(or .jar) and a artifact.xml(or .jar), which is not really supported any more and may make it harder to delete the cache.
Here are somethings you can try:
Help -> Install new software -> Available software sites -> (Select your update site) -> Reload
Delete and re-add your update site
Restart eclipse with the -clean option to clear out the configuration area
But, really you should be making sure that you are creating artifact.xml and content.xml (or .jar) and creating proper update sites.
Okay, so coming back to this I have a reason and a workaround.
Eclipse's caching is pretty aggressive. But something I was doing wasn't helping and I thought I'd share.
When I was building a new version of the plugin, I was deleting the previous one (which made sense to me, generally the previous one was an internal buggy thing and I could have always reconstructed it from the svn). However when I started leaving the previous versions in, the update site started working much more as expected.
I imagine the issue is already solved for the OP, but I thought I'd share:
I just spent 2+ hours fighting with a very similar problem and finally managed to solve it. I'm not sure whether my solution can be applied to this case. My case was like this:
I created some plugins and uploaded them to a software site I had also created.
In a default.target file I added the plugins from that software site.
I realized there was an error in one of the plugins, created it again, uploaded it to the software site, and clicked "Update" for that site in my default.target.
The plugin never got reloaded. Even when I deleted the update site, eclipse "magically" still saw it and pretended to update from there when I clicked update. Fun fun fun.
I tried all kinds of things and this is the only one that worked for me in the end (I'm going to assume that you have a default.target as well):
Remove the plugins that aren't being updated from your default.target.
Exit eclipse (at least the instance for the problematic workspace).
Backup your workspace, or at least default.target and <pathToYourWorkspace>\.metadata\.plugins\org.eclipse.pde.core\.bundle_pool\. It may be difficult to revert the following changes if you need to.
In <pathToYourWorkspace>\.metadata\.plugins\org.eclipse.pde.core\.bundle_pool\:
Open artifacts.xml and delete all references to the plugins that aren't being updated. Note that there may be multiple references to each plugin; for example in my case I have one with 'classifier='org.eclipse.update.feature' and one with classifier='osgi.bundle' (I'm using OSGi).
Open subdir features and delete the folders corresponding to the plugins that aren't being updated. (Sorting by date may help. Btw, in my case the "date modified" for those jars showed that they had only been downloaded the first time and never updated again)
Open subdir plugins and delete the jars corresponding to the plugins that aren't being updated. (Sorting by date may help. Ditto)
Open eclipse again, with the options -clean and -data <pathToYourWorkspace> so that it cleans the workspace.
Add the plugins to default.target.
If there are still problems try selecting the plugins or update site and clicking "Update", and/or restarting eclipse.
This almost drove me crazy. I hope this helps someone.
I think you first use a fresh copy of eclipse to add a plugin,if that plugin is already installed.Copy eclipse.zip in new folder,unzip it ,run eclipse and then start using update site to do this please
Help-->Install new software-->"paste update site url"-->It will catch updates-->click ok-->accept license-->"continue process"-->It gives a warning press Ok " now you are success in updating.
Note:An internet connection should be properly available.
I wrote a plugin using FireBreath, VS2010, for Windows, all browsers.
In FireBreath documentation I saw that I have to install WiX. I installed it.
I created the project using the automatic fbgen tool so it autmatically created a WiX for me.
I couldn't understand from the doc is waht to do now:
Do I have to edit the generated WiX source file? If yes, what to change there?
What to write in the object tag that will trigger the installation of the msi created?
Or at least say to the user that installation is needed and link him to a download?
10x!
With the WiX Toolkit installed, re-run the prep__.bat file to regenerate the installer project along with the main plugin project. Build the plugin project, then build the installer project named something like {YourPlugin}_WiXInstaller. The msi will be placed in Firebreath's \build\bin\{YourPlugin}\{Configuration} dir ( {Configuration} is Debug, Release, etc).
It's not necessary to edit the WiX file unless you really want to change a specific setting. One thing I can think of is changing the default per-user install to all users. Per-user is usually better because it avoids UAC issues.
Deploying it to the user is a bit trickier. For most browsers, the user must save & run the msi. On IE you can declare an object in the HTML body and point the codebase to a URL containing the plugin:
<object id="pluginid" type="application/x-yourplugin" width="0" height="0" codebase="/YourPlugin.msi" >
<param name="onload" value="pluginLoaded" />
</object>
However IE9's security seems to block MSI's here. It does work if the plugin DLL is used (codebase="/YourPlugin.dll"). This auto-install method only works in IE with signed binaries (unless IE's security options are cranked way down).
Hopefully a discussion thread on the MSI security issue will yield some answers.
Update:
As hinted by Richard / taxilian, an MSI must be packaged within a CAB file in order for IE to install it. Getting the INF right and creating the CAB takes some additional steps as documented by RB. And to add yet another wrinkle, Vista/Win7 do not allow the INF to call any binary outside of the CAB file, so a stub launching app must be used (see this thread and example code posted by Roey towards the bottom).