lilleulven

And here is their reply, for those who use the same plugin combination:
We use the custom field xyz_smap and set it to true (1) if a post is published.
The code used is,
add_post_meta($post_ID, “xyz_smap”, “1”); //when publishing a post

I’ll test taking its value out of the copy process next time I duplicate a post and will keep this post updated with the result as well.

Thank you ??
I will contact them and hopefully figure this out. And I shall keep this post updated with their reply should they give me the name of that field, so we can have some sort of solution even if they are not building a compatible version ??

Regards

Wiebke

Thank you so much for your help, @amboutwe ??
Found and removed the redirect and now the sitemap link works like a charm again.

Note to self: when looking for redirects just don’t search for the complete link…

You are using a Unicode character that is unsupported in your CSS here:
.main-navigation .menu-item-has-children > a::after {
content: ‘\F0D7’;
font-family: Lato;
position: absolute;
right: 1.125em;
top: 0.8125em;
}

If you replace the content: ‘\F0D7’ with a character from this list it should be displayed correctly. (You can leave the other content-lines with the same character or remove them, as they have no effect.)

Good luck

Wiebke

Hi @passiveinc

What I did, to improve the mobile view is the following addition to my Custom CSS (Customize -> Additional CSS, when you are looking at the blog and not the Dashboard)

@media (min-width: 768px) {
  .navbar-collapse {
 	  min-width: 768px !important;
   }
}
	
@media (max-width: 767px) and (min-width: 360px){
  .site-header{
	    height: 220px !important;
	  }
}

@media (max-width: 979px) and (min-width: 768px){
  .site-header{
	    height: 302px !important;
  }
}

@media (max-width: 1279px) and (min-width: 980px){
  .site-header{
	    height: 315px !important;
  }
}

That changes the size of the of the header to fit better for mobile devices (in my opinion). As you can see, I am using the @media-clause with different min- and max-width values, these address the different sizes of the displays, so you only need CSS and not some other miracle-tool to change the mobile vizualization.

Remove the site title from above the header image by adding this to the same Additional CSS:

.navbar-brand {
    display: none !important;
}

Change the font size for the site title in the header image by adding this (also to Additional CSS):

.site-title{
font-size: 16px; /*change the number of px to something you like*/
}

Hope this helps.

Regards

Wiebke / Lille Ulven

The expected RBRACE error is due to a typo in the first line of each example. Change the double {{ to a single { and it should work ??

#secondary .widget a:link {color:#0000ff;} /* unvisited link */
#secondary .widget a:visited {color:#ff4040;} /* visited link */
#secondary .widget a:hover {color:#8b2323;} /* mouse over link */

or

.entry-hearder .entry-title a:link
, #secondary .widget a:link {color:#0000ff;} /* unvisited link */
.entry-hearder .entry-title a:visited
, #secondary .widget a:visited {color:#ff4040;} /* visited link */
.entry-hearder .entry-title a:hover
, #secondary .widget a:hover {color:#8b2323;} /* mouse over link */

Hi andrewgj,

To change the link colors in the sidebar widges use
#secondary .widget a:link {{color:#0000ff;} /* unvisited link */
#secondary .widget a:visited {color:#ff4040;} /* visited link */
#secondary .widget a:hover {color:#8b2323;} /* mouse over link */

If you want to address the titles of your posts as well extend this to

.entry-hearder .entry-title a:link
, #secondary .widget a:link {{color:#0000ff;} /* unvisited link */
.entry-hearder .entry-title a:visited
, #secondary .widget a:visited {color:#ff4040;} /* visited link */
.entry-hearder .entry-title a:hover
, #secondary .widget a:hover {color:#8b2323;} /* mouse over link */

So basically you need the more specific targets defined so that the general a is not overwritten by more specific code in the themes CSS.

Good luck

Lille Ulven

Thanks for the fast workaround ??

You mean the link’s text color to change to that green tone of yours? (Not the alt-text that comes up above your link?)
If so you would need – if it should work on all links:

a:hover{
font-color:  #2dcb70;
}

If you want to address only specific links you could define a class:

.special-hover-color:hover{
font-color:  #2dcb70;
}

and then call that class in your a-tag as
<a class="special-hover-color" href...>

That should do the trick.

Good luck

Lille Ulven

In theory what should work is adding a css-clause, either to your child theme’s styles.css (if you have a child theme) or to the customizations css like this:

.col-md-9{
width: 75%;
}
.col-md-3{
width: 25%;
}

The value you specify should be greater than 75% for the .col-md-9 class, as this is the current standard value. Adding the width for .col-md-9 and .col-md-3 should give you 100%. So if you change the first to 80% you need to change the second to 20%, if you changed the first to 90% you would need the second to be at 10% (which seriously might not be wide enough for the widgets at all – not everybody has a 40″ screen ?? )

Good luck

Lille Ulven

Hi Ruben,
add this to your custom CSS code:

.archive-page-title{
display:none;
}

as a “quick and dirty fix”.
Another way of achieving the same goal would be to change the code that builds your sites to no longer put that text onto your site, but then you would have to create a child theme and find the proper place in the code, so this solution, while “not as nice”, should do the trick for now.

Good luck

Lille Ulven

But if the issue resurfaces, let us know, and we will be glad to continue helping you.

I will ??

You’re welcome for the support, and keep posting those wonderful pictures!

Thank you, @pmciano. I can promise some very good photos for the future indeed. When the Scottish Adventure finishes I will go on with photos & stories from Iceland and then (if I can manage to write something good up) there shall be Bulgaria next year.

Here comes Murphy’s law… I ran the troubleshooting mode with Jetpack and Photon activated and the feature-images showed as if nothing ever happened. So I turned off the troubleshooting mode, still having Jetpack and Photon activated…and the Featured images still show. I haven’t made any other changes to the plugins or their settings in the last four days – except for updating the troubleshooting plugin this morning.
Some sort of connection issues that lasted a little over a week?
I guess I will try again once the error occurs again – which hopefully is never in the first place.

Thanks for your help @pmciano.

Have a great Sunday!

Hi Mr. FFP ??

Yes, it looks like the source is the image CDN of Jetpack. Disabling Photon within Jetpack helped to get the Feature image up again. So this weekend I hope to run the plugin to debug my installation and then hopefully this can get a final fix so that I can use Photon again.

As for photo attribution: since I am the one to take those photos they all simply have a watermark ?? – not the nicest way of doing things, but…it works. And since most of the time the photos within the article link to the same gallery on my website, it should be able to find that one as well. But yea, visible image attributes for the featured image would be nice…Maybe I’ll just add a link in the footer of those posts directly to the photo in the future. Got to think about that one for a night or two.

Thank you so much for your help, @pmciano.
I’ll see to get the troubleshooting done latest during the weekend.