HELP ME please.
When I create a new section within the portfolio part of my Squarespace website, it is greyed out. See link below. I can still add content to the section. As you can see there is a 'BACK' button and variations of background with either an image or plain colour. But why is there a white/grey overlay on the section?
If I move the section up then the image gallery comes down into the second position, and has the grey overlay. So it seems it's the second section position which has the problem. If I create another section below the second one it's completely fine as well.
I hope this is an easy one to fix.
thanks! 🙂
https://www.regardsfromyourfuture.com/future-paintings/project-one-44zcm-57lgb-6glfy-p2f7c-nbdk9-76lc2-zh5z9
That is happening due to the following rule that is within your Custom CSS / CSS Editor:
.page-section:nth-child(2) {
background: #000 !important;
filter: opacity(30%);
}
That rule was likely written specifically for a different page, but was not written such that it only applies to said page. You'll want to examine your other pages to see if any page is benefiting from that rule, whereby the second section of the page has a lower opacity. If I were to guess, I'd say it's a section on a page that only has a background image with no content.
If there is no other page that benefits from the rule, you can simply delete it from your CSS.
On the other hand, if there is a page (or set of pages) that benefits from the rule, you would want to edit the rule so that it is specific to a single page (or set of pages) by adding the collection ID classes to the beginning of the rule.
Related
In PDF generators you can normally describe a bounding box where if there is overflow it goes to a new page and you can include the content that wrapped it again.
I'm trying to figure out how to elegantly do this in Wicked, since we have a new requirement to allow users to generate their own PDFs from HTML.
The layout is roughly as follows:
[ address / logo ]
[ list of items purchased ]
[ footer ]
All the regions are a fixed size. With a handful of items there is no issue. If there are more than will fit in the region designated for the items purchased it cannot overflow. It needs to generate a new page break and put the overflow items on the following page (with the same header and footer wrapper).
I'm not sure there is a way to get a div's overflow to paginate like that in CSS though. (Prawn can do it, but it doesn't accept HTML). I don't know that something is going to overflow until it's rendered too, just knowing the count of items isn't enough.
Webkit doesn't really have good support for page breaking. I found out from their own page: "The current page breaking algorithm of WebKit leaves much to be desired.
Basically webkit will render everything into one long page, and then cut it up
into pages. This means that if you have two columns of text where one is
vertically shifted by half a line. Then webkit will cut a line into to pieces
display the top half on one page. And the bottom half on another page. It will
also break image in two and so on. If you are using the patched version of QT
you can use the CSS page-break-inside property to remedy this somewhat. There is
no easy solution to this problem, until this is solved try organizing your HTML
documents such that it contains many lines on which pages can be cut cleanly."
Is there a way not to repeat a Migradoc header on every single page?
In my program I add an image to the header of my document as:
Section section = document.AddSection();
// Put a logo in the header
Image image = section.Headers.Primary.AddImage(#"C:\img\SmallLogo.png");
I would like the image to only appear on the first page of my document. However when the document spans multiple pages the image is added at the top of every single page.
How can I only add the image to the first page?
Header and Footer will be repeated on all pages of the section. It's a feature, not a bug.
To have the image only on the first page, you can use a "workaround" by setting a different header for the first page.
But IMHO the cleanest solution would be adding the image to the first page and not the header. This way it will only show once - on the first page where you want to have it.
BTW: Images are shapes and can be positioned anywhere on the page.
I removed the following fields from the "s4-titletext" cell using the Manage Content Regions in SPD:
PlaceHolderSiteName
PlaceHolderPageTitleInTitleArea
PlaceHolderPageDescription
And I added "SharePoint:SPLinkButton... Visible="False"
I have published this template and have set it as the Default Master. It displays fine but when I add a web part (not in SPD), I get the error "You must specify a value for this required field" and it will not let me add/remove the web part or change any list. What did I do wrong in my customization? I followed the instructions on this post. I used Option 2 to hide the words. The reason I removed the fields is because I want to stretch our banner across the whole page and I didn't want to leave the space where the bread crumb would have been. My "s4-titletext" area looks like the pictures on the top of the page, only banner is stretched all across the top of page. I can not add a link to my page due to it being on a private server. I have asked other SharePoint experts and they are stumped as well. Thank you for your help on this.
Instead of setting visible="false", getting hiding the control using a CSS class. Set the control's class to something like 'hiddenClass' and then define your class style.
.hiddenClass{display: none;}
Customizing SharePoint masterpages is a pain since they're so sensitive. You have to use this method when hiding a lot of the out of the box controls.
Some placeholders need to be on the master page, if you remove it it will cause errors in some of the scrips.
What I recommend to you is create a hidden div and inside of it put all the placeholder you want to hide, like the example bellow.
<div style="display:none">
<asp:ContentPlaceHolder ID="TitleZone" runat="server"></asp:ContentPlaceHolder>
<div>
the site that I'm working at is designed in a such way that CSS class is set for the tag on all the pages and the css classes used are different for all pages. Each page has common elements such as a header, a footer and a nav bar. I'd like to set up a single page template and include all common elements there but the body tag stands in the way. Is there a way to control a template from a content page? I know I can specify a code behind for content pages but i can't rely on content authors to enter it correctly each time they add a page. My current thinking is to set up multiple page template, one for each css class that is referenced in the body tag and put the common page elements into user controls. This is less than ideal because I will end up with lots of mostly identical templates and my user controls would not be editable easily. I guess I would have to use shared content items and such making the content authors hunt all over the site. I would have been much simpler to update the common header in a single page template.
Can someone please suggest a way?
I submitted a reply in the Sitefinity forums where you originally posted this, but just in case you check here first I'll ask the same question: how is the css class for body determined?
if it can be done programmatically you can use the code-behind of the Master Page for the template to set it so that it's handled automatically.
If this won't work, tell me more about how the css class is assigned and I will try to come up with an alternative.
hope this is helpful!
I had to create a custom menu for the template we chose as the links were supposed to be added over a image. I have a header image which is called in as a module. When I select mod_mainmenu, the menu shows over the header image. However when I disable the mod_mainmenu and select the custom html mod , they come below the header image.
I need it also to come as the menu. Which will resolve the issue.
www.diaryboard.com/ship
This is the link. Could someone help me on this.
Regards
Edward
The first problem I see is in your template.css file on line 672 -
height: 448pxx;
Fix this typo first. You could probably do without the absolute positioning for the logo, but the typo will probably make the page look right.