How we can change text and wording of "Terms of Use" and "Privacy Statement" pages in Dot Net Nuke from admin?
Those texts are part of the resources files.
Go to menu "Admin > Languages" and click for edit its content for the site or the host.
Keep on the edition of the "GlobalResources" file.
Search for "MESSAGE_PORTAL_PRIVACY.Text" and "MESSAGE_PORTAL_TERMS.Text" and modify them.
If you modify the system version, a future upgrade of your DNN installation could overwrite your customization.
Host mode will impact all websites on the instance.
Site mode will impact only the current website.
I know this is old, but it might still help someone:
Tested with DNN 08.00.04 there are different methods to get a custom terms page without editing the language files (which feels a bit cumbersome)
To have your own /terms page you just create named "terms" in the navigation root.
DNN will show up your newly created page if you browse yoursite.com/terms
You can also redirect to another page from there (create a "link" page instead of "content" page, this in case you want to call your page AGB and have this in the url (yoursite.com/agb)
If you have https://dnnurlmanagement.codeplex.com/ installed you can simplifiy the steps above with just adding a "custom page URL" 301 redirect rule with "/terms" to any page you want to show up as /terms.
Go to site admin section here Admin -> Language -> edit host -> find your required field "Terms of use" and "Privacy". you can change here or edit it.
Related
I installed a 2sxc version 11.11.3 Inside a fresh dnn 9.3.2.
After this I created a content Module with the simple test view inside. After this I granted this module the edit permission to the Registered Users Group on dnn module Level.
If I log in as a registered user I can see the 2sxc toolbar (blue symbols when hovering the item of the module) of the Module and the items. If I press the edit icon I get the Message "had an Error Talking with the Server (Status 403)".
Has anyone an idea what I am doing wrong?
Thank you very much
Robert
Edit1
The browser console shows following content in the ERROR object:
error: "Permission denied. required permissions for this request are not given"
headers: t
lazyInit: ƒ ()
lazyUpdate: null
normalizedNames: Map(0) {}
__proto__: Object
message: "Http failure response for https://.../api/2sxc/cms/edit/load?appId=2: 403 OK"
name: "HttpErrorResponse"
ok: false
status: 403
statusText: "OK"
url: "https://.../api/2sxc/cms/edit/load?appId=2"
Edit2
After this I wanted to explore, if the behavior is 2sxc Content module related or if it is related to all apps (in my understanding the 2sxc Content module is an app too). I installed the "FAQ" app, granted the dnn "Edit" permission to the "Registered users" group and logged in as a registered user and pressed the edit icon on the 2scx toolbar - and had the same behavior like described in the origin post.
But: I got it running for the "FAQ" app, but not for the "Content" app. Here are my steps to get it running for the "FAQ" app:
click on "Apps management" (available in the dnn edit action or in the 2sxc toolbar)
"Features" - add feature - enable "Permission by Group / Role" - Activate feature
"Apps" - "FAQ" (or another except Content)
"App" - "App Permissions" (click on the icon) - "create new permission" - Identity=xx (xx=RoleId of the Group in table dbo.Roles) - Grant=Edit (in my case I want that the current registered user is able to edit an item) - Save (Ctrl+S)
After this I was able to edit the item of the "FAQ" module.
The "App Permissions" icon is disabled by default for the "Content" module on App level (and on view and data level too). Does anyone know if this is by design or is there a possibility to activate this option? Otherwise I have to migrate my content views to an app to get the permissions running.
Edit3
I ended up by migrating the content of the "Content" app to a new custom app. The effort is very less and getting the possibility to grant permissions was worth doing it.
In a conclusion I'll answer my question by myself. I suppose that the "Content" app has not the possibility granting the dedicated permissions. But the app itself has the posibility - so it could be a good idea, to create content inside an app.
Just some background: The content-app is meant for simple content and behaves differently from normal apps. Example:
when you add a content-app, the dialog asks for you to choose what content-type, and what view
when you add an app, the dialog asks you for which app, and then what view
Basically the content-app has various optimizations to make it lighter and simpler, but we wanted to prevent people from "shooting themselves in the foot" because they will usually start with content, and then make it increasingly complex (never separating different concerns) and end up with a big mess.
This is why the content-app has some forced limitations (like no app-permissions) to guide people to place more complex functionality in own apps.
Now note that this doesn't explain your original issue: apparently edit-permissions didn't work as expected. That seems to be a bug, not an intension. If you think that should be followed up, best create an issue on github.
We recently upgraded one of our client sites to 09.01.01 to address a Telerik vulnerability, and then had to migrate the site from managed.com to Azure due to manage.com's outage. After the upgrade, a couple of pages on the site have been uneditable using the pencil icon in the persona bar, although the rest work fine. We're aware of the workaround of going into content > pages and clicking the pencil icon there, but even then not all of the areas on the page are editable. For example, there's one instance of the HTML module on the homepage where when you click on its pencil and then click "Edit Content," it just displays a pop-up with the text but no WYSIWYG or way to actually edit. Other instances of the HTML module work fine, on other pages and even other areas of the homepage.
What's more bizarre is that we just spun up another Azure VM and created a dev site from a clone of the live site so we could troubleshoot further, and this problem does NOT occur on that site even though it's an exact copy of the live site files and database and both sites are hosted in Azure.
Does anyone have advice on what might be causing this or how to troubleshoot? My original though was to clone the page and start removing modules one by one to see if anything made a difference, but it doesn't actually remove the module when I click delete. I've read about ways to do this directly in the database, but I'd prefer to avoid that if possible, especially since we're not seeing the same problem on the cloned site.
Thank you!
Could you please see if any error appearing on the logs folder? You can see the logs here. /Portals/_default/logs/2021.02.01.log.resources? The log file name may differ based on website's logging configuration.
A similar thing can be seen from the Personal bar as well using Admin Logs.
I have a dev box running with a namespace and just added a demo visualforce page named "test" and just clicked on "Preview". It is ending up with a certificate error on my browser.
The URL salesforce tries to open is https://myinstance-dev-dev--mynamespace.visualforce.com/apex/test
The certificate being provided by this domain is for "viv1.force.com". That is why my browser is blocking it.
Any idea why this is happening? My visualforce pages were working on the dev box, but now suddenly end up with this error.
Strange solution. Had to check "Critical updates" on setup, and DEACTIVATED the setting "Stabilize URLs for Visualforce, Experience Builder, Site.com Studio, and Content Files". Now it is working again.
I assume for some reason this stabilization missed to change the used certificate behind visualforce pages. Deactivating above option fixed it.
Above is the ribbonbar after I have logged in as a super user. The Admin option next to Host is completely gone
The site is running DNN6, the skin is only in the site portal folder, and it seems that all admin modules and options have gone away. Even the header, which I set in Site Settings (under Admin), went away!
Has anyone else had their admin options completely disappear on them? Is it possible that the skin is messing it up (all other sites use the same _default menu files and they work fine)?
Thanks for any replies.
We've recently had this exact situation occur in one of our DNN sites. It turn out that one of the site's administrators had accidentally renamed the Admin page from within the "Page Management" section (it's easy to see how that could happen). The fix was to go directly to /Admin/Pages.aspx and change the "Page Name" back to "Admin" ... and it will show up in the ribbon bar again.
As a suggestion to DNN developers, I would recommend making the Admin page and its subpages impossible to rename....
Can you check the database to see if those pages exist? What if you try to navigate to http://website/admin.aspx do you see the admin page and all the child pages there?
Can we create a content managed master page in dotnetnuke?
eg. I want the right pane and bottom pane to be content managed, but to show the same thing across all pages.
Thanks
What you are describing is essentially what DNN calls a Skin.
A DNN skin is actually just an ASP.NET user control (ascx) that dictates page-wide or site-wide look and feel, which offers developers the same functionality as a Master page, except that it ties into DNN-specific elements and uses some DNN-specific user controls, such as menu/navigation, logo, breadcrumbs, login/user account links, etc.
Now, in order to add the ability to provide content management capabilities site-wide, you specify an area in your skin to place a module (let's say, a Text/HTML module). This area is called a pane. Once you add a module to this pane, in its settings you can tell it to appear on every page. This way, the module can be edited on any page, and its changes will be reflected on all pages automatically.
Check out DNN's site, as it contains a TON of documentation on how to do many common tasks: http://www.dotnetnuke.com/Support/Documentation/DownloadableFiles/tabid/478/Default.aspx. Under the Technical Documentation section, you'll want to grab the Skinning document (I believe it's a PDF).
DNN Modules can be set to appear on all pages by checking a checkbox in the module settings. However DNN does not use the concept of a Master Page. It injects modules (user controls) in containers on a single aspx page at runtime.
A Master Page would be a great addition to DotNetNuke you cannot replace content in a single area of the page. The whole page refreshes. For example if you have a menu and you only want the content of what you select to appear in a specific content area without refreshing the rest of the page you have to resort to third party modules that attempt to do that but usually fail. There are 'module wrappers' but all the ones I've tested have issues with modules that allow the user to edit content. Edit screens are usualy different user control files (ascx) that are launched when you edit the module content. Since the page refreshes with the new page you have lost your place. Those module wrappers work fine for static content and some other controls but not for all controls.
IFrames can be used (DNN has one) to trade out content but that doesn't get rid of the probelms mentione above. I'm heavily invested in DNN, running the UCanUse.com web site so this isn't a slam on DNN. I just thought I'd try to answer the quesiton with detail.