sudo apt install zsh-autosuggestions zsh-syntax-highlighting zsh
<?php | |
/** | |
* Kindly provided by @notebleu on the Avada Community Forum | |
* - https://theme-fusion.com/forums/topic/unnecessary-js-files-load-even-when-fusion-elements-disabled/#post-648617 | |
*/ | |
function custom_disable_avada_js() { | |
Fusion_Dynamic_JS::deregister_script('avada-comments'); | |
Fusion_Dynamic_JS::deregister_script('avada-general-footer'); | |
Fusion_Dynamic_JS::deregister_script('avada-mobile-image-hover'); |
Here are the simple steps needed to create a deployment from your local GIT repository to a server based on this in-depth tutorial.
You are developing in a working-copy on your local machine, lets say on the master branch. Most of the time, people would push code to a remote server like github.com or gitlab.com and pull or export it to a production server. Or you use a service like deepl.io to act upon a Web-Hook that's triggered that service.
##Date and Time
=TIMEVALUE(SUBSTITUTE("{{OccurredAt}}"," at ", " ")) + DATEVALUE(SUBSTITUTE("{{OccurredAt}}"," at ", " "))
##Date
=DATEVALUE(SUBSTITUTE("{{OccurredAt}}"," at ", " "))
##Time
<style type="text/css" media="screen"> | |
html { margin-top: 32px !important; } | |
* html body { margin-top: 32px !important; } | |
@media screen and ( max-width: 782px ) { | |
html { margin-top: 46px !important; } | |
* html body { margin-top: 46px !important; } | |
} | |
</style> |
/** | |
* This Google Sheets script keeps data in the specified column sorted any time | |
* the data changes. | |
* | |
* After much research, there wasn't an easy way to automatically keep a column | |
* sorted in Google Sheets, and creating a second sheet to act as a "view" to | |
* my primary one in order to achieve that was not an option. Instead, I | |
* created a script that watches for when a cell is edited and triggers | |
* an auto sort. | |
* |
* { | |
font-size: 12pt; | |
font-family: monospace; | |
font-weight: normal; | |
font-style: normal; | |
text-decoration: none; | |
color: black; | |
cursor: default; | |
} |
remove_action( 'woocommerce_before_shop_loop', 'woocommerce_catalog_ordering', 30 ); |
<snippet> | |
<content><![CDATA[ | |
<!-- begin $1 --> | |
<div class="$1"> | |
$2 | |
</div> | |
<!-- end $1 --> | |
]]></content> | |
<!-- Optional: Set a tabTrigger to define how to trigger the snippet --> | |
<tabTrigger>di</tabTrigger> |
A basic Grunt configuration for working with the Bones Wordpress Starter theme. To be expanded! Compiles and compresses Sass and uses rsync to update the local installation of Wordpress for testing so I can keep my MAMP installation free of extraneous files...and simply FTP over the final result if it checks out without putting uneccessary node_modules
or .scss
files on the server by mistake. This was pretty much put together because I kept mistakenly FTPing over my .sass-cache
files like an idiot.
For this to work, the theme in development lives in 'src' inside the project directory so node_modules
, .sass-cache
, gruntfile.js
, package.json
and src
are all together in the top-level directory.
project folder
.sass-cache
gruntfile.js
node_modules
package.json