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.
Related
We are trying to make an PWA which works offline. Until December last year it was working fine, we could load the app, go through the content, change pages.
Something happened and we are not able to load the app anymore and we have this error. We have tried a lot of things on the service worker and nothing has worked.
If someone knows how to solve this, please let us know.
Thanks
[SPLoaderError.loadComponentError]: Failed to load component "86682639-29f2-47cc-ac3f-cc259ef2959d" (AppWebPart). Original error: Manifest not found for component id "0d910c1c-13b9-4e1c-9aa4-b008c5e42d7d" and version "16.8.5".
INNERERROR: Manifest not found for component id "0d910c1c-13b9-4e1c-9aa4-b008c5e42d7d" and version "16.8.5". CALLSTACK: Error
at t [as constructor] (https://res-1.cdn.office.net/files/sp-client/sp-classic-page-assembly_en-us_b9f62e31470bfd5b13c16abbbd9a56b1.js:68:116110)
at new t (https://res-1.cdn.office.net/files/sp-client/sp-classic-page-assembly_en-us_b9f62e31470bfd5b13c16abbbd9a56b1.js:68:299482)
at e.buildErrorWithVerboseLog (https://res-1.cdn.office.net/files/sp-client/sp-classic-page-assembly_en-us_b9f62e31470bfd5b13c16abbbd9a56b1.js:68:336766)
at e.buildLoadComponentError (https://res-1.cdn.office.net/files/sp-client/sp-classic-page-assembly_en-us_b9f62e31470bfd5b13c16abbbd9a56b1.js:68:332857)
at https://res-1.cdn.office.net/files/sp-client/chunk.systemjs-component-loader_en-us_c9d296eaa8490acee6b3.js:1:6036
We have tried caching different links on the service-worker but they all got the same error.
I am starting to help someone with a new project. This project is React (React Native as is a mobile app).
The project is working fine on her laptop (in her browser), and when I scan the Expo QR code, the app works fine on my Android device.
However, trying to run it in my browser is throwing all these errors:
The 'Can't resolve' error doesn't make sense, because the correct react native files are there. Is this a cache problem? I have tried deleting the .expo/web/cache folder and starting over.
Also, why are there multiple errors in my console, but only one being shown in the information on the actual web page? Does this mean that the single error being shown is causing all the other errors, or it is the only one which needs fixing, or will it show the next error when I fix the one that is being shown?
Thanks
Seems to have been a known problem re babel. See the links below:
https://github.com/babel/babel-loader/issues/173
how to solve this error You may need an appropriate loader to handle this file type
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 try to run my app on the emulator in Smartface App Studio, I get an error. It so interesting, i tried something to fix it and googled to find a solution lots of times. But i got nothing.
Checking Android SDK Configuration.Searching for Devices...Device found: Faea HY509SGenerating Exporting Packages for Android profile:"Default"Pages, JavaScripts files are preparingProject resources are preparingDatasets are preparingInstallation packages are creatingInstalling Emulator...Application could not install toError Message : pkg: /sdcard/SmartfaceEmulator.apkFailure [INSTALLFAILEDCONTAINER_ERROR]
Same issue again? Please refer to Troubleshooting document!Sorry, an error occured during launching! Please try to launch from your device.
The problem is about Manifest configuration.
I guess you changed some part of it.
There is a manifest entry like android:installLocation
it should be auto like;
android:installLocation="auto"
Smartface.io Team
Is there a way to get details about this error? I turned off custom errors:
It looks like I am missing a skin file. How do I get it back? I used the one from the default install of DNN 6.2.4.
You could look at your DotNetNuke log4net config settings and check where you are logging errors. The default location is {DotNetNuke_Root_Folder}/Portals/_default/Logs/.
The log level by default is set on error so you can change that to "Debug" if you want by changing the element in the following config file {DotNetNuke_Root_Folder}/DotNetNuke.log4net.config
You can copy the skin's folder in your DotNetNuke installation zip file to your installed DotNetNuke website. Path to skins (DotNetNuke_Community_07.00.05_Install.zip\Portals_default\Skins)
Hope this helps.
You can get all error detail from LogViewer module of DotNetNuke
Login as administrators then go to Admin-Event Viewer , here you can find the details about error.
I had this error also; on a local instance. After installing a DNN Template via the .visx file, IIS had set up a virtual directory for the desktopmodules folder. Removing the virtual directory cleared this right up in my case. Took a long time to troubleshoot, so hopefully this helps someone avoid the wild goose chase.