“Goldman Sachs' planned exchange traded fund tracking the 50 most popular hedge fund stocks might be better shorted than purchased.”
This morning in the Financial Times, Stephen Foley dissects the mood at the recent SALT Conference in Las Vegas and the fleeting hopes that hedge funds will be able to receive longer lockup periods for capital.
Add another entry to the list of times The Simpsons appears to have predicted the future, because a live-animated episode aired on American television last night.
Living style guides are an important tool for web development today, especially in large, complex web applications. They help document styles and patterns, keep designers and developers in sync, and greatly help to organize and distill complex interfaces. Indeed, living style guides remain one of the best ways to communicate design standards to an organization.
Recently, our company went through the process of creating a living style guide. This is the story of how we developed our living style guide, the mistakes we made along the way, and why the current landscape of style guide generators did not suit our needs.
This week reminded me again of how refreshing attending a conference can be. As mentioned, I was at the beyond tellerrand conference and, apart from meeting new people, I mostly enjoyed the inspiration I got from listening to the great talks.
I realized how I might be able to solve a few things that had led to me being unhappy with my work in the past. My trying-to-change-everything-at-once strategy always failed, and seeing that some people just change small things and succeed, I recognized that this is what I want to try over the next months. And I'm happy that I don't need to do this alone but have some friends who spent nearly the entire Monday night talking with me about how to do more meaningful work.
Sometimes, changes to a .htaccess file, whether manually or via a tool with appropriate access, renders a WordPress site inoperable. It might be that all pages 404, or there is simply a white screen without errors, or you get redirected to weird places, or you have the inability to login.
Whatever the case, for me, I usually take the same approach as I do with a very broken computer (or even my body for that matter). I wipe it clean and start fresh. Then I slowly add new “elements” completing a checklist each time making sure that the new element didn't cause any grief to the overall system (to the best of my ability).
That's what I would like to demonstrate today. I am going to clear the .htaccess file, and add the essential elements back in. Once the site is operable and you have the ability to login, at that time, it's OK to add new elements (such as security enhancements, etc.) little by little.
Steps to Reset Your WordPress Site's htaccess File
The steps below assume that you have FTP software (I use FileZilla) installed and that you have loaded your FTP details into the Site Manager (you can get these details from your web host, and often this is simply: host address, username, and password).
If you don't have any FTP software or you are not familiar with FTP then you should read this tutorial to learn how to use FTP.
Login to your server via FTP (or SFTP).
Often you will land exactly where you need to which is the root of the server, but if you have WordPress installed in a subfolder, browse there by double clicking the folder.
Make a backup of the existing .htaccess file. You can do that by right-clicking it, and clicking “Rename”. Perhaps add “backup” to the end of the existing file name.
Download your backed up .htaccess file by double clicking it. Make sure you know where it lands on your computer!
Within FileZilla, rename the downloaded file (the one on *your* computer) back to the original file name (.htaccess). That way, when you upload it after modifying it, it'll be ready to rock.
Open the downloaded .htaccess file in a text editor.
Delete ALL text within it.
Copy over the text below into your downloaded .htaccess file.
Head back to FileZilla, and double click the file on your computer so that it uploads back to the server. If you followed the steps above exactly, it *will not* ask you to overwrite any files, because .htaccess will not already exist on the server (because you renamed it to preserve the original, albeit broken, one).
Test. If it doesn't work, make sure that you followed the steps above precisely, and that you copied the text exactly.
If it does work, then make your other changes one by one (starting with making one small change). Test again after the change. If it doesn't work, it should be obvious as to why. Just backup a step.
This week reminded me again of how refreshing attending a conference can be. As mentioned, I was at the beyond tellerrand conference and, apart from meeting new people, I mostly enjoyed the inspiration I got from listening to the great talks.
I realized how I might be able to solve a few things that had led to me being unhappy with my work in the past. My trying-to-change-everything-at-once strategy always failed, and seeing that some people just change small things and succeed, I recognized that this is what I want to try over the next months. And I'm happy that I don't need to do this alone but have some friends who spent nearly the entire Monday night talking with me about how to do more meaningful work.