Title: glcreative's Replies | WordPress.org

---

# glcreative

  [  ](https://wordpress.org/support/users/glcreative/)

 *   [Profile](https://wordpress.org/support/users/glcreative/)
 *   [Topics Started](https://wordpress.org/support/users/glcreative/topics/)
 *   [Replies Created](https://wordpress.org/support/users/glcreative/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/glcreative/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/glcreative/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/glcreative/engagements/)
 *   [Favorites](https://wordpress.org/support/users/glcreative/favorites/)

 Search replies:

## Forum Replies Created

Viewing 1 replies (of 1 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Slideshow] tekst slide in widget](https://wordpress.org/support/topic/tekst-slide-in-widget/)
 *  [glcreative](https://wordpress.org/support/users/glcreative/)
 * (@glcreative)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/tekst-slide-in-widget/#post-3133416)
 * The solution above worked for me but required a small tweak. My theme’s css applied
   a style to the H2 element that was over-riding the slideshow’s style. The theme
   style looked like this:
 *     ```
       #content h2 { color:#000; }
       ```
   
 * In order to get around it I had to add the “#content” selector to the slideshow
   declaration like this:
 *     ```
       #content .slideshow_container h2 {
       	margin: 5px;
       	font-size: 25px;
       	color:#fff;
       }
   
       #content .slideshow_container p {
       	margin: 7px;
       	font-size: 15px;
       	color:#fff;
       }
       ```
   
 * This gave the new declaration the “precedence” it needed to be picked up. The
   reason it wasn’t picked up before seems to be that ID declarations (“#”) in CSS
   take priority over class declarations (“.”).
 * **NOTE: this fix is NOT NECESSARY if your theme doesn’t have the “content” element
   and a matching declaration for h2. But, this does give you another avenue to 
   trouble shoot.**

Viewing 1 replies (of 1 total)