Check Out the New Recommended Resources on Wptuts+

We’ve added a new page to the site, which will help WordPress pros grab top quality software, tools and services. It’s filled with our favorite WordPress resources. You can jump straight over to our Recommended Resources page here on Wptuts+ or read on for further information.

Hand Picked Resources for WordPress Professionals

Our Tuts+ editorial team has hand-picked these resources, which feature hosting recommendations, coding apps, and web services that will keep your WordPress sites in tip-top shape. Our goal here is to feature the highest quality, useful resources that we highly recommend and in most cases use ourselves. It’s a quick stop to finding the best of the best when you have an urgent need to fill as a WordPress professional.

Keep an eye out for more of these site sections as our Resource pages roll out across the Tuts+ network.

What WordPress Tools Do You Recommend

This is version 1.0 of this Wptuts+ Resources page. We’ll continue to add to it and grow this section of the site. We could use your help with that!

Are there any awesome apps, tools or services that you feel we missed Bounce into the discussion below and leave a comment about what resource you recommend to fellow WordPress experts.

Check out the original source here.

http://bit.ly/YugvRVhighest quality, original source, quality software, recommended resources, software tools, uqality software, useful resources

Jeffrey Tucker – What Bitcoin Is Teaching Us

Jeffrey Tucker – What Bitcoin Is Teaching Us:

Jeffrey Tucker (@JeffreyATucker), editor of Lassez-Faire Books and past editorial vice president of the Ludwig von Mises Institute, posts how deflationary currency brings a change to what we know about money.  Excerpts:

“None of us in living memory has had experience with a currency that rises in value. The emergence of Bitcoin — a digital currency that has grown in purchasing power over time — has changed that experience dramatically.”

“The 20th-century experience flipped our expectations for what money should do. Especially in the postwar period, the falling value of the dollar punished savings and rewarded spending. This is exactly what the Keynesian economists hoped for. They wanted money always circulating and never ‘hoarded.’ ‘Deflation’ was to be avoided no matter what.”

“Bitcoin is often described as a ‘deflationary’ currency. This is exactly why Paul Krugman hates it so much.”

“Here’s what beautiful about this experience: It doesn’t matter in the slightest what Paul Krugman thinks. It doesn’t matter how many economic experts Paul Krugman lines up to oppose Bitcoin. It doesn’t matter how many Nobel Prize winners denounce it and oppose it. That’s because Bitcoin is not a “policy” invented by elite and privileged intellectuals. It is a market-based currency, one created by an entrepreneur and chosen by market players.”

“That is an essential postulate of the free society. When government gets hold of the money, freedom is in peril. When the market makes and manages money, freedom has a built-in reinforcement in half of every transaction. In short, just based on our experience with Bitcoin so far, we see the conventional wisdom of a century completely turned on its head. Fantastic!”

 – http://lfb.org/today/what-bitcoin-is-teaching-us
 – http://bitcointalk.org/index.phptopic=171577.0 (Further discussion of the article)

All News – Daily E-mail Subscription – Twitter: @BitcoinNews

Check out the original source here.

http://bit.ly/13ishSEconventional wisdom, keynesian economists, ludwig von mises institute, mail subscription, nobel prize winners, nobel prize wniners, vo nmises institute, von mises institute

Running ActiveCollab 3 On Nginx (LEMP) On Debian Wheezy/Ubuntu 12.10

Version 1.0
Author: Falko Timme <ft [at] falkotimme [dot] com>
Follow me on Twitter
Last edited 04/10/2013

This tutorial shows how you can install and run activeCollab 3 on a Debian Wheezy or Ubuntu 12.10 system that has nginx installed instead of Apache (LEMP = Linux + nginx (pronounced “engine x”) + MySQL + PHP). nginx is a HTTP server that uses much less resources than Apache and delivers pages a lot of faster, especially static files.

I do not issue any guarantee that this will work for you!

1 Preliminary Note

I want to install activeCollab in a vhost called http://www.example.com/example.com here with the document root /var/www/www.example.com/web.

You should have a working LEMP installation, as shown in this tutorial:

A note for Ubuntu users:

