aelvan

# Varnish 4.0 file for our Craft CMS projects
# Based on https://github.com/mattiasgeniar/varnish-4.0-configuration-templates/blob/master/default.vcl
# 
# This is still work in progress, comments appreciated.

vcl 4.0;

import std; 
import directors;

mdcpepper

<?php
namespace Craft;

class EntryTypeSourcesPlugin extends BasePlugin
{
	public function getName()
	{
		return Craft::t('Entry Type Sources');
	}

ryanscherler

This issue is noted here: https://deliciousbrains.com/wp-migrate-db-pro/doc/ssl-errors/

Original reference for this fix is from: http://stackoverflow.com/questions/26461966/osx-10-10-curl-post-to-https-url-gives-sslread-error/26538127#26538127

Check OpenSSL version

php -i | grep "SSL Version"

You'll likely see this:

Chrisedmo

<?php

class Craft3ValetDriver extends ValetDriver
/* https://github.com/laravel/valet/blob/master/cli/drivers/CraftValetDriver.php */
{
    /**
     * Determine if the driver serves the request.
     *
     * @param  string  $sitePath
     * @param  string  $siteName

kant312

<?php

/**
 * @author  Quentin Delcourt <quentin@delcourt.be>
 * @date    2017-06-21
 *
 * This script will take a folder path in argument and will extract
 * all translatable strings from the Craft templates encountered
 * in the given folder. Each one of these will be
 * outputted to stdOut in CSV format.

croxton

<?php
// In general.php define an alias:

'aliases' => [
    '@baseUrl' => getenv('CRAFTENV_BASE_URL')
],

// In the CP, set the Base URL for each site to @baseUrl/
// When previewing, the CP will therefore always use the hostname the editor logged into as the base url for the preview
// (that happens with 'new' entries anyway regardless of base url, but existing entries use base url).

matthooks

See comment below:

ostark

class EventCatcher
{

    /**
     * @var array 
     */
    protected $classConstants = [];

    public function __invoke(yii\base\Event $event)
    {

samhernandez

{#
  Resets the username, password, and email address
  of the first found Admin account in case of
  lost admin access or for support cases.
#}
{% set values = {
  username: 'me',
  password: craft.app.security.hashPassword('mypassword'),
  email: 'me@site.com',
  passwordResetRequired: 0

dominictarr

Hey everyone - this is not just a one off thing, there are likely to be many other modules in your dependency trees that are now a burden to their authors. I didn't create this code for altruistic motivations, I created it for fun. I was learning, and learning is fun. I gave it away because it was easy to do so, and because sharing helps learning too. I think most of the small modules on npm were created for reasons like this. However, that was a long time ago. I've since moved on from this module and moved on from that thing too and in the process of moving on from that as well. I've written way better modules than this, the internet just hasn't fully caught up.

@broros

otherwise why would he hand over a popular package to a stranger?

If it's not fun anymore, you get literally nothing from maintaining a popular package.

One time, I was working as a dishwasher in a restu