309

[Admin]

In reply to: How can i have two columns on the homepage (without static page) ?

#29403

Post the link to your site so we can take a look.

[Admin]

In reply to: Show secondary menu only on a specific page

#29775

This will hide the secondary menu in all pages:

#secondary-menu-wrap {

display: none;

}

And this will display it only on selected pages:

.page-id-2 #secondary-menu-wrap,

.page-id-3 #secondary-menu-wrap {

display: block;

}

[Admin]

In reply to: Hiding some posts

#29715

Quote:

I’ve left the new theme-slider words in there. Is that correct?

That should be fine.

[Admin]

In reply to: Modifying Comments Form

#29621

Sorry, there was syntax error in the code I posted earlier. I’ve corrected it, so try again now.

[Admin]

In reply to: How to remove HTML tag under comment form ?

#29730

Graphene Options > Display > Comments Display Options

[Admin]

In reply to: Remove WordPress version from Graphene files!

#29750

Quote:

I notice that WordPress version is explicitly mentionned in Graphene theme folders! I removed it from WordPress files but it still displayed in Graphene!

Those are mostly comments, or specific version numbers that needed testing. They don’t reveal which version of WordPress your site is running.

Quote:

This is a huge drawback for the security of WP-based websites. Most WP-based websites and blogs are hacked continuously because of suh information rendered available for hackers and malicious people.

It’s a bad idea to let hackers know which version, theme, plugins or tools are used in a website. They could expoloit it easily and hack people. As those information offer valuable source as opened door for them.

As long as you’re using the latest version of WordPress, plugins, and themes, this shouldn’t be much of an issue. There’s really no way you can prevent somebody from determining the WordPress version you’re running. I can, for example, compare the loaded jQuery on your site with the ones included in every WordPress releases to determine which WordPress version you’re using. So you see, it’s not that they don’t want to hide the version number, but that it’s simply a futile effort.

But ultimately, it doesn’t matter. Security should be built into the codes, not achieved by hiding codes. WordPress has a WP-Hackers list exactly for discussing this sort of issue, among others. Any discovered security vulnerability is usually reported to the WordPress core dev, and security patch release will quickly follow.

Quote:

Also, hide Graphene theme version, too?

Not possible. The version number is in the theme’s stylesheet, which is used by WordPress to determine what version the theme is, so that it can properly check for updates, etc.

But like I said, it doesn’t matter. You’re really nitpicking on the small stuffs with little possible gain, if any. You should be more concerned with your server setup, regardless of whether you’re on a shared hosting or a private hosting. You should also be more concerned with what plugins you’re using and how secure they are.

Most plugin and theme developers do their best to eliminate any security vulnerabilities in their code, but it’s not a perfect world, and it never will be. The best everyone can do is to report any vulnerabilities they find, and usually the developers will be more than happy to release a fix quickly. The WordPress community is very accommodating when it comes to security fixes. For example, if somebody reported to me about security vulnerability in the Graphene theme, I can release an update within a matter of hours, instead of a few days or even weeks sometimes for standard theme updates to be approved.

[Admin]

In reply to: Hiding some posts

#29712

That’s weird. I’ve got it working on my end. Perhaps there’s some other files need updating as well.

Anyways, you can remove it by adding this code to either the Custom CSS option or the child theme’s style.css file:

.single .post-nav {

display: none;

}

[Admin]

In reply to: Modifying Comments Form

#29618

Quote:

Are you saying that there’s a way of putting the code somewhere in the child theme that will then alter the code in the comments.php file without me actually having to go into the comments.php file?

Yes. Try inserting this code into your child theme’s functions.php file:

function graphene_custom_comment_form_args( $args ){



$args['must_log_in'] = 'You must be <a href="http://somewhere.to/go">logged in</a> to post a comment.';



return $args;

}

add_filter( 'graphene_comment_form_args', 'graphene_custom_comment_form_args' );

[Admin]

In reply to: Problem with hover menu in IE (I know…)

#29737

Yes, that code is from the theme, but it’s taken straight from Google Webfont Loader for the webfonts. In any case, I don’t think that’s what causing the dropdown menu to not appear.

I’ve tested the theme in IE7-IE9. IE7 and IE8 throw that error you mentioned, but I’m using IETester for this – native IE browsers typically don’t show these errors. Regardless, the dropdown menu still works ine IE7-IE9, despite the error.

The menu dropdown issue has probably got something to do with z-index bug in IE.

[Admin]

In reply to: Inegration of phpBB into Graphene theme?

#29720

No, because all the functions used in the theme files are defined in the WordPress files, which isn’t loaded in phpBB. Instead, I copy the generated HTML when you view the page in the WordPress site.