November 2011 - Bogiecom.com

Imagick Powershell Resize Images In Folder

Posted on November 18, 2011 by bc-admin

Here’s a quick one-liner to re-size photos if you have Imagick installed using PowerShell. It also renames the files with the dimensions specified:

PS C:\Users\SloshDev> gci("*.jpg") | 
      %{convert  $_.FullName -resize 500x500 $_.Name -replace '\.jpg$','-500x500.jpg'}

1 2	PS C:\Users\SloshDev> gci("*.jpg") \| %{convert $_.FullName -resize 500x500 $_.Name -replace '\.jpg$','-500x500.jpg'}

Ultimately ended up with this to rename the file based on the actual dimensions of the file in the end:

PS C:\Users\SloshDev> gci("*.jpg") | 
   %{convert $_.FullName -resize 500x500 -set filename:area '%wx%h' ($destination + ($_.Name.Trim("\.jpg") + "-%[filename:area].jpg"))}

1 2	PS C:\Users\SloshDev> gci("*.jpg") \| %{convert $_.FullName -resize 500x500 -set filename:area '%wx%h' ($destination + ($_.Name.Trim("\.jpg") + "-%[filename:area].jpg"))}

This is great if you want to do this within the file itself, however if you need to specify dimensions, source and destination directories, and specific image file extensions you could use a script like this:

$source = 'C:\User\SloshDev\My Pictures\'
     $destination = 'C:\User\SloshDev\My Pictures\500's\'
     $ext = "jpg"
     $size = "500x500"
     #Resize Images
      gci("$source*.$ext") | 
        %{convert $_.FullName -resize $size -set filename:area '%wx%h' ($destination + ($_.Name.Trim("\.$ext") + "-%[filename:area]." + $ext))}

$source = 'C:\User\SloshDev\My Pictures\'

$destination = 'C:\User\SloshDev\My Pictures\500's\'

$ext = "jpg"

$size = "500x500"

#Resize Images

gci("$source*.$ext") |

%{convert $_.FullName -resize $size -set filename:area '%wx%h' ($destination + ($_.Name.Trim("\.$ext") + "-%[filename:area]." + $ext))}

Append Extension to All Files in Directory

Posted on November 11, 2011 by bc-admin

IIS 6.0 did not save configuration files with “.xml” extension automatically. So I needed to add the .xml to the files. So this is what I did:

 PS C:\_old-IIS-site-configurations> Get-ChildItem *.com | Rename-Item -NewName { $_.Name + ".xml"; }

1	PS C:\_old-IIS-site-configurations> Get-ChildItem *.com \| Rename-Item -NewName { $_.Name + ".xml"; }

Nice, quick one-liner to quickly eliminate what would be a pain otherwise.

Miva Merchant Product Attribute Export – Update Pricing with Powershell

Posted on November 9, 2011 by bc-admin

If you’ve ever wanted a tab delimited list of product attributes and prices to update pricing, here’s one way:

Export product attributes through ‘Utilities > Export Data > Export Attributes to XML File’

When exporting choose ‘Replace All Mode
You will have to add a root level element around the xml generated by miva and the file:

PS C:\>$a = Get-Content .\provide.xml PS C:\>Set-Content .\provide.xml -value "<products>",$a,"</products>"

1
2

PS C:\>$a = Get-Content .\provide.xml
PS C:\>Set-Content .\provide.xml -value "<products>",$a,"</products>"

Now bring in file as xml:

PS C:\>$xml = [xml] (Get-Content .\provide.xml)

1

PS C:\>$xml = [xml] (Get-Content .\provide.xml)

Run this command to generate a tab delimited list of Product_Code, Code, & Price

PS C:\>$xml.Products.ProductAttributeOption_Add | foreach { $_.product_code + "`t" + $_.Price } > .\provide-list.txt

1
2

PS C:\>$xml.Products.ProductAttributeOption_Add |
foreach { $_.product_code + "`t" + $_.Price } > .\provide-list.txt

For more information on Powershell’s xml capabilities and how easy it is to use XML with Powershell visit Powershell XML on Code Project

.

Grooveshark Konami Code

Posted on November 9, 2011 by bc-admin

If you’re a fan of Grooveshark…

Give the Konami Code a try.

Would you like to see what other sites have some Konami effects? Check out Konami Code Sites.

If you use YUI on your site, there’s a built-in event for handling the Konami Code… see YUI Konami Event by Luke Smith

Magento Custom Form Field Validators using Prototype (MySQL Date Format)

Posted on November 9, 2011 by bc-admin

Here I needed to make sure that the user input was formatted correctly for a MySQL database. The javascript calendar code was set to automatically input the date into the text field in the correct format, but the user still had the option to type it in manually. This was the Prototype validator I used to verify that the user had entered it correctly as ‘YYYY-MM-DD’:

<script type="text/javascript">
  Validation.add('required-date-format','Please Enter date as YYYY-MM-DD. Click the calendar icon to select a date.', function(v) {
       return  !Validation.get('IsEmpty').test(v) && /^([0-9]{2,4})-([0-1][0-9])-([0-3][0-9])$/.test(v);  });
       var warrantyregistrationForm = new VarienForm('warrantyregistrationForm', true);
</script>

Validation.add('required-date-format','Please Enter date as YYYY-MM-DD. Click the calendar icon to select a date.', function(v) {

return !Validation.get('IsEmpty').test(v) && /^([0-9]{2,4})-([0-1][0-9])-([0-3][0-9])$/.test(v); });

var warrantyregistrationForm = new VarienForm('warrantyregistrationForm', true);

</script>