That is is basically a "fork" of blog article i'm constantly returning to. It seems that the blog is down:
Dave Bass proposed this which I picked up for my implementation (here for an 8-chars token):
That is is basically a "fork" of blog article i'm constantly returning to. It seems that the blog is down:
Dave Bass proposed this which I picked up for my implementation (here for an 8-chars token):
// blade template - just html really | |
@section('journal-carousel') | |
<div class="container article-carousel"> | |
<div class="row"> | |
<div class="col-sm-12"> | |
<div class="article-carousel__slider"> | |
@for ($i = 0; $i < 3; $i++) | |
<figure><img src="{{Theme::url('images/blonde'.$i.'.jpg')}}" alt="" class="img-responsive" /></figure> | |
@endfor | |
@for ($i = 0; $i < 3; $i++) |
# This is a template .gitignore file for git-managed WordPress projects. | |
# | |
# Fact: you don't want WordPress core files, or your server-specific | |
# configuration files etc., in your project's repository. You just don't. | |
# | |
# Solution: stick this file up your repository root (which it assumes is | |
# also the WordPress root directory) and add exceptions for any plugins, | |
# themes, and other directories that should be under version control. | |
# | |
# See the comments below for more info on how to add exceptions for your |
To remove a submodule you need to:
To remove a submodule you need to:
git clone --bare [email protected]:user/repo.git
cd repo.git
git push --mirror [email protected]:user/repo.git
# Continuous Integration to a WP Engine install | |
# PHP CircleCI 2.1 configuration file | |
# Requirements: | |
# 1. In CircleCI settings, add environment variables for your site's installs: | |
# * WPE_PRODUCTION_INSTALL=thenameofyourproductioninstall | |
# * WPE_STAGING_INSTALL=thenameofyourstaginginstall | |
# * WPE_DEVELOPMENT_INSTALL=thenameofyourdevelopmentinstall | |
# 2. In your repo, have two files | |
# * `./.gitignores/__default` -- Excludes any compiled files |
<?php | |
/** | |
* Gravity Wiz // Gravity Forms // Map Submitted Field Values to Another Field | |
* | |
* Usage | |
* | |
* 1 - Enable "Allow field to be populated dynamically" option on field which should be populated. | |
* 2 - In the "Parameter Name" input, enter the merge tag (or merge tags) of the field whose value whould be populated into this field. | |
* | |
* Basic Fields |