Because we must run all the steps from this tutorial with root privileges, we can either prepend all commands in this tutorial with the string sudo, or we become root right now by typing

sudo su

2 Installing APC

APC is a free and open PHP opcode cacher for caching and optimizing PHP intermediate code. It’s similar to other PHP opcode cachers, such as eAccelerator and XCache. It is strongly recommended to have one of these installed to speed up your PHP page.

APC can be installed as follows:

apt-get install php-apc

Reload PHP-FPM as follows:

/etc/init.d/php5-fpm reload

3 Installing activeCollab

The document root of my http://www.example.com web site is /var/www/www.example.com/web – if it doesn’t exist, create it as follows:

mkdir -p /var/www/www.example.com/web

Next download activeCollab from the activeCollab web site (you need to buy a license – it’s not freeware) to your local computer; from there, upload it to your server (e.g. the /tmp directory), unzip it and place it in your document root:

cd /tmp
unzip activecollab-corporate-3.2.12.zip
cd for-upload/
mv * /var/www/www.example.com/web/

It is recommended to make the document root and the activeCollab files in it writable by the nginx daemon which is running as user www-data and group www-data:

chown -R www-data:www-data /var/www/www.example.com/web

If you haven’t already created a MySQL database for activeCollab (including a MySQL activeCollab user), you can do that as follows (I name the database activecollab in this example, and the user is called ac_admin, and his password is ac_admin_password):

mysqladmin -u root -p create activecollab

mysql -u root -p

GRANT ALL PRIVILEGES ON activecollab.* TO ‘ac_admin’@’localhost’ IDENTIFIED BY ‘ac_admin_password’;
GRANT ALL PRIVILEGES ON activecollab.* TO ‘ac_admin’@’localhost.localdomain’ IDENTIFIED BY ‘ac_admin_password’;

FLUSH PRIVILEGES;

quit;

Next we create an nginx vhost configuration for our http://www.example.com vhost in the /etc/nginx/sites-available/ directory as follows:

vi /etc/nginx/sites-available/www.example.com.vhost

server {
       listen 80;
       server_name www.example.com example.com;
       root /var/www/www.example.com/web;

       if ($http_host != "www.example.com") {
                 rewrite ^ http://www.example.com$request_uri permanent;
       }

       index index.php index.html;

       location = /favicon.ico {
                log_not_found off;
                access_log off;
       }

       location = /robots.txt {
                allow all;
                log_not_found off;
                access_log off;
       }

       # Deny all attempts to access hidden files such as .htaccess, .htpasswd, .DS_Store (Mac).
       location ~ /\. {
                deny all;
                access_log off;
                log_not_found off;
       }

       location / {
                try_files $uri $uri/ /index.phppath_info=$uri&$args;
                access_log off;
                expires max;
       }

       location ~ \.php$ {
                try_files $uri =404;
                include /etc/nginx/fastcgi_params;
                fastcgi_pass unix:/var/run/php5-fpm.sock;
                fastcgi_index index.php;
                fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
                fastcgi_intercept_errors on;
       }
}

To enable the vhost, we create a symlink to it from the /etc/nginx/sites-enabled/ directory:

cd /etc/nginx/sites-enabled/
ln -s /etc/nginx/sites-available/www.example.com.vhost http://www.example.com.vhost

Reload nginx for the changes to take effect:

/etc/init.d/nginx reload

Now we can launch the web-based activeCollab installer by going to http://www.example.com – click on the Validate button to have the installer check if the system requirements are fulfilled:

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

If the system requirements are fulfilled, you can now fill in your database details and click on Connect:

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

Next, specify an email address and password for the administrator account, accept the license agreement and click on Install:

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

That’s it – click on the Log in Now! button or go to http://www.example.com/public/index.php

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

… to log into activeCollab:

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

This is how the activeCollab interface looks:

(JavaScript must be enabled in your browser to view the large image as an image overlay.)

4 Links

About The Author

Falko Timme is the owner of nginx WebhostingTimme Hosting (ultra-fast nginx web hosting). He is the lead maintainer of HowtoForge (since 2005) and one of the core developers of ISPConfig (since 2000). He has also contributed to the O’Reilly book “Linux System Administration”.

