Custom Login Page Link

This is the link and link title on the login page.

along with some code snippets on how to handle this:

http://premium.wpmudev.org/forums/topic/remove-wp-about-menu-from-toolbar#post-161711

There are a few options. First the manual edits:
Open the file:
/wp-includes/class-wp-admin-bar.php
And around line 456:

456

add_action( 'admin_bar_menu', 'wp_admin_bar_wp_menu', 10 );

Comment it out or just remove the whole line. Now the WP links part is all gone!
But….. But……… If you wanted to edit those links to customise yourself, you could just go open up the file:
/wp-includes/admin-bar.php
You’ll see it all near the top, here is a short snippet:

if ( is_user_logged_in() ) {
// Add "About WordPress" link	 $wp_admin_bar->add_menu( array('parent' => 'wp-logo', 'id' => 'about',	 'title'  => __('About WordPress'),	 'href'   => admin_url('about.php'),	 ) );
}

You will note much of the same on there.
The logo is part of a sprite which can be found here:

/wp-includes/images/admin-bar-sprite.png

Both of these options mean updating the code every time you upgrade your WP install.
And now the final option, which is the easiest, but its yet another plugin………

Remove WordPress Admin Bar Links

Enjoy, its free!!

Well if you don’t see the WordPress Admin Bar on the front end then it is likely your theme is missing two functions:

<?php wp_head(); ?>

<?php wp_footer(); ?>

The CSS for the admin bar is loaded through the wp_head() function and the navigation is pulled through the wp_footer() function.

wp_footer() should be added just before your HTML closing body tag and is used by plugins usually for such things as add Java.

<?php wp_footer(); ?>
</body>
</html>

wp_header() should be called just before the closing your HTML head code and is used for things like CSS, Meta data and so on. If you use script in your head and have java there, that may need to be written after the wp_header() function is called.

<?php wp_head(); ?>
</head>

Well this quick set of pointers should help you out!

Log into your PHPMyAdmin or what ever you are using to edit your database.

1. Find the table “_users”.
2. Edit the row where the “user_login” column is equal to “admin”. Change the admin part to what ever is your desired user name.
3. Also edit the row where “user_nicename” column is equal to “admin” (same as above) Change this to your desired “nice” name (no spaces or such) – This is also used within BuddyPress for the profile link and @admin.
4. BuddyPress users will want to change their profile where it echoes out “admin”, this is located in the table “_bp_xprofile_data”.

Now you will most doubt have done all that but now can’t find the “Network Admin” link and section, well you need to edit one more thing:

5. Open the table “_sitemeta” There is a row “site_admins” with data under the column “meta-data”, it will look like this:

a:1:{i:0;s:5:"admin";}

You will want to change this including the number 5 which is the character count of your username, so in my instance it will look like this:

a:1:{i:0;s:3:"tim";}

Save and test it out, that should fix the issue for you.

Please note: There could well be other instances in the database on a multisite install, I haven’t thoroughly checked. I only worked through this to help another user find a solution, this worked for me and then worked for them. Always make a backup of your database first!

Hopefully this should help someone out there!

First of all if you are runing a vanilla install of WordPress you will have no doubt noticed that when system e-mails are sent out that the address is usually wordpress@yourdomain.com and of course you could most likely find a plugin to combat this but is a another plugin bloating your install really what you need?

So, where can you change this in the core code?

/wp-include/pluggable.php

Around line 391:

391

$from_email = 'wordpress@' . $sitename;

Around line 1057:

1057

$wp_email = 'wordpress@' . preg_replace('#^www\.#', '', strtolower($_SERVER['SERVER_NAME']));

So that is the default out of the way!

Now you are running BuddyPress and you notice that your “Contact Form 7″ or Supporter form is sending out e-mails with a sent address from noreply@yourdomain.com, of course this is damn annoying, it makes it more time consuming when you make replies, often you send an e-mail to yours noreply address and then get angry clients asking why you haven’t contacted them back, or if you use a support desk so you can’t just reply to that ticket. Its most annoying when all you need to do is reply yes or no and especially so when using the supporter form for your clients.

So the problem! It is actually buddypress causing the issue here. At least in 1.2.8 (Not checked other versions) You see it ads filters to the default WP_Mail function forcing its own headers. What you need to do is remove those filters and everything will be back working as it should.

Contact Form 7, Add the following:

