A regression in DotNetNuke 6 is that, by default, the editor appears in an in-page popup that uses a very limited portion of the screen.
While the editor does include the ability to go "full screen", this is not the default.
Is there a setting some place that I can adjust to cause it to always start full screen, or at least start out larger so that I don't have to scroll down to hit the save button?
One method for getting rid of this limited in-screen popup is to disable popups site-wide in the site settings (admin menu).
This will cause a full page load when the edit content button is clicked. The editing will be perform on a self-contained page. Clicking save will return the editor back to the page whose module is being edited.
Warning - Using this option will cause bulleted lists to not display as bulleted lists in design view within the default html editor
Related
I have an AngualarJS app that has an index page and some partial pages, displayed in ui-view. The app is using ui-routing. I have a button on the header (located on the index page) and on click of that button I want a small pop up open - a page displaying some data from the database, based on currently logged in user. I am trying to decide between opening a windows with window.open and sizing it to about 400x400 but that seems very un-elegant plus I see some issues with opening it. Another option I am entertaining is bootstrap ui modal but that would involve including bootstrap in my project on top of all the angular and routing includes.
Not sure if there is a better way to go, would appreciate any leads.
If you don't want to include bootstrap in your project You may use this one
--> http://www.dwmkerr.com/the-only-angularjs-modal-service-youll-ever-need/
I wrote an ExtJS application like this:
the sub menu is dynamic added by clicking the button on the left.
The question is :
as the sub panel is created dynamically, so if I refresh the whole page, the panel will go away.
What I expected is it could still display the same content before refresh pages.
So, my question is how to handle this in ExtJS?
Do I need to record the current panel information into Ext.App?
ExtJS is a framework to build Web Applications that run inside the browser.
With Web Applications, just like normal applications, you don't close the program and start it anew (like a browser refresh does) just because someone wants to switch to a different toolbar or look at different data. You work with multiple panels, switch between them, and/or open windows.
You could for instance generate multiple panels inside a container with card layout, and bring to front the panel that you want to show right now.
If you have a license that allows you to use Sencha Architect, there is a nice "navigation" sample available in Architect from where you can start and look at how it's done.
I'm running a dotnetnuke project (v7.0) with 2 portals.
I need to remove the default DDR menu from one page only.
The menu works great now with multiple pages and sub-pages, however on 1 specific page , ie landing page, I don't want to show the menu.
Right now I can think of 2 methods for achieving this:
Create a new skin template, remove menu, apply template to that one page
Use jquery to detect URL, for that page hide menu.
I'd rather just code the logic inside the template file, but I'm not strong in .net/c# and I'm new to DNN.
It's just one page today.
However, if you are using it for a landing page design I would recommend you just create another skin and exclude it from that and tailor that skin for that need.
That way when your non-technical editors need to work on the site and make a page that might only be used when linking from Google Adwords or whatever they can pick a template without that navigation and you as the developer/designer don't need to edit the skin to put in another exception based on the URL.
I have a normal article page with a huge image shown as a small one. What i want to do is, when the user click on the image, a new page is rendered and the image is shown at full size of the page (no menus, header, footer, etc.. just page). If the user click again, he will be redirected to the previous page.
How can i do this with joomla? I mean, i could create an html page, but i don't know how can i access it.
Any help would be appreciated,
RR
All you need to do is add this to any link you want to display without all of the module positions -
?tmpl=component
This tells Joomla to load just the component part of the page without anything else around it.
Not sure that anything specifically in Joomla is going to allow you to do that. The only way you can achieve that directly in Joomla would be using a light box type of plugin. When the user clicks the image, it will open up a full size window of the image. When the user click on the image again, it will exit the light box.
Otherwise, you can just edit the source code of the page, and change it to <img src="http://www.pathroyourimage.com/image.png"> . That way when a user clicks the image, they go directly to the picture.
We are using tab control in our project. While using this control i came across a few issues like
- When the tab control loads, it invokes constructor of all the xaml pages that form the individual tabs. Can this be avoided?
Is there any event with tab control that we can use to identify dirty data on the previous tab that i may have visited. I mean can i prevent user from navigating to some other tab before saving the changes on current tab.
You should be able to avoid the instantiation of each xaml page in the individual tabs by adding the content to the tabs dynamically, right before they are shown for the first time. You might be able to get away with doing this on the tab control's SelectionChanged event.
The tab control does not have a dirty state management. At best, you individual containers/pages will have to handle the dirty state.
I mean can i prevent user
from navigating to some other tab
before saving the changes on current
tab.
I don't think you can prevent it. We have something similar in our app and the route we have chosen is if the page is validated then the Tabs becomes enabled so they can either click save or navigate to a different tab. In case they navigate to a different tab without clicking on save we will perform save for them. I think as a user perspective this is a good thing!