I have confirmed that my Django project works perfectly. However, I am interested in integrating wagtail CMS into the project.
I am following Wagtail documentation, for proper guidance.
However, on clicking python manage.py runserver. I get the error shown below.
Wagtail Integration Error:
I have removed all my created apps from INSTALLED_APP, I have also removed them from the available URLs.
Unfortunately, non of the above method fixed the problem for me.
Your guide on how to fix this type of error will be appreciated.
I am not 100% sure of the steps you have taken. If I understand your question correctly, you added Wagtail to your Django site and then removed it again. But you are still getting an error message related to wagtailcore.Site. If that is the sequence of events, then I would say you did not fully remove all mentions of Wagtail from your code. Can you reset your code to the point before you added Wagtail using version control (git or whatever)? Or, if you have made other changes you don't want to lose, perhaps search your code for any other mentions of "wagtail".
If you would like to carry on integrating Wagtail into your site, please repeat the install steps and then post any errors you receive at that point so we can try to help. (And by the way, posting the error message inline as a code snippet makes it a lot easier for us to see the error at the same time as the description of how you got there.
Related
i am using B2C provider for DNN and trying to install it as extension and it's throwing error https://i.stack.imgur.com/6faW1.png
i am trying to use multiple version as well but not installed properly and using source from https://github.com/intelequia/dnn.azureadb2cprovider/releases
Please help me out.
There was an issue in the DNN manifest file that has been solved on v1.4.7 (release https://github.com/intelequia/dnn.azureadb2cprovider/releases/tag/v1.4.7). Tracking the issue at https://github.com/intelequia/dnn.azureadb2cprovider/issues/19
I wrote the answer below before seeing this: https://github.com/intelequia/dnn.azureadb2cprovider/issues/19
Perhaps this is pertinent to your question. You might want to check with Ryan Moore (moorecreative" to see if he was able to resolve the issue.
First, please bear in mind that I am not familiar with this particular extension, but it seems as if it is "just another" authentication provide for DNN.
I'm also a little confused. The error message indicates that you've already installed th Intelequia AzureB2C provider. Is that true?
You also say "I am using" and then "trying to install it as an extension." If you are using it, that means that it is already installed as an extension, so a second attempt to install it should throw an error. But, I would think that the installer should see that problem earlier in the process.
Finally, you say "i am trying to use multiple version as well." A provider should be installed only once, and that is what the error message is telling you.
Once you have installed an authentication provider you typically enable it for a portal, and it becomes part of the authentication process.
You should read the documentation carefully, and make sure that you are trying to use the provider as the developer intended.
I followed the tutorial Node.js Quickstart, including installing the libraries googleapis and google-auth-library. I believe I followed the instructions for setting up the credentials properly to my best ability, but I lack the experience to know for sure.
I was unable to exactly follow the tutorial, specifically this line:
e. Select the application type Other, enter the name "YouTube Data API Quickstart", and click the Create button.
because the drop down selection box had no "Other" type.
I had a project using this system working in the past, but it suddenly stopped working. I had not used the program for months, so it is possible something happened in the meantime, but I also absentmindedly revoked the program's access to my Google account.
I am not using the same credentials as before it broke -- in the developer console, I not only deleted the old credentials and downloaded brand-new ones, I created a new project altogether.
Here is an image of the credential:
Of course, I downloaded and renamed the client_secret JSON as instructed.
Here are my project files:
Since I directly copied the code, I have not tried changing it, though I did look through it to make sure there were no IDs I needed to copy in or anything of the sort.
I tried looking through this article, but I had no idea where to even begin the stated debugging processes, as my only experience with OAuth, Node.js, and the YouTube API is this project, and I don't even understand how I got it working originally.
If anyone has any ideas on ways I could try fixing this, or more thorough instructions on how I could begin debugging, I would be immensely grateful.
If relevant at all, I am using the WebStorm IDE.
Screenshot of the terminal:
We have to migrate several node.js applications from Loopback3 to Loopback4.
So the first step we want to do is a basic migration following guidelines (1 and 2), and then complete it by manually upgrade methods and logic, and completely remove lb3 application.
Unfortunately, at the end of the migration steps in the guide, when trying to start the app (node -r source-map-support/register .), we receive the following error:
...
Swagger: skipping unknown type "Document".
Cannot start the application. { S2OError: Could not resolve reference #/definitions/Document
...
Any help would be appreciated.
OK,
I had also opened an issue on loopback-next repo on github, at the same time of this question.
So this problem has been solved on that thread.
Here the solution:
I've temporarily changed this return type to Object, and it runs successfully and migration goes fine. So I've solved in this way as my scope is to rewrite this specific method.
Anyway I have to say the lb3 application runs fine, even though this type is not defined in it.
I hope this may help someone.
I have upgraded Kentico site from Kentico 8.2 to Kentico 9.0, everything was looking pretty and working smoothly. But when I tried to export my own site, I got Exception with following statement.
“Conversion failed when converting from a character string to unique identifier”.
From your current description it is impossible to tell what might have broken. The exception you are getting is very common and you can find many examples of reason why it happens here in SO.
However, what might be related to your question in Kentico is whether the upgrade you performed was successful. Try checking CMS_SettingsKey table for following KeyNames
CMSDBVersion
CMSDataVersion
Are they both set to 9.0? If not, the upgrade was not entirely successful. If yes, then there is some other issue within the data in your database for which we would need much more information.
Some of the class form definitions haven't been upgraded properly. Try the upgrade again and make sure you perform all the Steps after upgrade, especially "Running the website - First request".
Our NoFlo graph components have suddenly compressed themselves all into one uneditable box that says "WaitForward". See attached image.
For a while, this was happening on every browser, except Opera, so I could go in there and update graphs. Then, a couple of weeks later, even Opera wouldn't render the components, so now I am unable to add anymore logic to existing NoFlo forms.
We barely touch code related to NoFlo, so I don't think anything changed in our environment. My theory is that browsers (such as Chrome, which used to be the one stable browser to use for editing) have been updated recently, and this tool needs some kind of an update in order to render properly. Yet I can find no reference to this issue on the NoFlo GitHub instructions, and it doesn't look like anyone is having that issue here on StackOverflow (until now, of course).
The error message in the console says::
"TypeError: this.node.getTransformToElement is not a function"
I plunked this error into Google and saw that others are experiencing this with something called clientIO, and that recent updates to Google Chrome are to blame, as Chrome has recently removed a core feature that allowed related js to function.
But ... how can I fix this? That is the question!
It looks like recent updates to Google Chrome are the culprit.
Taken straight from jointjs.com's website::
Link to announcement from jointjs.com
Announcement: getTransformToElement() polyfill Nov 12th, 2015
Unfortunately, a new version of Chrome (48) removes a feature that is core to JointJS/Rappid. This feature is the SVGGraphicsElement.getTransformToElement() function. The motivation behind removing the method is - according to the Chrome team - open issues about how this method is supposed to behave.
To overcome compatibility issues with future versions of Chrome, we prepared a polyfill that makes sure this method exists. Before a new version of JointJS/Rappid is released (or if you, for any reason, don't want to upgrade), include the following code before you load your application JavaScript:
SVGElement.prototype.getTransformToElement = SVGElement.prototype.getTransformToElement || function(toElement) {
return toElement.getScreenCTM().inverse().multiply(this.getScreenCTM());
};
I was unsure exactly where to put this code in my noflo directory. So I tried putting it at the tippy top of the "app/js/main.js" file. It seems to be working! (But advice for a better location is more than welcome.)
I hope this helps anyone else out there who is experiencing the same issue.