remove_filter('wp_mail_from', 'bp_core_email_from_address_filter' );
remove_filter('wp_mail_from_name', 'bp_core_email_from_name_filter');

In the compose_and_send_mail() function around line 693:

693
694
695
696
697
698

	function compose_and_send_mail( $mail_template ) {
 
		remove_filter('wp_mail_from', 'bp_core_email_from_address_filter' );
		remove_filter('wp_mail_from_name', 'bp_core_email_from_name_filter');
 
		$regex = '/\[\s*([a-zA-Z_][0-9a-zA-Z:._-]*)\s*\]/';

Now it will use what ever you stipulate in the admin area of Contact 7 which is usually the e-mail address for the person contacting you!

And the WPMUDEV Supporter plugin, open the following:

/wp-content/mu-plugins/supporter-premium-support.php

Add it to the supporter_support_page() function which is approx. line 94 it should then look like this:

94
95
96
97
98

function supporter_support_page() {
  global $current_user;
 
	remove_filter('wp_mail_from', 'bp_core_email_from_address_filter' );
	remove_filter('wp_mail_from_name', 'bp_core_email_from_name_filter');

You could if you wished wrap it up in some conditional statements to check for BuddPress first, but for me it is always installed, at least for now!

If you are not using BuddyPress or you still have this issue after removing the filters then chances are there is another plugin or even theme which is forcing its use of the wp_mail() function.

Note: One thing to remember is that making changes directly to the main files of WP, a plugin or theme means that when you come to upgrade you will need to remember to make those changes again! I prefer this over bloating an install with plugin after plugin.

http://forums.winamp.com/showthread.php?p=2747002

They were recently hacked and now your details may have been exposed.

Winamp Management Team — On February 11, we discovered that the Winamp Forums (forums.winamp.com) servers were compromised, resulting in a security breach where Winamp Forums users’ email addresses and passwords may have been compromised.

We understand how important trust is, and we’re deeply sorry for and embarrassed about this breach of security. We immediately closed the exploit that led to this compromise and we’re working around the clock to ensure our security moving forward. We’re also committed to communicating openly with you to make sure you understand what has happened, how it may or may not affect you, and what we’ve done to fix things. If you are a registered Winamp Forums user, you should have received an email from us notifying you that your account may have been compromised.

We have confirmed that this attack was isolated to the Winamp Forum (forums.winamp.com) site only. Other Winamp sites and products such as Winamp.com, dev.winamp.com and the Winamp Desktop Media player were not affected in any way.

We have prepared the following FAQ for questions you may have about this incident. If you have additional questions please feel free to contact us at support@winamp.com.

1) How do I know if my password was hacked?

If you’ve registered an account on the Winamp Forums (forums.winamp.com), then it’s best to assume that your username and password were included among the compromised data.

Passwords in our database are encrypted (i.e., not stored in plain text), but they may still be vulnerable to hackers. You should immediately change the password on your account, and if you used that password on any other web site, you should change your passwords on all of those accounts as well.

2) What data was exposed in this breach?

We have confirmed that your email address was exposed as a result of this attack. We have not confirmed but must assume that other Winamp forums user account detail, including your forums username, date of birth, time zone preference and password hash (not your clear text password).

3) Should I be concerned about my other online accounts? What if I used that password on other sites?

If you used your Winamp Forums (forums.winamp.com) password on any other web sites, you should change the password on those sites as well, particularly if you used the same username or email with that site. To be safe, however, you should change the password on those accounts whether or not you were using the same username. We’ve put together a guide to help you audit and change your passwords.

4) How can I delete my account?

We understand how important trust is on the web, and some of you may wish to delete your Winamp Forums account. To delete your account make sure that you are logged into the Winamp Forums and follow these simple instructions:

Scroll down to the bottom of the forum home page and click on ‘View Forum Leaders’. Scroll down to the Root section to see the list of Administrators. Send your deletion request to DJ Egg or DrO using the contact link to the right of the administrator’s name. The Administrator will delete your account upon receiving the private request message.

5) How do I change my password?

You can change your password in your “User Control Panel” settings. Log in to your account, click the “User Control Panel” in the Forum Nav, then click “Edit Email & Password” under “Settings & Options” Enter your old password and your new password, re-enter to confirm new password and click “Save Changes.” Your password will be updated. You can also change the email associated to your Winamp Forums account on the same screen.

6) What if I forgot my Winamp Forums password?

