RewriteEngine On
RewriteCond %{HTTP_HOST} ^[^.]+\.[^.]+$
RewriteCond %{HTTPS}s ^on(s)|
RewriteRule ^ http%1://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

So if you visit mydomain.com it will redirect to http://www.mydomain.com
If you visit https://mydomain.com it will redirect you https://www.mydomain.com
If you visit subdomain.mydomain.com it will NOT redirect you to http://www.subdomain.mydomain.com

Pretty cool right? I hope this can help someone else out as well.

• Download the Free IonCube Loaders for your PC (machine), by choosing your OS platform. You can download them from HERE
• After you have downloaded it, extract that zip pack to your wamp folder directly. So, that it becomes like this, C:\wamp\ioncube
• Edit php.ini file: C:\wamp\bin\apache\Apache2.2.11\bin\php.ini and add this line at the bottom of the last line: zend_extension_ts = “C:\wamp\ioncube\ioncube_loader_win_5.2.dll”
• Restart WAMP and you are done.

Now, if you want to test,if you IonCube has successfully got installed and set on your server environment, then here is a way to test. Just goto your Joomla Site Admin backend. Goto HELP > SYSTEM INFO > PHP INFORMATION. Scroll down there and you should see something like this:

You can also create a simple php_info.php file.  Simply create a new PHP file and place the following code in it and run it by placing it into your c:\wamp\www\ folder.

Its actually quite simple to do this.  Let’s work through a simple example.

Suppose you were working with a website that sells flower arrangements.  Lets say you have a table called flowers which contains two fields: ID, flower_name  This table may contain flowers like:  carnations and roses.  Let’s also assume that you have a second table called colors which includes two fields: flower_id, color  Since a roses come in many different colors the person who is placing the order on the website will need to be able to select which color he/she wants.

Table flowers

    - ID

    - flower_name

Table colors

    - ID

    - flower_ID

    - color

If you were to do a standard SELECT query on the flowers table you wouldn’t know which colors were available.

SELECT
   *
FROM
   flowers

The above query would simply return all of the flower name and their associated id numbers.  As you can see I placed the select statement on several lines.  The reason I do this is to make it easier to read. Sure in this simple example it may not seem logical, but when you start building larger and more complex query statements it make it a lot easier when you return to your code at a later time, or if someone else has to read your code.

Let’s take a look at how to setup the query to JOIN both the flowers and colors table:

SELECT
   *
FROM
  flowers
JOIN
   colors
ON
    colors.flower_ID=flowers.ID

Let’s break this down.  We start off easily by selecting every record within the flowers table.  Next after the JOIN operator, we state which table we want to join with.  In this case its the “colors” table.  Next comes the most difficult part…After the ON operator, we state which columns the tables should join.  Since every color has a reference to a flower by the “flower_ID” column within the colors table and every flower has an ID within the flowers table The ID is the field which links the records within each table together.

The final piece to note is if you use the WHERE operand within a JOIN query statement, you need to add one additional piece of information, and that is the table name.  Using our previous example, lets say you wanted to select all of the records WHERE ID=2  This would break the query because MySQL doesn’t know which ID you’re talking about.  Both tables have a column ID.  To do this correctly, you must specify which table you are referring to in your query.  See the example below:

SELECT
    *
FROM
  flowers
JOIN
   colors
ON
   colors.flower_ID=flowers.ID
WHERE flowers.ID=2

Again, you will see in the WHERE operand the table name flowers was referenced first, followed by the field within that table which you want to reference, followed by the value of that field.  The above query would return all of the colors associated with the flower which has an ID of 2

That’s all there is to a MySQL JOIN query statement!

BUT, let say you are working with some really long table names and you wanted to abbreviate them.  Well, you can easily do that by simply injecting the AS operand into the JOIN query statement.  Let use the same query we just worked through, but notice the difference.

SELECT
   *
FROM
  flowers AS fl
JOIN
   colors AS cl
ON
   cl.flower_ID=fl.ID
WHERE flowers.ID=2

All we did was simply abbreviated the table colors to cl and the table flowers to fl  When working with really long table names this comes in quite handy.

I have tried many programs on Windows to visually design MySQL database tables.  Recently I have been using an opensource program called DB Designer by FabForce.  DB Designer is in its 4th version and runs on both Windows and Linux.  Its layout is quite similar to Illustrator and Photoshop.  The toolbars make it very convenient to access all of the relationship types.  You can also manually edit the queries for total custom control.  Once created you can easily export the SQL for creation on your server, or generate the tables right from within the software.

Here are just a few of the many features available:

