I installed the dotnetnuke Blog module and am getting an error when I try to manage it:
Error: is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Unknown server tag 'dnn:DNNGrid'.
---> System.Web.HttpParseException: Unknown server tag 'dnn:DNNGrid'.
I looked on their site but couldn't find much of anything.
You likely need to upgraded to the latest DNN8 specific release of the Blog module.
https://github.com/DNN-Connect/DNN-Blog/releases
https://github.com/DNN-Connect/DNN-Blog/releases/tag/06.03.00
DNN8 had breaking changes, that required some modules to be recompiled.
Related
I am getting the following error when publishing my create react app but the error doesn't appear locally. I recently updated my React version and a load of packages too. I'm guessing it's possibly something to do with that as I've never had this issue before?
Error during service worker registration: DOMException: Failed to register a ServiceWorker for scope ('https://**subdomain**.azurewebsites.net/') with script ('https://**subdomain**.azurewebsites.net/service-worker.js'): The script has an unsupported MIME type ('text/html').
Any input on this will be greatly appreciated. The error doesn't appear to be breaking anything from what I can see but I'd rather not push this to production with any kind of errors
So turns out the issue was because I updated the react version. CRA doesn't have service workers out of the box anymore. The project was returning 'unsupported MIME type ('text/html')' because it was hitting 404 looking for a file that doesn't exist.
The fix was relativly simple.
I replaced the registerServiceWorker() in my index.js file with reportWebVitals(). I then added reportWebVitals.js to my src folder. (I just created a temp react project and pulled the file from that). After I did that it started to work for me. I think I also had to npm install web-vitals.
After installing the module H5P, my site wouldn't load and only displayed "Error" The website encountered an error, please try again later
I had to manually disable the H5P modules in the database then clear the cache and a few minutes later the website started loading again. It also seems as if sub-domains couldn't load during this time.
Has anyone else experienced this?
After uninstalling and deleting the H5P module, it still shows on the page: admin/config/system/h5p but when the H5P link is clicked I get a Website encountered an error, please try again later error.
I can't seem to clear the cache via the site admin and I can't save panel pages. It says saved but when i try to access the page url, it says page not found.
Someone else said "I've had the same or similar issue. When I install, I just get a WSOD. I ended up using the missing module cleaner to get my site back to working normal after manually uninstalling it."
I've installed the module missing fixer module and when I enabled the module I got a "Website encountered an error, please try again later error." message but when I refresh the page, it shows the module is enabled.
However, when I click on "configure" from the module list page, it takes me to /admin/config/system with no option to configure the settings or actually use the module.
Should I be looking in the database for something that could fix this issue?
This issue was fixed by truncating every cache_ table in the database.
after deploying the "AngularJs_1.5.11" app to "azure-websites" using "azure-devops" continuous-integration and deployment gives error:
[$injector:modulerr] Failed to instantiate module app due to:
Error: [$injector:modulerr] Failed to instantiate module app.core due to:
Error: [$injector:unpr] Unknown provider: ENV_VARS
below is the screenshot of the error while accessing the AngularJS azure-website :
also find below screenshot of my build pipeline in azure-devops which deploys AngularJS application build to "azure-websites"
below screenshot is my application code in VSCode
I just started working on this new project which uses AngularJS_1.5.11 so I have no clue what is going wrong. I tried these links
unknown ENV provider in AngularJS from stack but as I am new to AngularJS I have no idea where to apply the changes in my code mentioned in the link.
Any suggestions would be of great help.
Edit:
#Mark if you look at the screenshots below you will come to know how we are setting "ENV_VARS" in the code using "gulp.js, env.config.js, config.json" file
Edit1:
#Mark please find the screenshot of the 'config.js' file which gets created in the gulp task 'ng-config' using source file 'config.json' under "./src/client/app/config.js"
Here are the docs regarding the knowledge relevant to this issue.
Somewhere in your program, it is trying to reference one or more members defined in an angular provider registered as "ENV_VARS". Providers are angularjs objects that are available during compile time (see the table row for "object available in config phase" in this SO answer)
I would search the source of the application to see if this provider was further configured elsewhere (you can search by its name 'ENV_VARS') as it may not be getting sent over with your other source files.
To attempt a quick fix:
On the first line of your app.module.js, change it to this
angular.module('app.config', []).constant("ENV_VARS", {});
This will likely result in another error, but it should pinpoint you to what is trying to access this provider. I'm assuming this is either inherited code or from a purchased template so you may want to investigate the sources to that if possible.
After upgrading to DNN 9, I get the following error when I try to place modules on the page:
`Error occurred when request service 'AddModule'.
With most of my modules, if I refresh the page after getting the error, the module appears "hovering" and ready to be placed on the page. But with one custom module I created using Christoc's custom module templates, nothing happens when I refresh so it's impossible to place the module on a page.
What can I do to fix this error?
It's been a while. But I had a similar problem. In my case the problem was an extra entry in the <moduleDefinitions> node of the .dnn file. Like a reference to an ascx file that was part of the original template, but was deleted by me, but not from the .dnn file.
It seems DNN 9 is much more strict when it comes to modules and adding them.
when I add braintree extension to my codenameone project and send android build to codenameone I got build error with these error log:
FAILURE: Build failed with an exception.
What went wrong:
A problem occurred configuring root project 'NLApplication'.
Could not resolve all dependencies for configuration ':_debugCompile'.
Could not find com.android.support:cardview-v7:26.0.0.
Searched in the following locations:
https://jcenter.bintray.com/com/android/support/cardview-v7/26.0.0/cardview-v7-26.0.0.pom
https://jcenter.bintray.com/com/android/support/cardview-v7/26.0.0/cardview-v7-26.0.0.jar
file:/tmp/build2388050053529696565xxx/NLApplication/libs/cardview-v7-26.0.0.jar
file:/tmp/build2388050053529696565xxx/NLApplication/libs/cardview-v7.jar
file:/home/ec2-user/android-sdk/extras/android/m2repository/com/android/support/cardview-v7/26.0.0/cardview-v7-26.0.0.pom
file:/home/ec2-user/android-sdk/extras/android/m2repository/com/android/support/cardview-v7/26.0.0/cardview-v7-26.0.0.jar
file:/home/ec2-user/android-sdk/extras/google/m2repository/com/android/support/cardview-v7/26.0.0/cardview-v7-26.0.0.pom
file:/home/ec2-user/android-sdk/extras/google/m2repository/com/android/support/cardview-v7/26.0.0/cardview-v7-26.0.0.jar
Required by:
:NLApplication:unspecified > com.braintreepayments.api:drop-in:3.1.0
Could not find com.android.support:design:26.0.0.
Searched in the following locations:
https://jcenter.bintray.com/com/android/support/design/26.0.0/design-26.0.0.pom
https://jcenter.bintray.com/com/android/support/design/26.0.0/design-26.0.0.jar
file:/tmp/build2388050053529696565xxx/NLApplication/libs/design-26.0.0.jar
file:/tmp/build2388050053529696565xxx/NLApplication/libs/design.jar
file:/home/ec2-user/android-sdk/extras/android/m2repository/com/android/support/design/26.0.0/design-26.0.0.pom
file:/home/ec2-user/android-sdk/extras/android/m2repository/com/android/support/design/26.0.0/design-26.0.0.jar
file:/home/ec2-user/android-sdk/extras/google/m2repository/com/android/support/design/26.0.0/design-26.0.0.pom
file:/home/ec2-user/android-sdk/extras/google/m2repository/com/android/support/design/26.0.0/design-26.0.0.jar
Required by:
:NLApplication:unspecified > com.braintreepayments.api:drop-in:3.1.0 > com.braintreepayments:card-form:3.1.0
It seems that Braintree pushed out a 3.1 update with an odd new dependency that fails. I've restricted gradle to use 3.0 and will push out an updated cn1lib. This should appear as an update in your extension manager later today. However, if you have the cn1lib already installed you will need to first delete the build hint android.gradleDep then do a refresh cn1libs.