mrhugzzz

Cais,

I’m sorry too as I was very satisfied with NextGen and had created quite a few galleries on my website which I now have to redo.
Unfortunately, I needed to find a solution right away as I started a new campaign which was having a lot of downloads and I couldn’t respond to each one individually or risk losing a customer because of Social Media messaging about troubles with the downloads.
If there is a fix for this, please let me know and I will be happy to reinstall and use NextGen.
Steve

Cais,

I had the latest version of NextGen and still had the issue. It was actually my Host service tech department that tracked down the issue as I would never have gone that route.
I tested it myself and had others test it as well with a free file download I had on my site. In all instances, when NextGen was active, the downloads didn’t work. When it was disabled, no problems.
I have since deleted NextGen and am now using the Jetpack gallery plugin with no problems at all.

I’ve found the problem – it’s because of the NextGen Gallery plugin by photocrati.

When I disable it, everything works!

Okay, I will. Thanks.

I’ve just taken it off of the Stylesheet Editor and the tags have reappeared on the blog post …

Here is the code I have in the child stylesheet css …

/*
Theme Name: Twenty Thirteen Child
Theme URI: https://scentimentalcreations.com/twenty-thirteen-child/
Description: Twenty Thirteen Child Theme
Author: Steve Malcolm
Author URI: https://ittakesballstoknit.com
Template: twentythirteen
Version: 1.0.0
*/

@import url(“../twentythirteen/style.css”);

.site {
background-color: #f2c38f;
}

.site-main .widget-area{
float: right;
background-color: #f2c38f;
width: 150px;
}

.widget .widget-title {
font: 300 italic 14px “Source Sans Pro”, Helvetica, sans-serif;
margin: 0 0 10px;
}

.site-header {
text-align: center;
}

#horiz-wid-line div {
display: inline-block; background-color: none;
}
/*.my_border {
border:3px red solid!important;
}

.col_3 {
background-color: #ff0000;
}*/

body .tags-links, body .categories-links {
display: none;
}

——
It’s still there at the very bottom … when I follow the link you show it doesn’t show up … where did you get that link?

Yes.

When I added it to the style.css it didn’t work …

Andrew, that doesn’t work. I’m attaching my Child Theme code …

/*
 Theme Name:     Twenty Thirteen Child
 Theme URI:      https://scentimentalcreations.com/twenty-thirteen-child/
 Description:    Twenty Thirteen Child Theme
 Author:         Steve Malcolm
 Author URI:     https://ittakesballstoknit.com
 Template:       twentythirteen
 Version:        1.0.0
*/

@import url("../twentythirteen/style.css");

.site {
background-color: #f2c38f;
}

.site-main .widget-area{
       float: right;
       background-color: #f2c38f;
       width: 150px;
}

.widget .widget-title {
	font: 300 italic 14px "Source Sans Pro", Helvetica, sans-serif;
	margin: 0 0 10px;
}

.site-header {
    text-align: center;
}

#horiz-wid-line div {
    display: inline-block; background-color: none;
}
/*.my_border {
border:3px red solid!important;
}

.col_3 {
background-color: #ff0000;
}*/

body .tags-links, body .categories-links {
  display: none;
}

As I said before, I also have an Edit CSS tab under the Appearance Tab in my dashboard. When I put the code there, it works. My concern is that I don’t know whether or not that code will be overwritten with the next upgrade of Twenty Thirteen. My understanding was that I had to create a child theme to make any permanent changes to Twenty Thirteen. Here is the code I have in the Edit CSS box that comes up …

html {
	background-color: #f37405;
}

/*
Shop nav
*/
#text-4 {
	position: relative;
	top: -95px;
/*background-color: hsla(60,100%,50%,.15);*/
}

.shop_nav li ul li {
	padding: 0;
}

.shop_nav li a {
/*	background: #0c9ba0;*/
	color: #FFF;
	display: block;
}

.shop_nav li a:hover {
	background: rgba(117,33,175,.1);
	border-radius: 9px 9px 0 0;
}

.shop_nav li:hover ul li a {
	background: rgba(117,33,175,.9);
	background: linear-gradient(to bottom,rgba(210,195,218,1) 0%,rgba(139,53,180,1) 52%,rgba(70,111,217,1) 100%);
/* W3C */
	box-shadow: inset 0 0 10px black, 0 5px 8px hsla(0,100%,0%,.6);
	border-radius: 0;
	font-weight: bold;
	text-transform: capitalize;
	color: rgb(240,240,240);
	font-size: 1.15em;
}

.shop_nav li:hover ul li:first-child a {
	border-radius: 27px 27px 0 0;
	color: rgb(255,240,240);
}

.shop_nav li:hover ul li:first-child a {
	color: rgb(255,210,210);
}

.shop_nav li:hover ul li:last-child a {
	border-radius: 0 0 5px 5px;
}

.shop_nav li:hover ul li a:hover {
	background: #f99c32;
	color: white;
}

.shop_nav li {
	position: relative;
}

.shop_nav li ul {
	display: none;
	position: absolute;
	min-width: 140px;
	right: -20px;
}

.shop_nav li ul li a {
	padding: 10px 12px;
}

.shop_nav li:hover > ul {
	display: block;
}

/* footer positions */
.col_1 {
	position: relative;
	top: -30px;
}

.col_2 {
	float: right;
	position: relative;
	right: -500px;
	top: -170px;
}

.col_2 p.phone {
	line-height: 1.1em;
}

/* end footer positions */
/*
Welcome to Custom CSS!

CSS (Cascading Style Sheets) is a kind of code that tells the browser how
to render a web page. You may delete these comments and get started with
your customizations.

By default, your stylesheet will be loaded after the theme stylesheets,
which means that your rules can take precedence and override the theme CSS
rules. Just write here what you want to change, you don't need to copy all
your theme's stylesheet content.
*/

In essence, this Editor is taking the place of my Child Theme …

I’ve fixed it. On my dashboard I have a Stylesheet Editor and when I placed it there it worked. I’ll have to delve into this some more.

I don’t think all of my child theme is getting read – I know that sounds strange. When I put that code in using firebug it works, but it doesn’t in the child theme???

I tried that but it doesn’t work. Not sure why …

Thanks Andrew! I use the developer tools as well and am self taught, but after an entire day of trying to figure this out (tried numerous things) I threw in the towel.
I am using a child theme – have to for this kind of stuff – and had issues with my cache not clearing so I couldn’t see the changes I implemented.
This worked brilliantly though, thank you very much!

This has been fixed. Thanks.

Thanks.

Thanks guys, I can see it now.
Hugzzz ??