| <!-- 1. Take your Campaign Monitor subscribe form as generated from within your account: --> | |
| <form action="http://myaccount.createsend.com/t/r/s/aljhk/" method="post" id="subForm"> | |
| <div> | |
| <label for="name">Name:</label><br /><input type="text" name="cm-name" id="name" /><br /> | |
| <label for="aljhk-aljhk">Email:</label><br /><input type="text" name="cm-aljhk-aljhk" id="aljhk-aljhk" /><br /> | |
| <input type="submit" value="Subscribe" /> | |
| </div> | |
| </form> |
| <?php get_header() ?> | |
| <!-- generated with home.php --> | |
| <div id="home-banner"> | |
| <?php putRevSlider("tsleadin") ?> | |
| </div><!-- #home-banner--> | |
| <div id="home-container"> | |
| <?php | |
| add_action( 'user_profile_update_errors', 'validate_field' ); | |
| function validate_field(&$errors, $update = null, &$user = null) | |
| { | |
| if($user->has_cap('s2member_level2')) { // Custom fields only display to business accounts | |
| // Nested if to check for field(s) | |
| if ($_POST['exp_years']=='' or $_POST['exp_years']==NULL) // Change to check for empty or any regular expression. |
There's no shortage of good resources for learning laravel. So instead of the usual introductory tutorial were just gonna learn Laravel by building a project from scratch and that's gonna be a User Management System.
I don't know if my definition of a User Management System is correct but here's my idea of what's it's capable of doing:
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <title>Angular</title> | |
| <script src="https://ajax.googleapis.com/ajax/libs/angularjs/1.3.15/angular.min.js"></script> | |
| </head> | |
| <body ng-app="myApp"> | |
| <div ng-controller="myCtrl as VM"> | |
| <a my-dir | |
| attr1="VM.sayHi('Juan')" |
| <script src="https://cdn.rawgit.com/zloirock/core-js/master/client/shim.min.js"></script> | |
| <script src="https://cdn.jsdelivr.net/lodash/4/lodash.min.js"></script> | |
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <script src="http://jashkenas.github.com/coffee-script/extras/coffee-script.js"></script> | |
| <meta charset=utf-8 /> | |
| <title>Welcome to JS Bin</title> | |
| <meta name="viewport" content="width=device-width"> | |
| <link href='http://fonts.googleapis.com/css?family=Doppio+One' rel='stylesheet' type='text/css'> |
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <meta charset="utf-8"> | |
| <meta name="viewport" content="width=device-width"> | |
| <title>JS Bin</title> | |
| </head> | |
| <body> | |
| <script src="https://cdn.jsdelivr.net/lodash/4/lodash.min.js"></script> |
| "use strict"; | |
| /* | |
| * Login page and fields | |
| * */ | |
| xdescribe('Application login page > ', function () { | |
| beforeEach(function() { | |
| //start at root app url every time tests are run | |
| browser.get('http://localhost:8888/#/login'); | |
| }); | |
| xit('should be accessible', function () { |
Sometimes you want to have a subdirectory on the master branch be the root directory of a repository’s gh-pages branch. This is useful for things like sites developed with Yeoman, or if you have a Jekyll site contained in the master branch alongside the rest of your code.
For the sake of this example, let’s pretend the subfolder containing your site is named dist.
Remove the dist directory from the project’s .gitignore file (it’s ignored by default by Yeoman).