I'm trying to repeat table header on each page. On first page, It looks fine but on rest of the pages, the height of the header is decreased and most of the data is hidden as below.
How can I fix the height of the header to look same on all pages?
You can achieve your requirement using Aspose.Words. Please set the value of RowFormat.HeadingFormat property to true for header row.
I work with Aspose as Developer evangelist.
I'm able to fix it. Workaround is : Under Table Tools, on the Layout tab, in the Data group, click Repeat Header Rows.
This messed up my table.
i un-did this change and it is working as expected. lol
https://support.office.com/en-us/article/repeat-a-table-heading-on-subsequent-pages-2ff677e0-3150-464a-a283-fa52794b4b41
Related
I am using Sitecore 8.1 and Glass mapper ORM. In page editor mode, I have a link field which can be linked to news article page. The folder structure is
News/News article. News folder is of type Bucket and article is bucketable item.
When I am trying to insert link from other pages to the actual news article I am unable to find search box or expand items under news. Is there any way I can insert link to the news article? Appreciate any help! Thanks in advance.
You have 2 options:
In the content editor in the view ribbon you can enable "Buckets". This will make all bucket items visible again (the bucket is expanded and all folders and items can be seen in the tree). This setting is taken into account in the "insert link" window as well.
Use the search tab in the "insert link" window (normally you should have 3 tabs (link, media items, search). The search tab will let you find the bucketed items as well, but also others - it is not restricted to a bucket.
Edit:
After trying this myself, I noticed that if you edit the link field within the experience editor the search is indeed not provided (not even with the general link with search field). In the content editor the search is present.
A workaround is option1, or use an EditFrame. But I would contact Sitecore Support as well and ask them to add this - I'll do it too.
Edit2 : issue has just been registered as a bug. If you need a fix without waiting for a solution in a future version, you can ask Sitecore Support.
I created a custom section named Created/Updated in Sitecore 7 just below the default “Quick info” section as shown below:
Recently we migrated our project from Sitecore 7 to Sitecore 8 but “Created/Updated” section developed by us is no more looking like quick info of Sitecore 7.
The code is similar to Quick info default code used in Sitecore.Shell.Applications.ContentEditor.Pipelines.RenderContentEditor namespace in Sitecore.Client.dll
As shown above the fields present in “Created/Updated” are not looking like “Quick info” section. Instead, we can see a distinct table and rows for fields and width of these fields is less because of which entire time in Created Time field is not visible at the moment and it is getting cropped. I am not sure how it changed in Sitecore8 and how it can be switched back to the correct view like Quick info of Sitecore 7.
Instead of outputting <input> HTML in your second column, just do straight values.
You will need to change CSS for your custom component.
First of all, make sure first column has fixed width and second column has nowrap style set:
td:nth-of-type(1) { width: 110px; }
td { white-space: nowrap; }
This will make second column that contains info to occupy whole rest of space after first column.
Important: CSS order does matter; also you would prefix td from example above with selector of your parent container element for your custom panel (not to mess with rest of tables on a page).
Also, you'd probably want to remove borders, to have look and feel like Quick View section has, but from your post it is unclear which element makes borders, likely to be the same TD.
Hope this helps!
To enable horizontal scrollbars in a table I need to style the containing DIV with "overflow: auto", highlighted in blue.
I tried it with FireBug and got the desired result. Just can't figure out out how to put the setting into APEX.
Using the theme "Blue Responsive".
I've played with this a bit in Apex 4.2.2, it should work the same in 4.2.1 I think. That particular div doesn't come from any template but you can target it with some CSS.
In the page properties, for CSS Inline, I entered the following and it seemed to work:
#report_2583625959157728_catch {overflow:auto}
(I think I've transcribed the correct id from your screenshot - you may need to check)
Unfortunately this means you'd have to do this for each report in your application individually where you want the scrollbar to appear.
Note: I haven't tested this in IE, however - last time I was mucking around with scrolling areas I found it incredibly frustrating to get it working in IE without breaking other functionality in the region - especially for Interactive reports.
You can add to Region Header:
<div style="overflow:auto;">
and to Region Footer
</div>
You can also add your css line to a report region template, if you want the scrollbar to be added to each report.
Other wise you're better of putting the overflow on a class and add it to your application's stylesheet, eg:
.myClass {overflow:auto}
you get more flexibilty to style your region this way. You can add the class to your report by setting the region attributes to class="myClass".
Note that instead of "auto", you can also try to use the element option "scroll", check the w3schools docs: http://www.w3schools.com/cssref/pr_pos_overflow.asp
I was trying to move components in Page Editor mode , and below are the things I have done to achieve this :
Set Compatible rendering selected for the Sublayouts
Added placeholder settings and allowed controls for placeholders
But , when I was trying to move components, the DataSourceItems for the sublayouts are not changing , hence the content is not changing.
And , also sometime I am getting Field related errors if the fields are different in the DataSources.
Can someone please help me in this .
From your question, it sounds like you are trying to move a component from one placeholder to another in Page Editor. That does not affect the data source.
If instead you mean you are trying to personalize the experience by using rules to switch the data source within a sublayout, the steps you've taken won't allow for that. You need to add conditions to the sublayout in Page Editor to choose which data source you want to display.
If you are trying to have compatible renderings (different sublayouts) show for the same placeholder, that is something that is done by your step 1. This is only to help authors know what other sublayouts would be a good idea to put in that placeholder. It does not affect the data source.
When you add components, the datasource for them is not set automatically. You need to check if it's set and use Sitecore.Context.Item if it's not.
Not sure if that's what you mean..
As for field related errors, please post more details.
I have a few fields that I don't want to appear in the report. Is there a way to hide them completely (not even show the column header for these fields)?
I tried to create my own ISaveAction with the intent to filter out those fields before they get saved to the DB, but even if they don't appear in the AdaptedResultList that is sent to the DataManager.InsertForm the columns associated to these fields still appear in the reports.
Out of the box functionality, the answer is that if you mean one of the reports in the Form Reports area of WFFM, you most likely can, depending on the report. If you mean one of the reports that you can see a "Design" button on top when you view it, then you know that it's using the report that is configured in one of the .mrt files in your website directory in this path:
Website\sitecore modules\Shell\Web Forms for Marketers\Reports
Editing one of the reports by hitting the Design button will open up the Stimulsoft designer that is built in to Sitecore and you can make changes. You can also download one of the trial clients from the Stimulsoft website and open the .mrt files directly and edit them that way (the interface is WAY nicer than the built in Sitecore one).
A word of caution, however, BACK UP THE FILE FIRST!!! The Stimulsoft interface is picky and easy to break and it's got a learning curve. Once you figure out the basics though, removing a field is cake.