On the Login screen attempt to log in once, after you fail one login you will see “Forgot your password? Click here!”. Enter the email associated to your account and text/numbers in the image verification box (aka Captcha). You will be sent an email at that address that will reset your password. Follow the link you will be taken back to Winamp Forums and another email will be sent to the same account. Use that username and temporary password to login. You can reset your password now by going to the User Control Panel. See instructions in #5 above.

7) Who was responsible for the security breach? How did it happen?

Our security team was able to identify and block access to the application flaw which resulted in this breach. The application was patched and new security measures have been deployed to keep this type of breach from happening in the future.

How are you notifying those whose details were compromised?

We are in the process of notifying all users with a registered account for the Winamp Forums via email. Please feel free to forward these FAQs to anyone you know who uses Winamp Forums. We can also be reached at support@winamp.com

9) What are you doing to ensure this doesn’t happen in the future?

The security team has introduced new web application protections and monitoring processes to detect abusive activity.

10) What should I do now?

You should change your password as soon as possible, both on the Winamp Forums and on any other site where you use that password.

11) When did you discover the breach had occurred?

We discovered the breach on Feb. 11. We actively monitor Winamp Forums and all Winamp products via a rigid security plan and software that alerts us whenever there are attempts to breach that security. Those processes alerted us of this breach and we reacted within 24 hours and shut down the exploit.

12) I received an email from “Winamp” on February 15, was that from you?

Yes, we sent an email on February 15 to all Winamp Forums users informing them of this breach and asking them to reset their passwords for the Winamp Forums and any accounts where they use the same email and/or password. The subject was “Winamp Forums Security Notification” and the body of that email was as follows:

Hello,
My name is Geno Yoham and I am the General Manager of Winamp. First, thank you for your support of Winamp. The Winamp Team is dedicated to providing you with the best possible media player experience so it gives us great pain to share that we have recently experienced a security breach of our user forums database.

We have confirmed that your email address was exposed as a result of this attack. We have not proven but must assume that other Winamp Forums user account detail which includes your forums username, date of birth, time zone preference and encrypted password (not your clear text or unencrypted password) was exposed. We have secured our Winamp Forums application and we would like to notify you of the incident and ask you to immediately change your password as a precautionary measure. If you have used your Winamp forums password across other web sites, please change the password on those web sites as well.

We apologize for any inconvenience this has caused and want to assure you that we are taking every possible step to ensure that your data and personal information remains secure as a part of our ongoing commitment to protecting your privacy.

If you have any questions or would like to speak to someone at Winamp for more information about your account, please contact:support@winamp.com. We have also set up an FAQ at forums.winamp.com for questions you may have related to this incident.

Best,
Geno Yoham
Winamp

13) What can I do if I’m receiving spam because my email was leaked?

You can take steps on your own to wipe out spam from your inbox, but you’ve also got legal recourse.

The CAN-SPAM Act of 2003 allows for private right of actions against spammers. If you receive any spam in your inbox that you believe is related to your leaked email address, please report it to the Federal Trade Commission. Send a copy of unwanted or deceptive messages tospam@uce.gov. The FTC uses the unsolicited emails stored in this database to pursue law enforcement actions against people who send deceptive spam email. For additional information, please visit the FTC’s website. Note, you should not respond to a spam email. By doing so, you confirm that your email account is active, and you’ll likely be flooded with more spam.

I was asked by various Facebook friends, and people within the new Facebook groups (updated version of groups) how to turn off their automated e-mails letting them know of every post and update made. Rather than repeating myself I thought I would knock up a quick tutorial, here it is.

If you are not sure how to go from Mylinks to imLinks, its pretty easy.

First grab yourself a copy if WF-Links 1.06 from http://members.chello.nl/rengelsman/mcdstore.html and upgrade to that, there is an update script with instructions in the read me. Once done then download the latest version of imLinks, you can get this from the ImpressCMS addons website. Again there is instructions on how to upgrade from WF-Links from the read me.

Now, I don’t know why but after updating the module as instructed to do through the read me and auto updater I find that in the database there are a ton of empty screen shot fields which generates a dead image on the front end for your viewing public. This is because the script detects a blank space and tries to parse it as a link to a screen shot image. To fix this just log into phpMyAdmin and run the following MySQL code

UPDATE `DATABASE_NAME`.`PREFIX_imlinks_links` SET `screenshot` = '' WHERE `PREFIX_imlinks_links`.`screenshot` = ' ';