Check out the original source here.

http://bit.ly/11m7BsOactivecollab, document root, eaccelerator, intermediate code, intermediatec ode, local computer, roo tprivileges, root privileges, tmp directory

Timothy B. Lee – Four Reasons Bitcoin Is Worth Studying

Timothy B. Lee – Four Reasons Bitcoin Is Worth Studying:

Forbes contributor Timothy B. Lee (@BinaryBits) writes again on Bitcoin. Excerpts:

“Even if you think the current value of of more than $140 is a bubble, it’s clear that Bitcoin has some genuine applications. The number of daily Bitcoin transactions has soared from around 1000 at the beginning of 2011 to about 50,000 today. Figuring out the “fundamentals” that drive the currency’s long-term value seems like an interesting theoretical puzzle.”

“A core part of Bitcoin’s appeal is that it’s not under anyone’s control. Supposedly, nobody has the authority to change the Bitcoin money supply, cancel or reverse transactions, or otherwise change the attributes of the protocol. But in practice that’s not really true. In the wake of last month’s fork, the elites in the Bitcoin community effectively changed the rules in a matter of hours. In principle, there’s no reason those same elites couldn’t make other changes to the Bitcoin protocol.”

“In principle, these two pools might be able to join forces and execute a 51 percent (or 53 percent) attack on the rest of the network. But doing so might prove foolish in the long run, since that kind of power grab might undermine public confidence in the currency’s long-term viability, since a mining cartel might have the power to change the rules of the Bitcoin protocol in ways that benefit themselves at the expense of ordinary users.”

 – http://onforb.es/10yeRSe
 – http://bitcointalk.org/index.phptopic=170270.0 (Further discussion of this article)

All News – Daily E-mail Subscription – Twitter: @BitcoinNews

Check out the original source here.

http://bit.ly/11cmVavcontributor, current value, curretn value, mail subscription, mail subscriptoin, money supply, original source, public confidence, term viability

Cross-Platform Sass and Compass in WordPress

I find it particularly interesting when other developers share their workflow tips and tricks. It can be very helpful to take a sneak-peak into somebody else’s development world and find out what tools they are using to make their own life easier.

Well today I’m going to show you a portion of my own workflow – specifically how to use Sass and Compass when developing a WordPress theme. Instead of simply explaining the configuration and tools needed, I thought it would be better to start from scratch and show you exactly what’s needed to get going when developing a WordPress theme that uses Sass and Compass.

I hope this article sounds interesting to you and I’m looking forward to sharing a small part of my workflow with you – I encourage you to do the same.

What You’ll Need

After much experimentation, this is the best tool for cross-platform Sass and Compass support. This is a menu-bar only app that can compile Sass files into CSS (it also has live-reload). It is not free, but at $10.00 I’ve found it more than worthwhile.

Alternatives

In the interest of providing a solution for all readers, regardless of platform, this tutorial will provide configuration for the app mentioned above. There are of course other alternatives, but be aware that things may need slightly different configuration than what you see here.

  • Mac alternative – Codekit
  • Windows alternative – I’ve not come across a decent Windows GUI alternative other than the app we’ll be using in this tutorial. If you know of one, please feel free to share in the comments below.

1. Start With a Theme

The _s theme is a design-less theme perfectly suited for developers. As stated on their website “I’m a theme meant for hacking so don’t use me as a Parent Theme.” – Sounds perfect for us. Head along to their website, _s theme, and use the ‘Generate’ command on their homepage to download a custom build. You could simply download the theme directly from GitHub, but then you’d have to manually search for all instances of _s within the theme and replace them with your own prefix. Using ‘Generate’ does that part for you automatically.

Once you have your custom build downloaded, unzip the theme directory into wp-content/themes. For this tutorial I used the generator to create the theme wp-tuts and the directory structure should now look like this:

You can now go ahead and activate the theme from the Admin Panel.

2. Configuration for Sass and Compass

