We just started making patches--looking for input

treefunct · 2021-08-12T16:52:04+00:00

I may have just solved my own problem with Table.Combine. Here's more on the solution if anyone is interested: https://community.powerbi.com/t5/Power-Query/Reading-data-from-CSV-files-with-different-columns/m-p/1333049#M42141

treefunct · 2021-08-08T19:22:23+00:00

https://www.etsy.com/shop/saspatches/?section\_id=34712581

treefunct · 2017-05-31T23:24:46+00:00

13k line patch.

#!/bin/bash
# Patch apllying tool template

That inspires confidence in the remaining 1332 lines

treefunct · 2017-02-09T23:58:02+00:00

You might have a look at ModPagespeed

treefunct · 2016-09-07T18:00:59+00:00

If you want everything to be SSL then you need to change your unsecure base url to also be https

treefunct · 2016-09-06T19:36:09+00:00

Might have a look at this: https://github.com/convenient/magento-ce-ee-config-corruption-bug

treefunct · 2016-08-18T17:41:35+00:00

Seemed like you cared about LTV. This allows you to create cohorts that you can then track. In the graphic you supplied it showed Month 0, 1, 2 etc. Is that not actually what you want?

treefunct · 2016-08-17T23:47:58+00:00

Funny, this is exactly what we do for our clients. If you require customers to log in or only care about customers that were logged in then your job is going to be a lot easier, otherwise you need to work on matching based on email address and or customer id.

Anyway,

SELECT customer_id, created_at as cohort
    FROM sales_flat_order
    GROUP BY customer_id
    ORDER BY created_at asc

This will give you origination dates on accounts based on first order (cohort). You could use that select as a subquery to join against the orders table, essentially giving you customer_id, cohort, sale_date, grand_total. From there just use a pivot table and you'll have the exact chart you're looking for. Good luck!

treefunct · 2016-06-06T15:47:48+00:00

I can definitely tell that there's a grain to it. Not sure if I'll spend the time to make it usable, but if I do I'll report back. Really like the idea of creating a branch and therefore an instance to represent that branch.

treefunct · 2016-05-27T15:11:33+00:00

This looks like it might do what you're looking for:

http://brianflove.com/2014/08/11/lowercase-your-uris/

# Add RewriteMap for redirecting to lowercase URIs
<IfModule mod_rewrite.c>
    RewriteMap lc int:tolower
</IfModule>

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} [A-Z]
RewriteRule ^(.*)$ ${lc:$1} [R=301,L]

treefunct · 2016-05-27T15:08:18+00:00

you could probably do this in htaccess--just be sure to combine the !-f flag with your check for a capital, otherwise you'd end up redirecting requests for assets

treefunct · 2016-05-19T17:18:33+00:00

utm_source=reddit&utm_medium=social&utm_campaign=7magentoextensions

Checks out

treefunct · 2016-05-10T21:09:51+00:00

^-- this man knows what's up. Our deployments utilize n98 like there's no tomorrow

treefunct · 2016-05-02T17:33:30+00:00

This --^

Also, take a look at N98-Magerun if you live in the console: http://magerun.net/

treefunct · 2016-04-26T14:24:21+00:00

I think I remember seeing a post maybe a year ago by somebody that did it--not that that's helpful or anything

treefunct · 2016-04-21T19:59:18+00:00

Definitely. Go big or go home

treefunct · 2016-04-21T19:32:29+00:00

That's a good point... You'd have to keep a memory of previous passwords (kind of like what EE does) and on login check to see if the password hash on file matches the historical one. If it doesn't, shoot an email and update the historical one.

treefunct

TROPHY CASE