WordPress has evolved from just being Blog-wear to a powerful Contact Management System (CMS) that’s very sophisticated, extremely user friendly.  It’s not perfect, like a double edge sword, it works both ways.  If you don’t take proper precautions and updates, then your software is subjected to vulnerabilities.  As long as you take the necessary security precautions by reducing risks and carry updated backups, you will have a very pleasant experience.

Also, some hosting companies offer cPanel access options to install these open source software easily!

If your requirements surpass the benefits of Shared Hosting, then perhaps it’s best you look into Virtual Private Servers (my personal choice) or Dedicated Servers, depending on your budget.  You can also setup accounts with wordpress.com, blogger.com, etc. for free and utilize what options they provide.

Anyhow, you can do use Google and research the pros and cons.

Resources

Hardening WordPress: http://codex.wordpress.org/Hardening_WordPress
Awesome wordpress security plugin WP Security & Firewall

The post Why Use WordPress As a Website or Blog? appeared first on My Web Development.

During my research, I figured this blog might of been my solution: http://wordpress.org/support/topic/redirections-to-127001-when-enabling-network
There was even a suggestion about the configuration within the nginx conf file and this did not resolve my issue; although, perhaps it might for you..

So many different suggestions regarding local host, yada, yada, none of the queries seemed to bring me much luck; until, I decided to revert my .htaccess in attempts this would work. YES, I was able to log back into my WordPress. After I reverted to previous .htaccess file, I was able to trouble shoot the issue and here is what I discovered.

Troubleshooting: WordPress 3.5+
My 127.0.0.1 Redirect Loop had to do with the plugin WP Security and the code it used inside .htaccess.

In WordPress, Dashboard; on the tool bar you will see option for WP Security > Firewall

WP Security > Firewall

If I enable the Basic Firewall Settings: fail
If I enable the WordPress Pingback Vulnerability Protection: fail

In either combination of enabling/disabling the above settings, no resolution was achieved.

So, with the Basic Firewall & Pingback Settings disabled, I troubleshooted ‘Brute Force Prevention’.

WP Security > Firewall > Brut Force Prevention: Enabled Brue Force attack Prevention & populated Secrete Word with the Re-Direcdt URL of http://127.0.0.1 (or where ever you want) and save (regenerating .htaccess file).

Conclusion

If you enabled WP Security plugin and in the Firewall options under Brute Force, you are provided a ‘secrete word’ as a login phrase; be sure you login into WordPress with the unique phrase or URL Brute Force provides.

So, instead of going to generic WordPress login: http://domain.com/wordpress/wp-admin
You would go to unique phrase WordPress login: http://domain.com/wordpress/?uniquephrase

And if that solution does not work for you, revert back to your old .htaccess file or copy the contents below and create your own .htaccess file & upload:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /wordpress/
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /wordpress/index.php [L]
</IfModule>

# END WordPress

Resources

Hardening WordPress: http://codex.wordpress.org/Hardening_WordPress
Redirecting loop occurs with .htaccess file: http://www.justincener.com/blog/how-to-easily-fix-the-wordpress-redirect-loop-error-without-admin-access/

The post Oops! Google Chrome Could Not Connect To 127.0.0.1 appeared first on My Web Development.

It’s best security practice to use a different username & nickname, than the generic ‘admin’ provided during install.

So, here is how you change the username after you install WordPress..

First Step

Access your phpMyAdmin, select the WordPress database find ‘table_user’ and select edit and change to your unique name, then save.

Final Step

Log back into your WordPress with your new user name.

There are other methods and plugins that will change WordPress username; check out the resource section for more information. Personally, the less plugins the better!

Resources

How can I change my default WordPress Admin Username: http://www.websitedefender.com/faq/change-default-wordpress-admin-username/
WordPress Change User Name: http://wordpress.org/support/topic/change-user-name

The post WordPress Usernames Cannot Be Changed appeared first on My Web Development.

WordPress Version 3.5+ allows multi-sites, so you can install WordPress in it’s own directory, powering the site from it’s root (http://example.com).
This method is cleaner, more secure way of archiving your WordPress.

Here are the steps I took, in Migrating WordPress.

NOTE: make any required backups before you perform any type of edits to your site. You will require a text editor, such as Notepad++ (preferred) to perform the following tasks.

First Step
downloaded WordPress 3.5+ and installed it in a desired directory /wordpress/ (e.g. http://example.com/wordpress/)

Second Step
Copy your index.php & .htaccess files to your root and perform the following edits to them.

Edit the index.php (line #17) file by including the directory where your WordPress resides.
Line# 17: require ( dirname( __FILE__ ) . ‘wordpress/wp-blog-header.php’ )

NOTE: do not include the / in front of wordpress (‘/wordpress/wp-..), otherwise it won’t work.

Third Step
Edit the .htaccess file you copied over to the root.
Remove the directory name /wordpress from the .htaccess: RewriteRule ./wordpress /index.php [L]

RewriteRule . /index.php [L]

Final Setp

Go to Dashboard > Settings > General and adjust the following: Site Address (URL) http://example.com/wordpress/ over to: http://example.com

Visitors can access your WordPress from the root directory (e.g. http://example.com). Log into dashboard will still direct to where wordpress core files are located: http://example.com/wordpress/wp-admin/

NOTE: I strongly suggest using All In One WordPress Security and Firewall Plugin and secure your login access and follow through recommended features.

Resources

WordPress Codex: http://codex.wordpress.org/Moving_WordPress
Ask WordPress Girl: http://askwpgirl.com/how-do-i-move-wordpress-from-a-subdirectory-to-the-root-directory/

The post Migrating WordPress for Multisite appeared first on My Web Development.

During development, it’s recommended to hide visibility, until ready for publications. However, the checkbox is always enabled upon installation, so most users forget that they are enabling the site to be viewable, when it’s not ready.  First impressions go a long way, same goes with users experience when they visit your site.

There has been some modifications to WordPress 3.5+ in where the option to discourage or enable Search Engine Visibility.

Log into your WordPress and go to Settings > Reading & there the options to enable or discourage is available.

Resources

How To Enable Site For Search Engine: http://wordpress.org/support/topic/how-to-enable-site-for-search-engine

The post WordPress Search Engine Visibility appeared first on My Web Development.

When you download the AdSense Deluxe plugin, only copy over the adsense-deluxe.php file to your plugins root directory (/wp-content/plugins). Also, in the file adsense-delux.php line 1085, change admin_head to admin_menu.

Activate plugin and enjoy!

Resources

AdSense Deluxe Quick Fix 1: http://ntmw.byethost13.com/fix-adsense-deluxe-wordpress-plugin-you-do-not-have-sufficient-permissions-to-access-this-page-error-for-wordpress-2-8-1/

The post AdSense Deluxe Permission Issue Error Solution appeared first on My Web Development.