Git is a software configuration management (SCM) program. This is just a fancy way of saying that it’s a software package that tracks and controls changes in the code.
I initially installed Git because I was playing around with Vagrant (local web development). It’s also a safe way to get the nerdy Bash shell (UNIX-like scripting language) for Windows without going into Cygwin .
These are some things that I changed in UniServer to speed up working with localhost.
Edit Core > Apache2 > conf > http.conf
I use 4001 as my localhost port.
Also disable the loading of the CGI module by commenting # this line:
#LoadModule cgi_module modules/mod_cgi.so
I think it runs faster… maybe.
I’ll update this if I make any other changes.
SASS is one of the scripting languages for CSS (like LESS, STYLUS, CSS-Crush, Myth, etc.). So, instead of searching and replacing colors or any other CCS attribute through ever expanding stylesheets, SASS compiles the stylesheet using variables and other coding to dump out a .css file.
The advantage to using SASS is that you can reuse CSS and flavor it for all sorts of projects. You can break your CSS code into logical sections. The danger of any sort of machine generated code is that you might get some bloat.
Oh–and did I mention that you have to install and learn another language and work with the command line? After my debugging adventures with grunt and a missing comma, I’m not too keen on learning another syntax.
But, do you really need SASS or any other preprocessor? CSS actually has variables. Of course, they don’t call them that. They’re called “CSS Custom Properties.”
The problem was that custom properties weren’t supported in all browsers. They are now supported by recent versions of all modern browsers, even MS-Edge.
There are still other coding functions that SASS and the other CSS preprocessors can do that plain CSS can’t.
So… the answer to whether or not you need SASS is a definite MAYBE. Just watch those commas.
Looks like updating Local WordPress version can be a painless. First, fully backup your local WordPress folder. Download the latest version of WordPress. Unzip it. Overwrite the local WordPress files.
So far, so good.
Most of the everything works as advertised. Maybe it’s something to do with changing a font or something after you set the tag. The result is poof–gone forever. It’s more than a bit irritating if you’ve already finished your post.
If you want to be safe, either wait until the whole post is complete and add the tag or just wait and do it within WordPress (safest option).
But Wait There Might A Chance to Recover. If you’re lucky there could be a html file of the lost post hidden away in a temp folder which I believe is created for the preview tab.
I found mine at:
This might be stored in a different temp folder for your particular post. Best bet is to search for the folder: “WindowsLiveWriter1286139640”. Inside this folder, there should be subfolders. I found my missing content in the most recent folder.
The easiest way to get everything back is to open the index.htm and from the browser copy the webpage with select all and then paste into a new WLW post. After all the content is back, reformat and make it look pretty again. Still a pain, but much better than rewriting from memory.
It started simple enough. I had some domains on 1 & 1 Internet, a web hosting company base out of Germany, and wanted to move a block of domains to another registrar. I’d been with 1&1 a long time and never thought much about support. Most of what I do isn’t exactly life or death. Continue reading
Remuxing reassembles the data packets of the audio stream and that’s exactly how to fix the problem.