I am using DNN7.
I have added a HTML module on my DNN7 site which needs to displayed on all the pages except admin pages.So i configured in settings of the module which said display module on all pages.But the problem i am facing is when i check this option to display on all pages the module is getting displayed on admin pages too which i don't require.*Is their any option to disable the module on admin pages and show only site pages.*Please help.
Thanks,
I don't think there is such an option. You just have to remove it manually from the admin pages you mostly use
Related
I have a Joomla website here and when you click on an article from the homepage it stills displays all of the home page modules. I went thru the settings for each module, and it is set to display only on the home menu page. I go to the menu setting that the articles are under and the settings stated the modules are published but not displayed. Any help would be appreciated!
I discovered the issue was due to a category error. The category is supposed to auto create a page for itself, however, it did not happen for whatever reason. So I had to delete the category and then make the category again and everything was fine. The reason the home page modules were appearing on articles is because that's the default behavior of Joomla when it can not find a specific page.
I use the angular-fullstack/generator-angular-fullstack for my project and for testing purpose I would like to run my project on two different browser windows.
The problem is that I got the same input for each text field on both browsers simultaneously.
For example:
On the login page, if I type my email address on one browser it will appear on the login email field in the other browser.
Any ideas of what I'm doing wrong?
Your project uses browserSync.
When your project is opened using localhost:3000, you should browse to localhost:3001 that will give you a BrowserSync configuration page.
Under Sync Options on that page you can disbable what to sync.
I have deployed dnn6.2.6
After logging in as admin/host user - when am in any page ( that too in EDIT mode - dropdown ) am not able to see the MANAGE Icon. :(
Is there any value to be set or enable any setting , in-order to make this facility enable after installing ?
where am missing ?
Please suggest
Rigin
I would start by looking for any javascript errors on the page. It is likely something is throwing a JS error earlier on and killing the icons on modules later in the page.
Do you have a custom skin, or any custom modules being loaded on the page?
Does it function different for an Admin or Host account?
My issue was :
Site Mgmt > edit site setting <<=== more need to configure site here
&
Add module > add "HTML editor" Module to that Page
Rigin
I had an link in my DNN site Menu - pointing to aspx page of my installed module.
I replaced this link with an external link.
And now i wish to change back to old one - aspx from module. BUT am not getting that listed in the dropdown
How to get that back or I missed anything ? I could found the module still in that EXTENSIONS.
Please suggest
Rigin
I think you may be a little confused,
Modules are placed on pages, (One or mor module generally makes up a page.
Menu links refer to pages,
To add a module to a menu it must be on a page.
Once you have placed you module on a page you can select it from the select a web page drop down
A dnn module got 2 pages a view page and a settings page. So you must be sure that your module start's with the correct page.
So what you want is not possible the way you want it.
Best way for you is to control the page in your module. You can control this with for example a user controls(ascx). See image for a default module view.
I write a standalone aspx file and upload it to DNN website. I add a html module and make an iframe to that aspx file. How I should check DNN user login or not in aspx file? I think there are something in Session but it is empty when I print it out on aspx page.
The aspx file executes outside of DNN. There is no context for you to work with. A much better approach is to turn your .aspx into a .ascx and derive from PortalModuleBase as the start of a DNN module. You can add a proper module to the page and permission the module as you see fit and DNN will take care of all the authentication and authorization details for you.
A starting point for module development
I don't recommend it in this situation, but you can also emulate the approach I described for getting context in a web service.
https://stackoverflow.com/a/9164573/51851
If your aspx is within DNN's website you can simply use Request.IsAuthenticated to check if user is logged in or not.
But be warned, if you have friendly URL turned on - DNN 5x and above will hijack you aspx request.