Hey all, I uninstalled a content type that I'd previously added and afterward I'm still getting a warning of
2010-01-06 22:43:50 WARNING OFS.Uninstalled Could not import class 'myclass
' from module 'ns.archetype_name.content.content_type_name'
It isn't resulting in obvious problems, but it concerns me since I thought I'd uninstalled it properly, and cannot find any place where I left a trace of it. I've restarted the server, re-run buildout, and everything else I can think to try to get rid of that message, to no avail.
I read online that this warning is an indication that the Data.fs is out of sync with the packages, in question, and that I should re-install the missing packages. I did that, and the error went away, but I'd really like to get rid of both the error and the content type in question.
Thanks!
Paul
It appears to me that the issue here was that there was content of that type on the portal; and so uninstalling hte package basically 'orphaned' those items, causing that error.
You can try the following:
Uninstall, remove, buildout.
Go to ZMI at the zope root, Control
Panel, Products. See if the the
product is listed. Remove it.
Restart.
This will likely make the annoyance disappear and if the product was providing simple content types should be enough. However you should check for funky left-overs such as persistent utils.
A good tool to help you find out what's going on if you still run into trouble is zodbupdate. IIRC the latest version will only run on python 2.6, you should use the earlier ones.
Related
I'm pretty new to using Github and Git in general. But this error is driving me crazy because I can't find anyone with a similar problem..
In short. Whenever I try to commit a saved file to a repository in Github I get the following error:
enter image description here
I tried reinstalling RStudio and changing the project to a different folder because I thought maybe there was an issue with writing rights, so I don't think that is the problem. I find it interesting that the message inside the Error warning is in Spanish. I remember that RStudio was initially like with Colombian formatting or something like that, that I had to change to install and use packages. But I don't really remember that well what that was. However, I don't think it has anything to do with this.
Thanks in advance for your help.
After the fall of the server with the site entrance to the admin page redirects to install the module "Magnolia Scheduler Module". When I try to install it get the error:
Error while installing or updating scheduler module. Task 'Bootstrap' failed. (ItemExistsException: a node with uuid 54b56ea3-a89c-4736-b234-b62b63b6e602 already exists!)"
Maybe someone knows how it repaired?
On top of my head right now, this may happen when one has scheduler module jar one than once? Also I assume that, you are trying to upgrade Magnolia, It is also important to know the versions of this upgrade.
One possibility to solve it to change importUUIDBehavior in SchedulerModuleVersionHandler. Therefore, one may change the conflict strategy as they wish and hence, not hit to those exceptions anymore. However, It is also important to be careful while doing these changes.
Meanwhile, you may want/need to use https://documentation.magnolia-cms.com/display/DOCS/Groovy+module#Groovymodule-RescueApp for undetstanding what actually had happened.
Hope this helps,
Cheers
here's what's happening. within the last few days something happened to my solution that apparently broke nuget. when i go into package manager/installed and do a find on SignalR, nothing comes back as if SignalR wasn't installed when i know it is. when i go into manager/online and do the same, all the signalr libraries do appear but with green checkmarks next to them as if they WERE installed. but i have to way of uninstalling/reinstalling. this has been driving me crazy since i now can't seem to get a stable solution.
on top of that, running nuget commands from the console always result in a CommandNotFoundException. nothing works except get-help Nuget.
what i'd like to do is reset everything related to Nuget so i can reinstall those packages from scratch and hopefully fix the console commands.
any ideas?
I think this happened to me a few times. Go to the packages.config file that should be the root directory of your project and remove the insurgent (in your case the line with the package: SignalR). This will tell NuGet that the package was never installed.
Now you will be able to reinstall it through the repository, then uninstall it so everything is back to the way it was before you got into this mess. I am unsure how it is occurring.
After installing ASP.NET MVC 4 Beta, Visual Studio shows "Updating source control status" on the lower left side of the status area.
Any ideas? Seems a lot of stuff is broken after installing the beta. I am trying hard not uninstalling it.. :(
Issue is Nuget Manager. It installs templates for both ASP 4 and ASP 2.
Uninstalled Nuget Manager and then re-installed it (reopen VS Studio) and solutions come up in few seconds
I have the same exact problem! It seems to take forever to deal with TFS when opening a project.
I already uninstalled it once to verify (yes, it solved the problem). Now, I've re-installed and it came back with a vengeance. VS.NET locked up with loading my project :(
I'll post more if I get anywhere...
UPDATE: I waited longer and VS.NET wasn't locked up, it just took a really long time (5 minutes or so).
It seems that it's related to NuGet packages somehow, since my Source Control window has almost 1200 messages like this:
The item $/...[snip].../packages/AmplifyJS.1.0.0 already exists.
The item $/...[snip].../packages/AmplifyJS.1.0.0/AmplifyJS.1.0.0.nupkg already exists.
Every message in there is "already exists" for something in the NuGet "packages" folder
I'll keep you posted
UPDATE 2: I added a "Connect" bug. Go there and verify that you can see it too to get it more attention.
As Sonali pointed out, the issue is related to NuGet. On solution open, the NuGet package manager does a version control operation for every file in your "packages" directory. This issue should be fixed any day now in their 1.7 release by making it a one time bulk operation.
In the meantime, if you're using VS11 with TFS11, you can upgrade your workspace to a "local" workspace to eliminate the delay on solution open.
We were experiencing the same problem when opening projects...delays up to 10 minutes while the solution was loading. Our only solution after trying many suggested solutions via web searching, was to purge all deleted files for the project(s) in source control. Different solutions for different people seem to exist but if nothing else has worked, then maybe this helps.
I'm finding this problem in VS2013 Ultimate, but was not seeing the Nuget messages mentioned in other replies. The consistent message is "Updating source control status...", which can take upwards of 10 minutes to complete. It occurs at what seems like random intervals - I could be opening a solution, or typing out code, and UI lockup with the above message.
The solution that appears to be working for me now is to edit the devenv.exe.config file. Details can be found here.
Essentially you add one line to disable the default proxy. I hope this helps someone else.
I hate to ask the same question others have asked in Stackoverflow, but I still can't figure out why Installaware 7.0 R2 has this problem.
I need to build a installable CD for the previous version of my software. So, I am using what came with RAD Studio XE to do this. After creating a new Win32 setup for installation and customizing it, I built and test ran the project. In the middle of the installation, it raised an error, "Error Folder Path 'C:' contains an invalid character." So, I went back and created another win32 project and without doing any changes to anything I compiled, built and test ran the project. It worked without any error. After spending hours changing one thing at a time and testing it over and over again until I hit the error message again, I finally found the offending property in the Installaware. The error is raised thereafter once you change the Target folder textbox default value which is $PROGRAMFILE$\$TITLE$\ or Shortcut folder textbox default value which is $TITLE$. They only way to get passed this error is by not changing those default folder paths and allowing the user to change the folder path during installation.
It sort of annoying especially when you spend thousands of dollar purchasing these software from Embarcadero and Codegear. Is there a fix for this? Does anybody know?
These variables are resolved automatically to full folder paths. If you delete them or set an incorrect value, your package will not be able to resolve the installation path (hence the error). So the path edit controls should have valid default values.
If you don't want to allow the user to change your installation path, you can try deleting the dialog which offers this option. I'm not sure if that version of InstallAware supports it though.
If you don't like InstallAware, there are some good free or commercial alternatives which may help you.