56

[Admin]

In reply to: Post Navigation at the bottom (neo)

#48970

.singular .post-nav {
	display: none;
}

[Admin]

In reply to: Image Alignment on Mobile Devices

#48965

Looks like it’s caused by Jetpack as you’re using the Jetpack tiled image gallery option. Try disabling that and see if it works for you?

[Admin]

In reply to: Post Navigation Arrows

#48964

That kind of modification will need to be done via custom programming in a child theme. With CSS, you’re restricted to only modifying the appearance, and not the function.

[Admin]

In reply to: Language support

#48958

The best and permanent solution is to contact the translation editor for your language, and ask them to review and approve the translations. Depending on the quality of the translation and the established guidelines for your language, they might request you to modify some of the translations.

You can find the list of translation editors at this link:
Brazilian Portuguese: https://make.wordpress.org/polyglots/teams/?locale=pt_BR

[Admin]

In reply to: Menu CSS

#48953

Copy and paste this code into Additional CSS:

@media (min-width: 768px){
	.navbar-nav {
		text-align: center;
		width: 100%;
	}
	.navbar .nav>li {
		display: inline-block;
		float: none;
	}
}

[Admin]

In reply to: Remove Title on selected pages

#48952

Try disabling your plugins temporarily to see if any of them is preventing your customisations from being saved and published.

[Admin]

In reply to: A few questions regarding Franz Josef theme and addons bundle

#48951

Hi Gendji,

To answer your question, we are currently pausing development on Franz Josef at the moment since much of our development time is focused on implementing new features for Graphene. We’ll still provide support and fixes for Franz Josef, but only for the critical and security bugs.

After the new features for Graphene are completed, we’ll be porting over much of the same code to Franz Josef, so in the end both themes will achieve feature parity, but serving the needs of different kinds of website. We expect to achieve this some time around the middle of this year.

Some of the features we’re working on for Graphene includes AMP implementation, full integration of WooCommerce and bbPress forum, more intuitive typography options, etc. These are completely new features so they do take quite significant amount of time and resources. As an example, we’ve just completed the bbPress forum integration, which required us to customise most of the default templates to achieve the desired result. We could take a shortcut and just do a light skinning of the default templates, but that would not do justice to everyone.

As for the new FontAwesome version, yes you can simply copy the new version over the current files being used in the theme. The next time we publish an update, you can be sure that we’ll include the latest version of FontAwesome and SiteOrigins plugin.

As for the SiteOrigins plugin, you can also install and activate the plugin separately. The theme will simply not load its own copy and just use the one you have installed.

[Admin]

In reply to: Unwanted side effects of the recent update to graphene v2

#48943

Actually, you won’t need to customize the theme to implement the above code. Just copy and paste to WP Admin > Appearance > Customizer > Additional CSS.

But yes, actually changing the headings to normal text is the better solution.

[Admin]

In reply to: Unwanted side effects of the recent update to graphene v2

#48940

Strange that other items were not affected, but they had much longer descriptions.
Maybe this happens only when the description is short.

Yes, the theme considers the length of the description before displaying it in the menu.

As for the headings, the sizing and bold styling were design decisions for emphasis. This is a common practice, both in print and on web. You will rarely find the heading has the same size as normal text, anywhere.

The sizing of h1 to h6 were also determined so that h6 is smaller than h5, which is smaller than h4, etc, with h6 still being at least similar size with normal text. If this is detrimental to your content appearance, you’re probably using the headings in context that they are not meant to be used for. As an example, in your front page even the list is using h3 whereas they should just use normal text, with bold if you need emphasis.

Some other good practices guidelines include:

• Only one h1 per page. This is normally reserved for the most important heading on the page, which is typically the site title on home page, and the page/post title on other posts and pages.
• h1 to h6 is in decreasing importance. For example, h1 for the post title, h2 for sections in the content, h3 for category in the section, etc.

The above is not merely theoretical – search engines take this into account when scoring and ranking your pages.

Given all that, if you would still like to adjust the sizing of the headings, you can use this code in Additional CSS:

h1,
.h1 {
  font-size: 36px;
}
h2,
.h2 {
  font-size: 30px;
}
h3,
.h3 {
  font-size: 24px;
}
h4,
.h4 {
  font-size: 18px;
}
h5,
.h5 {
  font-size: 14px;
}
h6,
.h6 {
  font-size: 12px;
}

[Admin]

In reply to: Image won't display

#48938

Something on the site is modifying the sizes of the images to zero width and height when viewed on desktop. Can you try disabling lazy load feature from Jetpack? If that doesn’t solve it, try disable Photon as well just to confirm.