James Hall

I only see options to disable movement (whatever that is) and prevent removal… is the restrict editing option a 6.1 feature only? Is there a way we can start using that now?

My FINGER is so worn out from these constant clicks guys… why is no one listening?

I have exactly the same question. Julia have you any new on this? ~James

SAVING MY ASS JASON THANK-YOU!!!

but this gave me MY IP:

<?php echo $_SERVER[‘HTTP_X_FORWARDED_FOR’]; ?>

207.210.203.168

Filed a trouble ticket in s2m just now.

207.210.203.168 is the IP of the server and not the client

We decoded the Policy s2m used to sign the URL and found that it is using the server’s IP in the AWS:SourceIP

This is causing an access denied when accessing the signed URL since the IP won’t match.

For ex upon decoding the signature associated with a file download we get this:
{“Statement”:[{“Resource”:”https://d3od88nicba67t.cloudfront.net/SD-os-gringos-parte-1-DOWN-SD.mp4&#8243;,”Condition”:{“IpAddress”:{“AWS:SourceIp”:”207.210.203.168/32″},”DateLessThan”:{“AWS:EpochTime”:1424884195}}}]}

have been online with amazon support for 2 days trying to find out why s2m is restricting ip that is requesting a s3/cf file.

any updates on this — seeing similar issue.

just those that upgraded form a specific level to another specific level. In this example, L0 > L2

Well that’s close — and that’s the feature that inspired my question. But i need something like this that is TRIGGERED by a different criteria (other than # logins):

> for members of level 2, that WERE PREVIOUSLY level 0

TRIGGER:2:https://www.whatever

i do.

Do you know if there is a script already developed?

Thanks Richard — i’m actually receiving these email notices from jetpack BUT they are being sent to a DIFFERENT address than the one configured on the Settings > Discussion page (!). How is this even possible?