Don’t forget to change the DATABASE_NAME to that of your own and the table PREFIX to the one you use in your database. Once done and run you will find no Screen shot column has this space and thus the problem is solved. Simples!

As I said, I don’t know why it happened for me, perhaps something in the good ole days, maybe the upgrade itself which I doubt but still possible but if it happens for anyone else, then here is your fix!

Thank to McDonald for making the awesome imLinks what it is today!

Anyway, so if you’ve already overwritten your files with the new upgrade and your presented with a white screen or you having bodged upgrades then chances are its a module. First of all make sure you have a back up of your installation (which you should have from before the white screen and upgrade issues), reinstate your database to the back up (the bodged upgrade could have altered the tables). Log into your PHPMyAdmin or equivalent and then run this MySQL code.

Update table_modules SET isactive = '0' WHERE isactive = '1'

Make sure that this “table_modules” is changed to your table, so if its “mysite_modules” then put that other wise this won’t work.

MySQL Disable ICMS And Xoops Modules

Hit the go button and now all your active modules will be deactivated, now try your website and upgrade, hopefully this might have solved the issue for you. If it does, then only activate your modules one by one to find out which one was the trouble causer.

Why should I change the generator of my WordPress install?

WordPress, your themes and many plugins like to display the version number of your installation, this is a great way to let a potential hacker or cracker know if your using an insecure and buggy version and even though whilst your installing WordPress it may seem secure, at a later date a vulnerability may be found. Personally because of this I don’t like to display those details, Google maybe your friend along with other search engines, but remember they don’t only help you find sites.

Anyway, I digress again!

Open /wp-includes/general-template.php

Around line 2202 you will find a PHP switch with the following code:

2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224

switch ( $type ) {
	case 'html':
		$gen = '<meta name="generator" content="WordPress ' . get_bloginfo( 'version' ) . '">';
		break;
	case 'xhtml':
		$gen = '<meta name="generator" content="WordPress ' . get_bloginfo( 'version' ) . '" />';
		break;
	case 'atom':
		$gen = '<generator uri="http://wordpress.org/" version="' . get_bloginfo_rss( 'version' ) . '">WordPress</generator>';
		break;
	case 'rss2':
		$gen = '<generator>http://wordpress.org/?v=' . get_bloginfo_rss( 'version' ) . '</generator>';
		break;
	case 'rdf':
		$gen = '<admin:generatorAgent rdf:resource="http://wordpress.org/?v=' . get_bloginfo_rss( 'version' ) . '" />';
		break;
	case 'comment':
		$gen = '<!-- generator="WordPress/' . get_bloginfo( 'version' ) . '" -->';
		break;
	case 'export':
		$gen = '<!-- generator="WordPress/' . get_bloginfo_rss('version') . '" created="'. date('Y-m-d H:i') . '"-->';
		break;
	}

Basically a switch tests a case and if it matches it executes the cases code, so if your on a HTML page you will execute the part located in the case ‘html’:

2202
2203
2204

case 'html':
	$gen = '<meta name="generator" content="WordPress ' . get_bloginfo( 'version' ) . '">';
	break;

You don’t really need to understand that to be honest, just change the relevant parts, your end result should look like the following:

2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224

switch ( $type ) {
	case 'html':
		$gen = '<meta name="generator" content="SJBNetwork">';
		break;
	case 'xhtml':
		$gen = '<meta name="generator" content="SJBNetwork" />';
		break;
	case 'atom':
		$gen = '<generator uri="http://sjbowers.net/" version="na">SJBNetwork</generator>';
		break;
	case 'rss2':
		$gen = '<generator>http://sjbowers.net</generator>';
		break;
	case 'rdf':
		$gen = '<admin:generatorAgent rdf:resource="http://sjbowers.net" />';
		break;
	case 'comment':
		$gen = '<!-- generator="SJBNetwork" -->';
		break;
	case 'export':
		$gen = '<!-- generator="SJBNetwork" created="'. date('Y-m-d H:i') . '"-->';
		break;
	}

Now if your running a WordPress multisite you won’t have to add a new function to every theme on your install, but keep in mind that some themes do add the generator meta tags themselves.

Remember though that when you update your WordPress installation that will need to make this change again.

If you do the above, you don’t need to do the next part to change the displayed generator in your theme.

If you are looking for the other option of adding a php function to your theme then open your themes folder, locate functions.php and add:

2202

remove_action('wp_head', 'wp_generator');

Make sure this is encased in php tags.