In the theme’s root directory, we’ll have a folder called sass. This is where we’ll put all of our .scss files. Compass.app will then watch that directory and compile everything into the single style.css file that lives in the root of the theme.

  1. In the root of the theme, create a folder called sass.
  2. Also in the root, create a file called config.rb

These are the settings that will work well with WordPress:

/* config.rb in the theme's root. */

css_dir = "/"
sass_dir = "sass"

output_style = :compressed

Ok, we have our sass folder and our config.rb both sitting in the root of our theme. We are now ready to rip apart the theme’s CSS file and create individual files that will be easier to build upon / maintain in the future.

3. Convert the Theme’s CSS to Sass

One of the advantages to using any CSS preprocessor is the ability to split our CSS into many small files. This helps our workflow tremendously as we can organize our code into related chunks that are easier to maintain and work with. So instead of having everything crammed into one giant CSS file, we can have a separate file that is only for resets. Then we could also have a separate file that only handles the menu, one file for media, etc. etc. We can have as many .scss files as we like, and after compilation they will all be compressed down into a single style.css.

If you look at the style.css file that comes shipped with the theme we downloaded, you’ll see that the author has put comments to separate the content into sections like this:

/* =Content
----------------------------------------------- */

.sticky {
}

.hentry {
	margin: 0 0 1.5em;
}

We’ll use those comments as a guide for breaking up this stylesheet into separate .scss files.

Within the sass directory, create a file called style.scss – This is the file that we’ll use to import all of the other files. Also, this is the only scss file that will NOT be prefixed with an underscore (“_”). This tells our compiler that this file should be converted into an actual CSS file.

Now run through the style.css file and for each commented section, create a new file in the sass folder that is prefixed with an underscore and has the file extension .scss. Copy the contents of that section into the newly created file.

For example, where you see this in the style.css, you would create a file called _navigation.scss and put it within the sass folder:

/* =Navigation
----------------------------------------------- */

.site-content [class*="navigation"] {
	margin: 0 0 1.5em;
	overflow: hidden;
}
[class*="navigation"] .previous {
	float: left;
	width: 50%;
}
[class*="navigation"] .next {
	float: right;
	text-align: right;
	width: 50%;
}

/* Ends up being sass/_navigation.scss */

After running through the entire stylesheet, your sass directory should now look like this. (notice that style.scss is the only file that is not prefixed with an underscore, everything else is considered to be a partial, and will not be compiled into a separate CSS file.)

Now that we’ve put all the CSS into separate SCSS files, we now need to import those into the style.scss file and also add the theme information.

/*!
Theme Name: wp-tuts
Theme URI: http://underscores.me/
Author: Underscores.me
Author URI: http://underscores.me/
Description: Description
Version: 1.0
License: GNU General Public License
License URI: license.txt
Tags:
*/

@import "reset";
@import "global";
@import "menu";
@import "content";
@import "asides";
@import "media";
@import 'navigation';
@import 'comments';
@import 'widgets';
@import 'scroll';

Ensure these files are imported in the same order that the CSS appeared in the original document. You can see that we start with reset and add the rest in the correct order. You still have to think about the order in which rules are defined in the final CSS!

Important: Also note that exclamation mark (!) on the first line. This tells the compiler not to strip out this important comment. We need to do this because earlier we set the option output_style = :compressed (in the config.rb file). This means that all white-space and comments will be removed from the compiled version. This is a great thing and you certainly want that to happen – but not here! If this comment was removed by the compiler then WordPress would not recognize this theme.

4. Compiling Into CSS

We’ve done all the manual work, now it’s time to bring the automation into play. Go ahead and delete the style.css file from the root of the theme as we no longer need it. Now, if you have successfully followed all the steps above, then you should be able to open up Compass.app and choose Watch a Folder. Select your theme’s root directory (in our case, it’s the wp-tuts folder inside of wp-content/themes)

  1. Open Compass.app
  2. Select Watch a Folder
  3. Select your theme’s root directory

After a very short delay, you should see a new style.css file that has been generated. Open it, and you should see a minified version. This is an indication that everything worked as expected.

5. Using Compass

At this point, we’ve converted the theme’s base CSS into small, manageable chunks of code and now we’ll look at using Compass with our project.

