I'm trying to use the Authentication.Federated module to enable ADFS support for Orchard. I installed the module by downloading it locally and adding it, and I enabled the module. Now, according to the instructions, I should see the Federated authentication settings under the general "Settings" menu in the Orchard dashboard, but they are not there. What's missing?
I'm running locally, if that's relevant, and I had Orchard setup its own local database when I started it the first time
EDIT: Tried installing from Gallery; same thing.
EDIT2: Looks like the logs show this:
Orchard.Environment.Extensions.ExtensionManager - No suitable loader found for extension "Authentication.Federated"
Looks like the dynamic loader doesn't like Authentication.Federated, but the settings show up if you include the project in the solution.
Related
I am trying to write a custom plugin for hawtio 2.x.
The first step that I tried building the entire project (https://github.com/hawtio/hawtio) as instructed in https://github.com/hawtio/hawtio/blob/master/BUILDING.md
Later, I tried the example (springboot sample) located at https://github.com/hawtio/hawtio/tree/master/examples/springboot
The example seems to run fine, except for the fact that I do not see a trace of the sample plugin written in this application (https://github.com/hawtio/hawtio/blob/master/examples/springboot/src/main/webapp/app/sample-plugin/js/sample-plugin.js)
Right now, I am not trying to do fancy stuffs. I am simply trying to run this sample application and see how the plugin works.
Below is the screenshot of the web console. I have also checked in the browser console. I do not see any traces of the initialization of this plugin.
Am I missing something specific?
I am trying to uninstall the Designer Tools, but, when I Uninstall, I get a 404 on /Packaging/PackagingServices/UninstallModule. Is there a way to get that UninstallModule?
In Orchard 1.x, uninstalling a module is as simple as deleting its folder under the modules directory. Before you do that, however, disable it just to check the site still runs without it, and also check in the modules admin page what other modules depend on it. In the case of designer tools you should be fine.
Another solution if you want to keep the convenience of debugging easily on your dev boxes but keep your deployed version secure is to modify your deployment procedure to exclude specific modules.
docdokuplm
Hi !
Just checking out your PLM, looks great! I followed your instructions:
https://github.com/docdoku/docdoku-plm/wiki/Installation-Guide
I used the nightly build.
After uploading the ear file and then using http://localhost:8080 I see the Payara server page. Was there something else I need todo or where do I start to troubleshoot? Thoughts?
Thank you!
The page displayed at 8080 is the default landing page. If you have deployed the DocDokuPLM application and configured the settings detailed within the instructions, you can open the application through Payara Server. Go to Applications -> DocDokuPLM -> Launch, and you'll get a series of links which should help you troubleshoot.
If you can't see any, run through the installation procedure again to ensure that you haven't missed a step - it seems like there's a few steps which must be configured exactly correctly for the application to work.
According to this GitHub issue, this seems like a bug with DocDokuPLM. As with most software, nightly builds are inherently risky. Looking at the source, though, it seems that the code changes fairly rarely, so you might try with the previous version of Payara Server (173), though the stack traces in the GitHub issue don't look to me like an issue with Payara.
The backend server and the UI are two separated components.
If you want to install the User Interface you have to go there :
https://github.com/docdoku/docdoku-web-front
The project which you have deployed is just for backend,inorder to interact with UI just clone the web-client from this repo https://github.com/docdoku/docdoku-web-front and in command prompt use this command npm run dev then you can use this project, make sure the port number which is mentioned in app/webapp.properties.json of web-client project is same as you have given in server-config.
Read https://github.com/docdoku/docdoku-web-front/wiki/Development-Guide for more details
I recently created an Orchard CMS instance on MS Azure. I wanted to add some modules but I am getting the error (within the module page):
Error loading extensions from gallery source 'Orchard Gallery'. Unable
to connect to the remote server.
I'm not familiar enough with Azure to be able to diagnose what is going wrong. I've seen some pages that say that this is by design. If so, then I can just install modules manually. But if this has ever been changed and this is indeed an issue then, does anyone know a) what the issue is or b) how to go about diagnosing it?
Thanks!
What is the version of your Orchard CMS instance? (see bottom right in admin)
Check on the Gallery setting page (/Packaging/Gallery/Sources) that the url of the default feed is https://gallery.orchardproject.net/api/FeedService
I am working on orchard CMS (version 1.8.1) sites with multiple language, I found this one (https://github.com/qt1/orchard_contrib-RM.Localization) is useful, and I would like to add this to my site, but failed to work (I just copied it into, but picker widget cannot be found in dashboard), may someone know how to do and give me some advice?
Regards,
David
If you want to use this module in you Orchard app, you need to add it the the Orchard.sln and compile the application - then the module will be visible in Modules section of the dashboard.
You can also try using an existing package from the Orchard Gallery
Download a package
Go to Modules, and enable Packaging module
Go to Modules -> Installed and click Install a module from your computer
Browse the package and click Install
Now enable the installed module