I got a problem when I put 2 instances of FckEditor to a page in dotnetnuke.
sometimes, I got empty text when I call the text property.
Anyone helps?
The empty Text property is usually caused by having the editor in an update panel (either explicitly or by turning on partial rendering for that control definition).
For those using the FCKEditor on their
dotnetnuke sites, I recommend updating
to the latest version, it fixes a
number of problems including multiple
instances on the same page. (something
you will need for the latest news
articles).
Source
Download the latest version of the FCKeditor provider.
Related
I am working on my first Episerver Project and I have come across a problem with the UI.
I have a block Type with a PROPERTY LIST property. However when I add more than five items you can't see them all in UI.
I have another 10 Rows I can't see....
Is this a bug in Episerver??
Sounds like the bug where the Episerver Forms addon restricted the height of the PropertyList editor.
It was fixed in Episerver.Forms version 4.4.1: Bug report
Perhaps this is the issue you're facing? If so, make sure to upgrade the site's NuGet packages.
I am stumped on this one. I am not sure if others are having the same issue.
In past versions, when I use the report wizard, one of the screens lets me choose the style (Slate, Forest...)
With my new setup the screen never appears and on the summary screen it says 'Style:Modern'
I tracked down the StyleTemplate.Xml, made a copy and changed 'Modern' to 'ModernTest'. Both in the Styles folder and the en folder. I have searched my c drive and these are the only two places this file exists.
EDIT: I had to change the label to 'ModernTest' not the name. Now 'ModernTest' is showing up in the summary. I still however do not get the chance to change styles.
I added a new style to see if the page only shows up if more than one is present but maybe since that one was from an older version it still only thinks there is one valid style so skips the selection page... I will try to replicate modern...
I am using VS2015 Version 14.0.25123.00 Update 2, SSDT Version 14.0.1601.5
Anyone else have the same issue?
EDIT: I copied an xml file from a previous version and now slate appears as the style. I guess the only problem is that the screen to select the style no longer shows up.
Because of some reasons I am not able to change the view of teaser of my content type using drupal's UI, so I have to immediately force drupal to show images of contents of one of my specific content types in teaser. So, Is there anyway to do it by editing a table of it's database or someone could give me a better idea?
Thanks in advance \M/
You can override the node's template files in the site's theme. A full description of Drupal theme overrides is a large topic, and is version specific but hopefully this is enough to get you started down the right path.
Drupal provides a series of naming suggestions for various templates you can use to override default behaviors (and your own code as well). In Drupal 7 would should be looking for node--[content-type-name]--teaser.tpl.php or node--[content-type-name].tpl.php and then add conditional for the various display modes.
See also: the Drupal community documentation on node.tpl.php
I'm using umbraco 4.7.1 and the Repetable Custom Content Pacakge. My questions are:
I see questions that are saying that this package is not compatible with umbraco 4.7.1, but it is working fine for me... is the package compatible with umbraco 4.7.1 ?
When should I choose repetable custom content over creating nodes of a certain datatype ? Which option is better for performance ?
Is it possible to index/include repetable fields in examine search ?
Thanks.
Repetable Custom Content
Repeatable custom content is very useful if the number of fields you have is small and they are logically part of the content node you are editing. By this I mean a collection of content that is part of the page you are editing. An example of which may be a list of links with a description, name etc.
Child nodes make most sense if the content is related but not necessarily part of the same page. Or if the content in question has lots of data. The trade off with child nodes is that they are slightly slower to add.
Another benefit of child nodes is that they are selectable and sharable amongst nodes easily. For instance a content panel that can be shared amongst pages.
There is no right or wrong way to use either nodes or repeatable content, however the main thing to consider is the ease of editing experience. As from a developer perspective it doesn't make much difference.
In terms of compatibility if you know that the package is working in a version of Umbraco that is not listed as compatible on the Package page on our.umbraco.org, then you can click the Report Compatibility link to indicate which version of Umbraco you have tested it with. This will ensure that the information is up to date.
It seems that due to ActiveX that Firefox can't display the print icon/button on the Report Viewer control in SQL Server Reporting services. Has anybody figured out a way to work around this or gotten this to work?
If it's not possible, does anybody know of a way to add a standard button that would trigger the print behavior on the report viewer control?
As you state, the print functionality is ActiveX, so it will not work in Firefox.
You could place a button in the "msrs-buttonHeaderBackground" div using a javascript button.
I found the div using the firebug firefox extension - it's great.
You could possibly find the other divs you'd like to hide and put them in a print style sheet, so they don't show up when going to print.
http://www.456bereastreet.com/archive/200709/how_to_create_an_unobtrusive_print_this_page_link_with_javascript/
I agree with the author that ctrl-p could simply be pressed for a similar result instead of adding a button - but the print style would still help in that.
You know what...I just realized something. You will not be able to print a page that is more than one page! Ouch.
I know this is a very old questions, but we came across this and chose the following solution.
We downloaded an IE Tab extension(this is one there are several more) for FireFox and then configured that extension to use IE to render the report server URL by default.
You could easily create a how-to web page,pdf, or maybe even create a dummy report that shows the instructions on how to do this to your end users and then you're all set.
So now every time the report server website is accessed it's being rendered in IE so the print button shows up. Every windows machine already has IE so no compatibility issue there, unless you're not using windows. :)
My best suggestion would be from within Firefox export it to PDF and then print it from your PDF viewer. In my experience this is a better way to print the reports anyway.
Hope that helps!