• Available on Linux / MS Windows
• User Interfaced based on industry standard layouting software
  • Canvas navigation similar to Adobe Illustrator® and Photoshop®
  • Palettes (docked / floating) including “Bird Eyes view”
  • Available objects include tables, realtions, labels, regions, images
  • Extensive Drag’n'drop support
  • Extensive Popup-Menu support
  • Advanced Editors
  • UNLIMITED Undo-/Redo- functions
  • Copy-/Cut-/Paste clipboard functions (XML, DDL)
  • Align functions
• Design Mode / Query Mode
• Reverse engineering MySQL, Oracle, MSSQL and any ODBC databases
• Userdefined schema-generation
• Model-To-Database syncronisation
• Index support
• Automatic foreign key placement

UPDATE: DB Designer has been depreciated.  Similar features can be found within - MySQL Workbench 5.0 Distribution

Must have plugins for WordPress by WordPress Jedi

Here is a simple technique you can use to make all of your .php files appears as though they are .html files instead.  You simply need to create or edit an existing .htaccess file.  Note: The .htaccess file must be placed within the root folder of your website.

# Make all PHP code look like HTML
AddType application/x-httpd-php .htm .html

Now each time  someone goes to yourdomain.com/index.html the browser will actually load index.php and simply change the extension to .html

Did you find value in this? If so please share this.

There will be two three-hour sessions this year – 1 to 4pm and 6 to 9pm.  Each includes a buffet meal featuring items from Penn Brewery.  Live entertainment will be provided by Flow Band and Blues Orphans

Ticket Pricing:

$45 advance purchase price May 1st through June 3rd

$60 at the door

Contact Penn Brewery at 412-237-9400, ext 100 to purchase tickets or visit the Penn Brewery Store.

Check out http://www.pennbrew.com/data/english/microbrewersfest.htm for a full list of the participating breweries.

This is an important security update and it helps protect your WordPress blog. This release includes security fixes and enhancements, including the new feature “clickjacking” protection.

We recommend you upgrade to WordPress version 3.1.3 ASAP.

WordPress version 3.1.3 includes the following security fixes and enhancements:

• Various security hardening by Alexander Concha.
• Taxonomy query hardening by John Lamansky.
• Prevent sniffing out user names of non-authors by using canonical redirects. Props Verónica Valeros.
• Media security fixes by Richard Lundeen of Microsoft, Jesse Ou of Microsoft, and Microsoft Vulnerability Research.
• Improves file upload security on hosts with dangerous security settings.
• Cleans up old WordPress import files if the import does not finish.
• Introduce “clickjacking” protection in modern browsers on admin and login pages.

I found a great article by Lucian Constantin explaining these new security fixes and explainations. He goes into great detail on the new “clickjacking” protection feature and more. Be sure to check it out here.

Files Revised in WordPress 3.1.3:

• readme.html
• wp-admin/admin-ajax.php
• wp-admin/custom-background.php
• wp-admin/custom-header.php
• wp-admin/includes/class-wp-plugins-list-table.php
• wp-admin/includes/import.php
• wp-admin/includes/media.php
• wp-admin/includes/post.php
• wp-admin/includes/template.php
• wp-admin/includes/update-core.php
• wp-admin/ms-delete-site.php
• wp-admin/plugins.php
• wp-admin/press-this.php
• wp-app.php
• wp-includes/canonical.php
• wp-includes/class-oembed.php
• wp-includes/default-filters.php
• wp-includes/formatting.php
• wp-includes/functions.php
• wp-includes/meta.php
• wp-includes/post.php
• wp-includes/query.php
• wp-includes/taxonomy.php
• wp-includes/theme.php
• wp-includes/version.php
• wp-login.php

In other news, the WordPress developers report that they are on schedule for WordPress 3.2. They have just released WordPress 3.2 Beta 2 for testing purposes. It is not recommended that you use it on production sites.

Important!

As we get ready for the new release of WordPress 3.2, it’s a good time to make sure that your site is currently running on a minimum of PHP 5.2 and MySQL 5.0.15 or higher. Once WordPress 3.2 is released, PHP 4 and MySQL 4 will not be supportedby WordPress. And you will not be able to upgrade to the newest version. Not sure if your website meets these requirements? You can check easily by installing the Health Check plugin. More information here.

WordPress & Security Resources:

• WordPress News: 3.1.3 Security Hardening Update
• WordPress Codex: Version 3.1.3
• WordPress Trac: 3.1.3 Change Log
• Download WordPress 3.1.3
• WordPress Codex – Updating WordPress
• Upgrading WordPress Extended
• Download WordPress 3.2 Beta 2

Important!

If you’re self-hosting WordPress on your own domain, you need to protect it by upgrading to WordPress 3.1.3 as soon as possible.

Leave your feedback

Have you upgraded to WordPress 3.1.3? Did you upgrade WordPress automatically through the Dashboard or manually? Do you have any WordPress plugin issues with WP version 3.1.3? If you noticed any glitches in the upgrade or conflicts with any plugins be sure to let us know. Leave your comment below.