WordPress.com is an easy way to start blogging. Get a blog, check out our features, read the latest announcements, choose from great themes, or learn about the team behind it.
Need help? Check out our Support site, then
Hi all.
I am using template Duet and I have a slideshow at my HOME page and I want to have it without background color and no borders. I upgrade my template by purchasing the $30 package that includes (fonts/color/css).
I applied a few codes that I have read on several forums but none of these seem to work.
Can you please provide me the code and where to put it?
Thank you very much.
Yiannis
The blog I need help with is kairoschoir.com.
To remove the background color and border from the WordPress.com slideshow feature, add this to your Appearance → Custom Design → CSS editor:
kairosadmin
div.slideshow-window {
background-color: #fff;
border: 0;
}Hi designsimply and thank you for your response!
I applied your code in my css editor but unfortunately it didn't work.
I previewed it, saved the stylesheet but nothing changed..
Thanks anyway!
You entered this:
.slideshow-window
But it needs to be this:
div.slideshow-window
Try adding the "div" part at the beginning.
Sorry I got back to you a bit late but I am working in several tasks these days. It worked and Thank you so much... The reason that I didn't include the div. text was the wordpress. They were marking with red color the "div." text and a message on the screen was saying the div. is overqualified and I thought it wouldn't work. Thank you so much for insisting on that!!! If a new question comes up can I ask you again directly to this forum?
Best,
Yiannis
By the way, I just created a post called Staff and I want to replace the page called staff because I want to apply the "read more" option and I know that works only with posts. I went to the post's code and I added: <!--more--) to the point where I want the text's break but it still shows all the text
Any help:)
The reason that I didn't include the div. text was the wordpress. They were marking with red color the "div." text and a message on the screen was saying the div. is overqualified and I thought it wouldn't work.
Ah, yes. That warning must be ignored in this case because of how CSS specificity works. I think the warning notes are great, but sometimes you do need to go against them to make things work with the other CSS that' gets loaded by WordPress.com themes.
If a new question comes up can I ask you again directly to this forum?
If you have new questions about CSS, you should make a separate, new help request at http://en.forums.wordpress.com/forum/css-customization/#postform
I went to the post's code and I added: <!--more--) to the point where I want the text's break but it still shows all the text.
The more tag doesn't change anything for a post by itself, only when the post is displayed in a list of posts. You currently don't have a "blog" or "posts" section setup to display a list of posts.
If you're not going to setup a blog on your site or use a "posts page," then you probably want to use pagination instead of a more tag. Try switching back to using a page and follow this instead:
http://en.support.wordpress.com/splitting-content/nextpage/
Thank you designsimply, this is great but it doesn't give the option of read more. I mean it breaks the page but doesn't leave any link to the rest of the content.
I really appreciate all the help you have already provided to me.
With the pagination option, the link to the rest of the content should appear as page numbers. It shouldn't make it so there is no link at all to the rest of the content. If that is happening, please post a link to an example where I can check it out.
It sounds like your goal is to add a "read more" link to an individual post or page, and there's not a built-in option to do that within WordPress itself (unless you count the pagination feature). However, perhaps you can do something else such as create a duplicate page or sub-page and then add a "read more" link manually to the first page and point that link to the new page.
This topic has been closed to new replies.
