I'm using the NuGet N2CMS package. I've tried version 2.9.6.8 and 2.9.6.14( and .16)
This is a fresh setup/install. When finishing the setup and navigating to /N2 I'm getting a 404 Not Found from the following:
/N2/API/Context.ash?mode=full
You can see my question on their GitHub here.
Anyone experience this, or have a fix?
bherila from the N2CMS team, was able to help me. It turns out that some of the Nuget Packages do not work out of the box; one of which is the standalone N2CMS package.
I was able to get a new project working using the N2CMS.NoZip (management UI) and N2CMS.MVC packages.
Even with these, you will still need to create and decorate a RootPage and StartPage to get past installation. You can see how I created those in the link I posted in my question
Related
I have read other posts with people having issues with the 404 Not Found error when building their own local version of NuGet.Server. None of them specifically asked about what I am seeing as an issue.
I followed the instructions at https://learn.microsoft.com/en-us/nuget/hosting-packages/nuget-server and get the Default page just like it said. The only changes I made to the web.config were to set the requireApiKey=false since this will be a local server.
When I click on the "Click Here to View Packages", and get the 404 Not Found error, I noticed something on the page. It looks like it is trying to resolve to the same URL that is shown as the link for the Package Manager (https://localhost:44375/nuget), but then adds "Packages". Which might seem okay until you look at the "Physical Path" that is listed. It has a physical folder called "nuget" which is not there and was never created in the instructions or during the install of the NuGet.Server package.
Here is a screenshot of the 404 page.
There was nothing in the documentation about adding that folder, and it was not added when NuGet.Server was installed. Is this a configuration issue that I cannot seem to find, a setup step missed in the instructions or a bug in the NuGet.server ?
Cloning a project and it looks like it comes down fine, until I look in the references and they all have the yellow warning triangle. Then my Error List shows all the references as Warnings. My application is on Visual Studio 2017 and it is MVC with C# coding using .NET Framework 4.7.2. In my normal application, original, the references are perfectly fine and no errors and it works great. Builds and works fine. Once I bring down the clone is then the references are lost. I've done a build on the cloned version and it shows all the references as warnings.
I've double clicked a reference and received an error popup box of "This project cannot be viewed in the object browser because it is unavailable or not yet built. Please ensure that the project is available and built". It feels like Azuredev-ops is just missing my references and their location. I am the only one working on this, so there should be no conflicts. I've posted and cloned right after posting, with same result. My code and Web configs look just fine. I have cloned on other people's system too, and same problem with this application. FYI, many of my other applications are working fine using the clone. Just 1 application is having issues. My references are separated in that some are Copy Local True while others are False. I've also removed a reference and added it back, and it comes back with a warning as if it were never added.
Warning message for individual reference:
The referenced component 'EntityFramework' could not be found.
I am also seeing errors for NuGet packages not being there, but when I look I see the package folder with all it's components in it.
It says that for all my windows core references. And just warning symbols in my reference folder for other references.
I am expecting no errors when I bring down the clone. I've upload using my machine and cloning should be able to use the same reference locations. It just feels like AzureDev-Ops is stripping my reference links out, and then going I can't find them.
Azure-DevOps clone shows references as warnings
To resolve this issue, you should make sure of the following:
Make sure you have checked those two options Allow NuGet to download missing packages and Automatically check for missing packages during build in Visual Studio:
Make sure you do not check the \packages folder to the source control.
When you clone the project from Azure-DevOps server and get missing reference error, you should use the NuGet command line Update-Package -reinstall in the Package Manager Console to force reinstall the package references into project. Check this thread for some more info.
Note: Especially need to pay attention to the third point.
Update:
Error:Mircrosoft.CodeDom.Providers.DotNetCompilerPlatform.2.0.0
According to the error message, it seems you are not add your packages to your packages source in Visual Studio.
You should publish your custom packages to the nuget feed or you can create you local nuget feed, then add the nuget feed path or local feed path to the package source:
Check this document for some more details.
Hope this helps.
I figured it out. I went to my original and did the Update-Package -reinstall. It came back with the Microsoft.CodeDom.Providers.DotNetCompiler.Platform.2.0.0 not there, but it added one, just not 2.0.0. Then I ran an uninstall of the Microsoft.CodeDom.Providers.DotNetCompiler removing it from my system. Then I posted my original up to AzureDev-ops. My clone came down, not all the references were messed up, some were still, but I did a rebuild and that cleared it up. Thank you to the responses, it pointed me in the right direction.
I am new to TYPO3. I recently upgraded TYPO3 to 6.2 LTS from 4.5 following steps from some websites. Everything seems to be working okay.
I created a test folder and tried to edit the folder. I got INVALID VALUE("254") in Page Type. Here is the image
http://i.stack.imgur.com/h85Hx.png
I looked at logs, developers logs, and searched Google but I did not find anything relevant to the problem. Any idea on where to start?
PS: I didn't have enough reputation to add images directly. So, sorry for the link.
254 is the page type "Folder". It is very strange that this should be illegal. It's working here on a 6.2 installation.
Maybe it's a TypoScript configuration that disallows folders as subpage types at the parent page.
Have you already tried "database compare" function in your install tool? Looks for me like a update problem.
I have downloaded and installed Zend Server community edition. I am on a mac.
I have tried to changed the path in
/usr/local/zend/apache2/conf/httpd.conf
so that it pointed at a test file in my documents folder. However, when I type
http://localhost:10081/test.php
into my browser, I just get 404- page not found.
Any suggestions? I am new to web stuff and don't really know what I'm doing wrong.
You can find step by step directions for setting up your local environment on a mac:
http://www.cmiwebstudio.com/blog/zend-server-ce-for-mac-osx-10-lion/
and some other posts that may also help here:
http://www.cmiwebstudio.com/blog/tag/zend-server-ce/
I am using Eclipse for Android dev and everything was going fine until I tried to incorporate the facebook SDK. Now when I tried to back it out, there appears to be an artifact left behind that Eclipse tries to link the FB library?!?
[2010-11-17 18:50:22 - Library Project] Unable to set linked path var '_android_com.facebook.android' for library /Users/mobibob/Projects/workspace/facebook-android-sdk/facebook: Path variable name cannot contain character: ..
Any clue where this command / reference is in the build configuration? I have scoured it as best that I can, but I still get the same error.
Problem solved ... as it turns out, it was not so much the Facebook SDK but something that I did in the process of configuring the library reference. I am not entirely certain of how I misconfigured, but I was tweaking the various "path" settings such that, once when the automatic build tried to build my project, an import for android.R was added to my source module. This superseded com.myproject.R and would not resolve the values for resource references.
There were other problems with path order and setting that I modified during the troubleshooting that made it worse. Recreating the project without Facebook was the first step to discovery and fixing.
Either way, the lesson I learned is that the build error messages can misdirect one to the configuration when the problem is in the source code.