Syahir Hakim
KeymasterKuala Lumpur, Malaysia
When not perched on my workspace, I tremendously enjoy hiking in the bushes and climbing mountains. They serve as much-needed refuges from the pretense of cities.
Forum Replies Created
-
Admin
I just did something like this for one of my clients the other day.
Two things you need to do. First, add this code to your child theme’s functions.php file:
<?php
/**
* Make slider posts clickable
*/
function graphene_clickable_slider(){
?>
<a href="<?php global $post; echo get_permalink( $post->ID ); ?>" class="slider-link"></a>
<?php
}
add_action( 'graphene_before_sliderpost', 'graphene_clickable_slider' );
?>Then, add this into your child theme’s style.css file or the Custom CSS option:
.slider-link {
height: 100%;
left: 0;
position: absolute;
top: 0;
width: 100%;
z-index: 10;
display: block;
}`
OK, this will be fixed soon!
Hi danr,
Firstly, let me explain a bit how the Graphene theme development goes.
1. The developers (2 developers, in case of the Graphene theme) write the codes and make changes/updates to the theme.
2. The developers then uploaded the updated theme to the Google Code project hosting for the theme. Only the authorised developers have the permission to do this. In this case, it’s only me and one other developer, Jeffrey Tummers.
3. The theme then goes into a public beta period, which lasted anywhere from a few days to a few weeks, depending on how major the changeset is. A number of volunteers test the theme, and translators update their translations. Any issues found during this beta testing period are fixed almost immediately after being reported.
4. The theme is then submitted to the official WordPress.org theme repository. A member of the WordPress.org Theme Review Team will then review the theme and the changes made. Note that this happens everytime before an update is published. The reviewer that reviews the theme is independent and not related to the Graphene theme.
5. Only after the theme passes the review which checks for a heck lot of things will the theme update be published and made online on the WordPress.org official theme repository.
So you see, there’s a lot of checks being done between the development process and the stage when the theme’s updates are published, by a lot of people. The full history of changes made to the theme’s codes are publicly available on the theme’s Google Code Project Hosting page. If anyone has malicious intent with your site, you can be pretty certain that it is not us.
That being said, there’s a lot of ways that a site can be compromised, one of which is via insecurities in the codes. We’ve made significant efforts in later versions of the theme to harden its security, but as with all software developments there’s always a possibility of a security hole somewhere that we are not aware of. If somebody finds one and point it to us, we’ll be more than happy to plug it.
But the theme is only part of the codes that make up your site, and a small part at that. Your site could have been compromised in a myriad of ways, including those that do not involve vulnerabilities in the codes at all. This can include improper server configuration, sharing of server resources, etc. In fact, if it’s really the theme that contains the vulnerability that causes your site to be compromised, many of the tens of thousands of the theme users would have similar issues. But they don’t.
So really, the best way to go about it is to try do a complete reinstall of your site. Back up the database, change all the passwords (including the FTP and server admin panel passwords), wipe out all the script files, and then reinstall WordPress, the theme, and other plugins that you have again. Then notify Google to let them do a review of your site again.
I know it can be frustrating when things like this happens, but it does. We’re not living in an ideal world, and people with malicious intents do exist. So your best option would be to just stay cool and ride it out. If we can help in any way that is within our constrained time and ability, we’d be happy to.
Add this to the Custom CSS:
.home .posts-nav {
display: none;
}The theme added an additional layer of customisability for the site’s title. You can see the function definition for the
graphene_title()function in the functions.php file.I am not sure how the Yoast SEO plugin would use the
wp_title()function, but my guest would be that it somehow attaches a filter to that function which modifies the site’s title based on the page.The theme uses the
wp_title()function as well for generating the titles of all pages except the front page. You can try using the plugin first without changing anything, and see how it works out.Otherwise, you can simply override the
graphene_title()function by placing this code in your child theme’s functions.php file:<?php
function graphene_title(){
wp_title( '' );
}
?>You’re welcome 🙂
Does this happen every time you went to the General tab? I can’t seem to reproduce it on my end.
Add this to the Custom CSS option:
.home .recent-posts,
.home .latest-post {
display: none;
}Hmm..that’s weird..can you try resetting the options and set it again?
Hmm..can’t switch the location as of now. But you can simply hide the list of recent posts, and let only the list of posts by categories to be displayed.
