Comments for TipsFor.us

Comment on The Importance of Unique Passwords by Help! My Site Was Hacked! | TipsFor.us

Help! My Site Was Hacked! | TipsFor.us — Tue, 15 Jan 2013 03:51:37 +0000

[...] into other sites using the credentials he cracked from your database. This is why you should never reuse a password: if one site gets hacked, the dominos start falling. You can use 1password or a similar tool to [...]

Comment on The Importance of Unique Passwords by Brian

Brian — Wed, 21 Nov 2012 18:21:26 +0000

I still like and use KeePass (see article). I'm warming up to LastPass' convenience, but the open-source nature of KeePass is more appealing. Plus, you stay in control of your data and are not relying on a third party.

Comment on Why GoDaddy is a Horrible Host by Everett - TipsFor.us

Everett - TipsFor.us — Sat, 23 Jun 2012 22:21:34 +0000

One more gem: flock is not functional on their servers with PHP (for file locking).

And this: http://www.forbes.com/sites/kellyclay/2012/09/10/5-reasons-you-should-leave-godaddy-and-how/

And the capper: one one page of their domain management, it says I have one number of domains. On another page, the NUMBER IS DIFFERENT. Searching for one of the “missing” domains comes up empty. This is web dev 101 stuff and they’ve categorically failed.

Comment on Review of Web-based Project Management Software by Everett - TipsFor.us

Everett - TipsFor.us — Wed, 29 Feb 2012 23:14:02 +0000

I keep finding these things:

http://www.assembla.com/
http://www.kanbanpad.com/
https://www.clutchapp.com/
https://sifterapp.com/tour
http://hedgehoglab.com/products/fixx/features/project-management/
http://www.getdonedone.com/plans-pricing
http://www.bontq.com/features.php
http://www.bugherd.com/features
https://bugrocket.com/pricing

Comment on Why GoDaddy is a Horrible Host by Everett - TipsFor.us

Everett - TipsFor.us — Mon, 30 Jan 2012 16:42:15 +0000

The latest bit of incompetence: even using GoDaddy as a registrar had a total fail last week. One client had a dozen domains or so and we just had to edit DNS records to switch the email servers. GoDaddy’s dashboard showed the correct settings, but we kept getting email errors. Only after calling GoDaddy did they admit that there was a problem on the back-end, and they had to manually correct it. When DNS changes can take 24 hours to propagate, having to do them twice makes for a real bad experience when we were losing emails that whole time.

Comment on Microsoft takes another hit: NGINX tops IIS by Everett - TipsFor.us

Everett - TipsFor.us — Fri, 13 Jan 2012 03:54:33 +0000

I’ll believe that when Texas executes one.

Comment on Microsoft takes another hit: NGINX tops IIS by Brian - TipsFor.us

Brian - TipsFor.us — Thu, 12 Jan 2012 13:36:52 +0000

But… but… corporations are people!

Comment on WordPress vs. MODx by How WordPress Destroyed the Internet | TipsFor.us

How WordPress Destroyed the Internet | TipsFor.us — Tue, 10 Jan 2012 07:38:21 +0000

[...] ranted about WordPress before but what put me over the top today was the Suffusion Theme. It looks like a clean layout, so I [...]

Comment on Why GoDaddy is a Horrible Host by Rolanda Mcgue

Rolanda Mcgue — Sat, 07 Jan 2012 22:57:11 +0000

Thanks, I’m continually in search of information regarding VPS services.

Comment on Releasing New Versions of your WordPress Plugins by Everett - TipsFor.us

Everett - TipsFor.us — Fri, 06 Jan 2012 06:30:55 +0000

I should point out the super-fast version for those of you who are daring enough to try it:

1. Make your edits, update your readme.txt to reflect the new version, and update the “stable tag” to this new version (yes, update it BEFORE that directory exists).
2. Commit your changes (the head is ON now…)
3. Quickly copy over the trunk to the tags folder as outlined above, e.g.
svn copy http://plugins.svn.wordpress.org/your-plugin/trunk http://plugins.svn.wordpress.org/your-plugin/tags/0.5

That works, but it’s a potentially problematic: if WordPress scans its directory before you’ve copied over the trunk, it will package up the code at the head in the TRUNK. At that moment, that code should be identical to what you’re copying into the new tags directory, but you have to ask “when will WP re-scan the repo?” because you definitely don’t want the code at the HEAD to be in your zip file after you’ve made other changes.