Press minus + shift + s and return to chop/fold long lines!
This contract is not meant to trick or deceive you; the intention is purely to protect both parties. I have tried to keep the wording as plain as possible, but if anything is unclear, please let me know and I will be more than happy to clarify it with you. Also, until you sign it, please feel free to request to change bits of it to suit your requirements.
In short, [client name] is contracting me, [my name], to [description of my role] between [start date and finish date].
By signing this, you are confirming that you have the power and ability to enter into this contract on behalf of [client's company].
| RewriteEngine On | |
| # add-ons rewrite rule. Note absence of slash in "rewrite to" (second portion of rewriterule) | |
| # this makes the rewrite relative to the directroy of the .htaccess file unless RewriteBase is defined | |
| RewriteRule ^add-ons/apps/([a-zA-Z0-9-/]+)$ add-ons/apps.php?s=$1 [L] | |
| # The "most generic" rule comes last, as "more specific" rules should match first. | |
| # Added a check to see if we've already got .php in the URL. | |
| RewriteCond %{REQUEST_URI} !.php$ | |
| RewriteRule ^(.+)$ $1.php [L,QSA] |
| .selected { | |
| background: #000; | |
| color: #fff; | |
| } | |
| .even > li:first-child { | |
| @include nth-child(even, 'li') { | |
| @extend .selected; | |
| } | |
| } |
Below are two techniques to help debug the WSOD (white screen of death), usually a 500 server error, in an ExpressionEngine site. The Basic-Debugging option will be suitable in most cases and is specific to ExpressionEngine. The Advanced-Debugging is generic and applicable to any PHP based software. If the basic debugging does not work, try the advanced.
If you get a WSOD you will need to first get your site to reveal an error before reporting it to EllisLab or the add-on developer. Simply reporting "I get a white screen" does not give the developer enough information to assist you. An error message on the other hand will point the developer to the source of the issue.
| <?php | |
| perch_blog_date_archive_months('years.html', 'months.html'); | |
| ?> |
Jekyll is a great CMS for developers and GitHub Pages is a great host to store your Jekyll sites. There is just one problem, GitHub runs Jekyll in safe mode, which means you can't use plugins. One thing you can do is building the Jekyll website locally and then push to GitHub.
Alexandre Rademaker found a solution to do this easially, which is quite usefull: "GitHub Pages and Jekyll plugins" After reading this I thought, that can be done easier!
Git provides a way to have aliases of bash commands. You can do this by adding items to the alias key of your configuration. For this, you can add this locally by adding this lines to your %PROJECT_ROOT%/.git/config file:
| (function($){ | |
| $(function(){ | |
| var $form = $('#search'), // Search form | |
| $target = $('#results'), // Results container | |
| rp = 'search/ajax-results'; // Template for results only | |
| // Function to execute on success | |
| var success = function(data, status, xhr) { | |
| $target.html(data); | |
| }; |