Compass is a framework that provides a lot of powerful features to make your life easier when crafting CSS. Because we’re using Compass.app, we can bring in the functionality provided by Compass by simply importing the required module in our style.scss file. For example, if you want the CSS3 modules of Compass, just do this:

/* Make this the first import you do, then it will be availble to all files. */
@import "compass/css3";

That’s really it, now you can head over to the Compass website and when you’re ready to use any of its features in your project, you’ll know exactly how to do it.

You’re Ready!

You now have all you need to start using Sass and Compass when building themes in WordPress. Next, we’ll take a look at a couple of very simple examples of how to use them and whilst this tutorial is not an introduction to Sass and Compass, the examples below should help beginners further recognize the benefits of using a CSS pre-processor.

6. Examples

As we are now leveraging the power of a pre-processor, we can be more efficient when writing CSS and avoid repeating ourselves. One of the things I have on every single WordPress project is a _vars.scss file where I would keep anything that is project specific in variables. That way, I can refer to the variable names throughout many files, and should I need to change something, I would only have to do it in one place.

/* Example of the types of things you might what you might put into _vars.scss */

$brand-color     : #56483B;
$default-padding : 24px;

To use them across your entire collection of .scss files, just @import it like any other file into style.scss, but just make sure it’s the first one, or just after reset would be ok too. Once you have imported it, use the variables like this:

/* Inside any file imported AFTER _vars.scss, you can use all of your variables */
.logo {
	color : $brand-color
}

Compass

Often, many people will only use Compass for its vendor-prefixing abilities. I fall into that category myself and here’s a small example to show why:

/* Without Compass */
* {
	-moz-box-sizing: border-box;
	-webkit-box-sizing: border-box;
	box-sizing: border-box;
}

/* With Compass */
* {
	@include box-sizing(border-box);
}

Conclusion

I hope this tutorial has been helpful in showing a simple but effective workflow when using Sass and Compass within WordPress. The two examples I gave at the end are the absolute basics of using Sass and Compass and you should look into both separately to make full use of them.

Saying that, you’ll still be improving your workflow a great deal with what you’ve learned here. By using these tools to split up CSS into small files, using variables to reduce repetition, and removing the need to type vendor prefixes – you’re on your way to better development workflow.

Check out the original source here.

http://bit.ly/12bmG1ucross platform, developers, edvelopers, menu bar, scratch, sneak paek, sneak peak, tips and tricks

Gigaom’s David Meyer – Yes, You Should Care About Bitcoin

Gigaom’s David Meyer – Yes, You Should Care About Bitcoin:

David Meyer (@superglaze)’s post on Gigaom offers a current introduction to Bitcoin for any of its readers who haven’t yet brought themselves up to speed.  Excerpts:

“No one’s really sure where [Bitcoin] will end up, because no one has really done this distributed, borderless digital currency thing for real before – yes, there are Facebook Credits and Linden dollars, but these are still centralized and controlled as such.”

“There have also been multiple previous attempts at creating non-digital alternative currencies, such as the Liberty Dollar, which earned its creator Bernard von NotHaus a counterfeiting conviction. Bitcoin may share the anti-statist motivation behind that wannabe currency, but it’s hard to see how it could constitute counterfeiting.”

“If you lose your Bitcoin wallet, the money is lost forever, to everyone. If you lose your bankcard, it doesn’t wipe out the money in your account, and your bank will issue you a new one. There is no such mechanism in place here; losing Bitcoins is effectively like burning banknotes.”

“From where I’m sitting, Bitcoin is already proving its worth as a disruptor and as a test-case for how technology could divorce currency from certain external factors.”

[Note, the same article was syndicated on CNN Money]

 – http://bit.ly/XfAVAz
 – http://bitcointalk.org/index.phptopic=167472.0 (Further discussion of the article)

All News – Daily E-mail Subscription – Twitter: @BitcoinNews

Check out the original source here.

http://bit.ly/ZrtNirdavid meyer, digital currency, external factors, external factosr, liberty dollar, mail subscription, mail susbcription, original source