All types of magento works can be done in my company IT Live Web (Itliveweb.com). All types of extensions can be development by experienced programmers. In IT Live Web (Itliveweb.com) Development Company we have developed extensions to book the product weekly basis, Enter the products form user panel in magento, upload the flv and swf files for products at the place of images

I specialize in two things: building good-looking Magento webshops and ensuring good conversion rates (sales) for our clients. While trying to identify how to improve webshop conversion, I often use Google analytics to see what’s going on.

One of the nicest features of Google Analytics is the ‘Goal’ feature. It allows you to set goals (=sale or leads) for your site and track how successful you are. Via the sales funnel you can see quite nicely how you are doing and what you can do to improve your webshop conversion.

This short article describes how to set-up a ‘Goal’ for your Magento webshop in Google Analytics. It presumes you have already set-up Google analytics on your Magento webshop.

1) Login to Google analytics and select the site you want to set-up a goal for. Click edit.

2) On the next screen, click ‘Add Goal’

Setting-up a Google analytics sales funnel

3) Give your goal a name (for example ‘Sale’) and configure the screen as follows:

• Select ‘URL Destination’ as goal type.
• Select ‘Head Match’ as match type.
• The Goal URL, is the URL when a sale is completed. For Magento shops this is usually:
• http://www.yourdomain.com/checkout/onepage/success/
• In Goal value enter the average order amount you normally have in your shop.
• Then click:  ‘Yes, create a funnel for this goal’

4) Now we have to set-up the different steps in getting to the goal ‘Sale’

• In Step 1 we will add the following URL: http://www.yourdomain.com/index.php and call it ‘Home’ – This is your homepage
• In Step 2 we will add the following URL: http://www.yourdomain.com/checkout/cart/ and call it ‘Cart’ – This your shopping cart page (yahooo somebody added a product to his shopping cart!)
• In Step 3 we will add the following URL: http://www.yourdomain.com/checkout/onepage/ and call it ‘Checkout’ – The customers getting to this page actually want to proceed with the order. Only step left is to have them press ‘order now’

5) Click ‘Save Goal’.

Now do this take a piece of paper and write down how many customer you think actually complete your purchase process after they have reached the checkout process…..80%, 40%…10%? Let the statistics run for a couple of days, make sure everything is working as it should and check your sales funnel. It should look something like this:

What is your percentage and how can you improve it…..that’s the topic of our next post.

If you need any help on this post, or are looking for an experienced Magento partner, feel free to contact us!

Have you ever wondered how people are showing larger images for products on mouseover or mouse click using lightbox (very popular JavaScript library). Adding Lightbox to your magento theme is not difficult and by adding very little code to your theme you can get the Lightbox functionality easily. Lightbox will give the ability to highlight your products by showing lager image of the product along with brief description. Our approach will be based on default layout, you can change the theme name based on your selection.

Click Dere to read full article

Lot of people are heading down the road of integrating the WordPress and Magento. Probably everyone in web development has heard about WordPress. Personaly I like them, from Joomla, Drupal, WordPress… But there is that little something that makes WordPress far more loving in the eyes of the client. Not to start a flame here, lets get back to the topic. Due to the lack of the proper content management in Magento those who use WordPress can easily manage the (home page in this case) content trough WordPress and make it accessible in Magento CMS page (that you can set to home page in Magento).

Click Here to read full article

Seeing is believing.  One of the most visually appealing effects you can implement in a store is category thumbnails.  This is an example of the maternity wear department with images for all the categories.

The thumbnails were created using some code written by Jake Rutter, available here.  I’ve made some style changes.  One thing to watch is the length of the category name.  If it takes more than one line it could disrupt the rows.  Note in the baby gifts section the longest title is almost exactly the width of the column.  This is a little risky since different browsers may use a larger font.

I’ll explain more of the features I’ve chosen in future posts.

Dando continuidade ao nosso tutorial sobre Como Montar Uma Loja Virtual vamos discutir agora a escolha da plataforma (sistema) que você pode utilizar para criar o seu e-commerce.

Anteriormente abordamos os seguintes passos no processo de criação de um e-commerce:

• Artigos desta série já publicados
  Como Montar Uma Loja Virtual – Parte 1 – Escolha do Domínio
  Como Montar Uma Loja Virtual – Parte 2 – Definição do Mercado de Atuação
  Como Montar Uma Loja Virtual – Parte 3 – Escolha do Sistema – Soluções Open Source

Agora vamos abordar um terceiro passo muito importante que é a definição do sistema de e-commerce que a sua loja virtual irá usar para realizar vendas on-line. As opções são muitas e passam por sistemas open source ou lojas virtuais grátis, lojas alugadas ou sistemas proprietários ou soluções personalizadas. Todas tem vantagens e desvantagens e é justamente sobre isso que iremos falar.

A primeira idéia que muitos e-empreendedores tem é a de montar uma loja virtual usando uma plataforma open source por acreditarem que é uma opção inteiramente grátis. Tudo bem, grátis a plataforma é, mas quem vai instalar e configurar essa loja virtual? Alguém que é claro vai cobrar por isso, nada mais justo, pois acumulou conhecimento neste tipo de sistema. Aí então vem alguém com a seguinte “idéia brilhante”: o meu provedor de hospedagem “dá” essa loja virtual grátis e até instala. Uau!!! Tudo bem, instala através do “hiper super mega instalador automático” (oferecido pelas Organizações Tabajara) e pronto. Tá lá e se vire. Personalização e ajustes, esqueça, não existe e você vai sim ter que contratar alguém para fazer isso, se é que o provedor permite. Tem a outra “idéia brilhante” que é a de chamar aquele “sobrinho que mexe com internet”. O resultado é uma dor de cabeça monstra. Portanto a escolha por uma plataforma open source é sim válida, mas isso não quer dizer que você não vai gastar nada para tê-la. Em nosso curso de e-commerce estamos tentando dar uma visão geral sobre o assunto, mas o mais indicado mesmo é o aconselhamento profissional.

As Plataformas Open Source Existentes

Como dissemos em nosso artigo Lojas Virtuais Grátis, hoje em dia existem algumas plataformas open source bem interessantes, mas o grande problema é saber qual delas pode suprir as suas necessidades, se as necessidades de customização se adaptam ao seu orçamento para o projeto de e-commerce. Portanto, vamos analisar os dois sistemas para lojas virtuais mais comuns no momento, a plataforma osCommerce, velha conhecida de guerra já comentada em nosso site e a novata e super comentada Magento também já analisada e comentada em diversas seções do nosso site.

osCommerce

Um projeto que já conta com mais de 8 anos de desenvolvimento através de uma comunidade mundial. Desenvolvido em linguagem PHP utilizando portanto plataforma de hospedagem Linux. O sistema em si é bastante simples e justamente por essa simplicidade se transformou na opção número um para desenvolvedores e web designers durante muito tempo. Gerou uma série de variações como a ZenCart e outras justamente pela flexibilidade do sistema. É um WordPress do e-commerce. Serve para todo mundo, mas quem sabe manipular os códigos de programação consegue resultados impressionantes. É o sistema disponibilizado pela maioria dos provedores de hospedagem que oferecem esta opção de script.

Vantagens da osCommerce – Por ser uma plataforma com muito tempo de mercado, existem vários profissionais com experiência comprovada na instalação e atualização do sistema. Também por ser um sistema com mais tempo de existência possui inúmeras templates que podem ser compradas pela Internet e instaladas sem maiores problemas, desde que você tenha um profissional qualificado para auxiliar nessa instalação.

Operacionalização da Loja – O sistema é bem simples de ser administrado podendo ser feito por qualquer pessoa com conhecimentos mínimos de Internet, seguindo as instruções que você encontra em fóruns e sites na Internet ou pela pessoa ou empresa que instala a loja para você. O ideal entretanto é que você treine um funcionário ou você faça um curso para assumir esta função, pois administração de e-commerce é coisa séria.

Plugins – Vários e a maioria funcionando perfeitamente. Dá para dar uma boa turbinada no modelo original.

Desvantagens da osCommerce – O projeto passou por um longo período sem atualizações significantes em seus códigos o que o deixou um pouco desatualizado, mas não inviabilizado ou ultrapassado. Com o lançamento da plataforma Magento, parece que o sentimento de “orgulho ferido” tomou conta da comunidade de desenvolvedores e uma nova versão está a caminho. Vale a pena esperar, pois estas reações costumam ser avassaladoras.

Quem Oferece o Serviço – Se você conhece programação pode baixar os códigos direto da comunidade do site. Se for contratar alguém para fazer a instalação existem vários anunciantes em nosso site que prestam este tipo de serviço, basta pesquisar para saber qual deles oferece as melhores condições.

Nossa Opinião – Apesar de algumas críticas, acreditamos ser ainda a melhor solução em sistemas open source para quem está criando sua loja virtual, principalmente para quem está fazendo sua primeira incursão no e-commerce e optando por uma plataforma gratuita.

Site de Referência – osCommerce

Magento Commerce

Um projeto recente com aproximadamente 2 anos de desenvolvimento. Como a osCommerce, foi desenvolvida na linguagem PHP utilizando portanto plataforma de hospedagem Linux. O sistema é um exemplo de boa programação o que não significa que seja fácil, muito pelo contrário, sua programação é bem “cascuda” e exige do programador profundos conhecimentos de CSS, XML e outras linguagens. É o sistema disponibilizado atualmente para a loja virtual oferecida pela UOL Host.

É apresentada em duas versões, a Commun ity Edition que é open source e a Enterprise Edition, esta sim paga, mas com muito mais recursos. O preço da versão Enterprise separa os adultos das crianças; U$ 8.000 ao ano com algumas vantagens como por exemplo suporte direto com o pessoal da Varien, desenvolvedora do sistema original e básico. É coisa pesada mesmo.

Vantagens da Magento – O sistema é simplesmente a plataforma open source mais completa do momento com diversas opções de configuração e principalmente com ferramentas para divulgação da loja não encontradas em outras plataformas open source.

Operacionalização da Loja – O sistema é bastante complicado exigindo um bom conhecimento dos conceitos mais técnicos de programação.O ideal é que você treine um funcionário ou você faça um curso para assumir esta função, pois administração de e-commerce é coisa séria e principalmente quando se fala da plataforma Magento.

Plugins – O projeto é relativamente novo, por isso não tem ainda muitos plugins. Para turbinar a loja exige um bom conhecimento não só de programação como da plataforma em si.

Desvantagens da Magento – Ainda é um sistema desconhecido da maioria dos programadores e por isso é bastante difícil encontrar profissionais realmente qualificados para instalá-la. A quantidade de templates disponíveis ainda é muito restrita o que ainda limita um pouco as opções de design.

Quem Oferece o Serviço – Se você conhece programação pode baixar os códigos direto da comunidade do site. Se for contratar alguém para fazer a instalação existem vários anunciantes em nosso site que prestam este tipo de serviço, basta pesquisar para saber qual deles oferece as melhores condições.

Nossa Opinião – Em termos de recursos tecnológicos é sem dúvida a melhor plataforma do momento. A única restrição é a de que para operá-la é necessário alguém com profundos conhecimentos de programação e funcionamento dos diversos sistemas de divulgação de lojas na Internet como o Google. Não é nada que a contratação de um bom profissional da área não possa resolver, mas também não é nada barato. Talvez para uma primeira incursão no e-commerce esteja acima do orçamento previsto pelo e-empreendedor.

Site de Referência – Magento Commerce

Bem, sobre as opções de plataformas open source mais conhecidas acho que é o suficiente para podermos tomar uma decisão. No próximo artigo vamos analisar a opção por lojas virtuais alugadas. que é mais uma opção para quem está pensando em abrir uma loja virtual.

Vi no http://www.blogdoecommerce.com.br/

I recently completed my first e-commerce website for a local luxury product called AVOOVA. The client wanted a sophisticated and elegant site for his brand of stylish products. I researched Magento and felt that this cutting edge software would be the way forward. Magic Zoom was used for the zoom effects as the client wanted the website to also depict the beautiful detail and intricate designs of the AVOOVA products.  I did all the design and project managed the AVOOVA website. Development was outsourced to a very talented developer (Johann Visagie) who has experience with Magento. For the payment facility we have used EFT, but in the second phase of the website we will be incorporating the payment gateway.

See the AVOOVA site here: www.avoova.net

Seperti dalam berbagai media online ada penawaran pelatihan toko online, maka yang tampak baru sekedar penawaran pelatihan install softwaere toko online, artinya baru sebatas membangun toko online sebagai benda. Belum memiliki roh yaitu strategi bisnis dan pemuas pelanggan. Namun saya sedih sekali ketika pelatihan membuat toko online baik dengan oscommercer, prestashop, magento, zen cart dll itu diberi judul stategi bisnis online. Kenapa? Iya karena pelatihan itu baru mengarah pada skill IT saja sedangkan masih ada banyak skill yang dibutuhkan untuk memajukan toko online, antara lain:
Skill BIdang Keuangan
Skill ini dibutuhkan dalam bisnis toko online untuk menagarah pada sejauh mana pengelolaan toko online menjadi unit yang profitable, artinya bisa memperoleh laba jadi tidak hanya menerima uang. Banyak toko online masih menghitung bisnisnya sekedar menerima uang. Skill Bidang keuangan harus bisa memperhitungkan, biaya operasional, biaya promosi, dan perencanaan keuntungan jika ada diskon, jika biaya tak terduga untuk return, klaim pengiriman dll. Pentingkan bidang keuangan ini? Kalo anda ingin sukses seperti EBAY.COM anda wajib menetukan arahnya. Sehingga menentukan diskon bukan dari feeling saja, namun dari prediksi keuntungan setelah memperhitungkan biaya operasional. Emosional dalam arus diskon karena pesaing maka menyebabkan frustasi sesaat jika ternyata keuntungan sangat minim tidak mampu diputar kembali dananya. Ingat ini bisa dipelajari sambil jalan tapi harus dipahami. Bidang keuangan juga mampu mengawasi perkembangan atau keruagian secara cepat.
Skill Bidang Pemasaran
Ada beberapa perusahaan yang begitu menggantung kan usahanya terhadap aspek pemasaran tentu juga dalam toko online, karena yang dijual di toko online mudah sekali di duplikasi oleh orang lain, dengan harga yng mungkin lebih murah. Saya ingat bahw ada produk di Yogya bidang kerajinan yang dijual online, dalam 3 hari sudah diduplikasi di toko online milik orang jawa barat dengan harga lebih miring, karena memang kedekatan bahan baku lebih unggul di Jawa barat. Sehingga pemasaran merupakan hak yang penting agar transaksi terus berjalan, awareness juga tetap berlaku setiap saat. Pemasaran yang baik tentu adalah bukan sistem menjual saja, namun lebih kepada mengingat pelanggan untuk tetap puas dan tetap loyal. Produk boleh sama, harga bisa lebih mahal namun karena konsen dalam membangun kredibilitas, pelanggan tetap loyal.
Skill Perilaku Konsumen
KEtika semua orang membuat website untuk toko online maka, berbondong-bondong orang mengikuti pelatihan training computer dan programming toko online namun sadarkah bahwa semua pelanggan tidak akan mengakses lewat web dengan akses HTTP bisa saja karena ada PDA,HP, Blackberry yang canggih maka model WAP, MOBILE ACCESS lebih disukai karena kecepatan, kemudahan dan murah akses. Perangkat PDA,HP, Blackberry memang semakin sebanding dengan Laptop, tapi itu kan fitur, nah untuk lebarnya layar maka PDA,HP, Blackberry tidak bisa menandingi Laptop atau PC. Perilaku ini juga berdasar segmentasi yang tepat.
Skill untuk Management Information System
Tidak harus dari orang Informatika untuk bisa menguasai Management Information System, karena toko online yang mempunyai kekuatan yang baik adalah toko online yang menggunakan Management Information System yang berorintasi pelanggan. Misal masing masing SOurcode antara Prestashop. Magento, Zencart, OScommerce menawarkan Management Information System yang berbeda. Atau anda mau membuat sendiri web toko online maka Management Information System adalah dasar yang terus diperbaiki, bahkan EBAY yg besar pun terus menyempurnakan aspek Management Information System. Facebook pun penyempurnaan untuk bidang Management Information System tetap dijalankan, untuk akses yang cepat, mudah ,murah, simple, namun tangguh dalam melayani transaksi
Skill Ekonomi
Ini hanya sekedar tambahan yang lebih mendorong faktor apa yang akan booming dalam produk-produk masa depan dan tetap aman sampai waktu tertentu. Misal dengan memanfaatkan situs Desperindag dan Bursa Ekspor impor dan gejolakperekonomian suatu Negara maka bisa menentukan lamgkah, minimal mampu mengalihkan arah penjualan dari suatu Negara yang tiba-tiba hancur bangkrut ke Negara yang lebih kondusif. Dengan Skill Ekonomi prediksi trend akan lebih mudah, misal lebih prospeks mana, antara bisnis toko online mebel ekspor atau bisnis toko online hasil kerajinan.
Ada 5 skill lagi yang perlu dalam membangun sukses nya toko online, akan disampaikan lain waktu. SUkses dengan toko online yah, aka nada artikel toko online di masa-masa mendatang.
Tidak perlu gusar semua skill uuntuk membangun skill toko online dengan sukses bisa dipelajari/dibangun secara perlahan, yang terpenting mulailah dengan membangun toko online dari hal yang terkecil.

O magento tem um tipo de produto bem interessante: são os “produtos agregados” ou bundle products.
A idéia deste tipo de produto é criar kits promocionais, também chamados de “venda casada”.
Funciona da seguinte forma:
1. Cadastramos 2 produtos de quaisquer tipos.
2. Cadastramos 1 produto do tipo bundle, onde informamos os produtos que farão parte do kit e seu preço promocional. =)
Desta forma, implementamos uma promoção de kit ou venda casada.
Sds,
Noca.

Currently Magento is one of the most popular open source ecommerce solutions. Its user-friendly interface and usability suit online store owners perfectly.

So what are the main advantages of Magento over the other shopping carts?

Magento offers a great number of options including layered one page checkout.  Using Magento dropdown menus for prices, products, and colors potential customers save their time for choosing the right product. They don’t have to wander from one page to the other in order to find these details.

Compare products option allows future customers choose several products from Magento online store and compare them in order to buy the most appropriate one. Each customer can also make a review on the products he/she has purchased from Magento store. Reading product reviews help people make the right choice.

Purchasing products in Magento store customers can send them to multiple shipping addresses within one transaction. It’s easy to shop at Magento online stores so they bring good profits to Magento store owners. It’s also easy to change currency and language while buying something at Magento store. It means international clients have nothing to worry about.

As everyone knows Magento is free to download so everyone who thinks of starting an online store can give Magento a try. Download Magento

You want to know more about magento:

1. Magento Feature List : Click here
2. Magento Screenshots : Click here
3. Magento Demo : Click here

Long time awaited but it’s finally here, Magento cart! This fully operational cart has multiple retail options to boost up the sales. All the purchases are greatly presented in the reports to let you gain control of your business.

The back end is very professional and easy to get around. I think that Magento developers thought about every option in the cart that possible can be used in the online retail store.

See below our use of Magento cart on the site of www.galwaygirl.com and www.viviscal.fr

Galwaygirl.com

Viviscal.fr

У Magento є така не дуже приємна функція, як компресування (зменшення їхньої якості) малюнків, які завантажуються з бекенду. Йдеться про ті малюнки, які зменшуються до потрібних розмірів. Якщо якість малюнків є критичною для магазину (наприклад магазин листівок) то необхідно знаходити вихід з ситуації. На офіційному форумі є приклад вирішення цієї проблеми. Дана інструкція стосується версії Magento 1.2.x.x і вище.

Крок №1 Знаходимо файл File: lib/Varien/Image/Adapter/Gd2.php.

Крок №2 Коментуємо 80 рядок

//call_user_func($this->_getCallback('output'), $this->_imageHandler, $fileName);

замість нього вписуємо,

if ($this->_fileType === IMAGETYPE_JPEG) { call_user_func($this->_getCallback('output'), $this->_imageHandler, $fileName, 99); } else { call_user_func($this->_getCallback('output'), $this->_imageHandler, $fileName); }

де “99″ — це максимальна величина якості картинки (можна поставити меншу, якщо потрібно)

Крок №3 Йдемо в Панель Адміністратора Admin->System->Cache Management і тремо кеші малюнків Images Cache-> Clear. Також раджу потерти кеші браузера.

Підказка: Будьте уважні – при подальшому піднятті версії даний хак потрібно буде прописати знову.

Amig@s amantes de la tijera y recorte del show bizz bienvenidos a una semana mas de chisme del espectáculo.

Iniciamos esta columna con un noticia triste y que pone de luto al mundo del deporte (que por “X” o por “Y” siempre esta ligado al espectáculo) ya que Antonio de Nigris, gran futbolista Mexicano murió el día de Ayer victíma de un ataque al corazón mientras dormía.

En este video en ESPN hablan sobre que Antonio sufría una malformación congénita en su corazón y que incluso le habían prohibido jugar Futbol.

Cambiando rapidamente de tema, resulta que Enrique Iglesias da de que hablar y ahora MTV se hace de la boca chiquita. En su nuevo video realiza una “masturbacion” mientras ve un canal de llamadas sexuales ademas de candentes escenas amorosas. ¡picoso!

Pero es de verdad algo molesto que te censure un canal que habla de Homosexualidad abierta y plena a las 4 pm con muestras claras de la falta de noción que tienen en este tema, que te muestre el lado negativo de la juventud disfrazada con un “viva la juventud” y que algo que es normal y que todo el mundo realiza sea “prohibido”.

Por ultimo, ¿se acuerdan de Geena Davis?, aquella mujer que salió en películas como Stuart Little, Beetlejuice o Thelma y Louis, pues acaba de ser criticada terriblemente por los paparazzis por su sobre peso.

Cuando en el 2006 se veía espectacular como lo muestra el video, ahora luce así.

Esta mujer ha sido arquera olímpica, y miembro de la asociación de las personas más inteligentes del planeta, pero por sus embarazos no ha podido recuperar la figura.

En fin vamos a un corte comercial y regresamos con Sharlee Trujeque desde los Estados Unidos.

Amigo azotados y estrellados, comenzaremos la semana con un parche en la nariz (después del trancazo que me di por tropezarme, auch) con los resbalones desde el gabacho…

Guapa, famosa y extorsionada…Cindy Crawford y su esposo Rande Gerber fueron víctimas de una extorsión por $100 mil, pues el modelo Edis Kayalar les pidió la exorbitante cantidad de dinero para no publicar una fotografía de su hija que fue tomada por una niñera de la pareja. Kaia Jordan, hija de la modelo, aparece en la fotografía atada a una silla y usando “ropa reveladora”, según describen los documentos archivados en la Corte Distrital de Estados Unidos. La representante de Crawford, Annett Wolf, aseguró que la imagen fue tomada cuando Kaia tenía 7 años sin que la modelo lo supiera, aunque Kaia dijo que la fotografía se la tomó su niñera durante un juego de “policias y ladrones”. Edis “Eddie” Kayalar, conocido de la niñera, robó la imagen y trató de conseguir dinero de la pareja. El modelo fue deportado por violar las leyes de inmigración hace tres meses, aunque después volvió a llamar al matrimonio. El último contacto con él fue un correo electrónico en que le prometían el pago, enviado por instrucciones del FBI. Gerber finalmente consiguió que Kayalar le diera la foto y le pagó mil dólares en efectivo, agrega. Pero el alemán luego exigió más dinero y dijo que tenía otra copia de la imagen. La niñera, de quien no se ha dado a conocer su identidad, no ha sido acusada de ningún cargo. Cyndy Crwaford y Rande Gerver se casaron en 1998 y son padres de dos niños: Kaia Jordan, ahora de ocho años y Presley Walker, de 10.

Ah que la canción….El padre de Michael Jackson no pretende darse por vencido en su pelea por obtener alguna pensión de la fortuna de su hijo muerto y decidió llevar a un tribunal de apelaciones de California (oeste) su molestia porque el artista lo dejó fuera del testamento. Según documentos judiciales divulgados el lunes, Joe Jackson presentó un recurso para que la corte de apelaciones se pronuncie sobre su pedido de una pensión de la fortuna de Michael Jackson, muerto el 25 de junio en Los Angeles de un paro cardiaco a raíz de una sobredosis de sedantes recetados. El patriarca de los Jackson está indignado luego que el 10 de noviembre un juez de la Corte Superior de Los Angeles indicó que no tenía ningún poder para impugnar a los albaceas de la herencia de su hijo, indicaron los documentos divulgados por el sitio especializado en las estrellas TMZ.com. El cantante de “Human Nature” dejó su herencia a su madre, Katherine, sus tres hijos menores de edad y a un Fondo. Joe Jackson había pedido una pensión para ayudarlo a afrontar sus gastos mensuales, estimados en más de 15.000 dólares, y se quejó de que los administradores del legado del artista no le fijaran una pensión similar a la otorgada a la madre. Pero el juez de la Corte Superior de Los Angeles, Mitchell L. Beckloff, se negó a fijar una audiencia para atender esta solicitud al afirmar que existía información suficiente para ejecutar las decisiones del testamento tal como han hecho sus albaceas, John Branca y John McClain. “El señor Jackson no tiene nada que tomar bajo este testamento”, dijo el juez Beckloff, y agregó: “Esa fue una decisión que tomó su hijo. No veo cómo él se siente afectado por los señalamientos de Branca o McClain como administradores”. Brian Oxman, abogado del patriarca de los Jackson, dijo que esperaba que una corte de apelaciones les diera la razón. Joe Jackson, de 81 años, recibe 1.700 dólares mensuales en concepto de pagos de la seguridad social, según los documentos. Tiene diabetes y sufrió un ataque en 1998. Un presupuesto mensual presentado en los documentos judiciales enumera más de 15.000 dólares de gastos, incluidos 1.500 dólares de alquiler, 2.500 en restaurantes y 5.000 dólares para hoteles y billetes de avión.

Pasele, marchanta, escoja la que más le guste….Dos casas que pertenecían al actor estadounidense Nicolas Cage fueron rematadas en Nueva Orleans por problemas con el pago, anunció este sábado el sitio de internet de la revista People. Las dos propiedades, situadas en el “barrio francés” de la metrópolis de Luisiana, fueron rematadas por un total de 4.5 millones de dólares (3 millones de euros) el jueves, según la misma fuente. A medidados de octubre, documentos judiciales mostraron que el actor había demandado a su ex agente acusándolo de haberlo arruinado efectuando inversiones de alto riesgo. Según el texto de la demanda, el actor le debe al fisco estadounidense 6 millones de dólares por impuestos atrasados. En abril, Nicolas Cage anunció que había vendido un castillo que poseía en Alemania a causa de la crisis económica.

En cine “2012″: Nunca antes una fecha había sido tan importante para tantas culturas, para tantas religiones, para científicos y para Gobiernos. “2012″ narra la épica historia del cataclismo global que supone el fin del mundo y de la heroica lucha de aquellos que consiguieron sobrevivir.

En fin, cuidando nuestros pasitos de futuros trancazos y resbalones, seguiremos el recuento hasta la próxima semana.

Muchas gracias Sharlee, ahora es turno de Hector Ledezma desde la Cd. De México, que cada vez tiene mas hoyos.

El reciente puente me fui unos días al puerto de Acapulco, donde además del rico clima, fui al concierto de Magneto, sí, a ese, no pagué aclaro, me invitaron y acepté, reconozco que en otras circunstancias habría dicho que no, pero se prestaba el momento, y tenía curiosidad por ver como sonaban, y la verdad pues poca gente, mucha adrenalina y dieron un show corto, pero pasaron por sus éxitos, sí, por eso duró cerca de una hora.

No son para nada de mis tiempos, era yo muy peque, pero recuerdo muchas de sus canciones, Vuela vuela, A la puerta del colegio, Para siempre, Tu libertad, Malherido, entre otras.

Todos lucían obvio con los años encima, si acaso Alex era de los que lucía mejor, Alán con varios kilos de más, Tono que si no lo hubieran invitado no pasaba nada, Mauri pues un poco más arrugado, y Elías pues sigue sin cabello. Deleitaron a fans que en su mayoría eran mujeres de 30 años, unos cuantos grupos de jóvenes y unos cuantos perdidos que no se sabían ni vuela vuela.

Aquí un video de sus años mozos, cuando las chavitas estaban de su lado, ahora realmente no queda casi nada de aquellos años, señal de que segundas partes nunca fueron buenas y señal de que es mejor a veces quedarse con los recuerdos y éxitos a intentar que haya un poco de lo que fue.

Y siguiendo en la onda de las segundas partes, en las telenovelas ya no es novedad y ya debemos hablar de cuartas y quintas, sino pregúntenle a Corazón Salvaje. Sin embargo, una de las novelas que nunca se han hecho dos veces, Cuna de lobos, marcó un hito, gracias al libreto y a la villana María Rubio, que en su papel de Catalina Creel, inmortalizó su personaje, al grado de llegar a perder su propia identidad, pues la sobrepasó.

Desde hace tiempo se maneja una posible adaptación, pero el nombre de Catalina Creel les hace ruido y sombra, y no se deciden por quién puede ser la actriz que logre por lo menos acercarse a ese gran papel. Ahora se manejan nombres como Jacqueline Andere, que es muy buena, y que es la que más suena.

Aunque se manejan nombres como Alma Muriel, que me topé en una obra de teatro y que luce bien, y que también es una buena villana, además de Silvia Pasquel, Rebeca Jones que sería bueno verla de nuevo, aunque no sea tan grande, y hasta Victoria Ruffo, que si no quiso o no pudo con el papel en En nombre del amor y se le quedó a Leticia Calderón, menos podrá con este papelón, toca esperar cuál de todas se queda.

Muchísimas gracias a todos los que hacen posible este espacio, gracias por sus comentarios, chismes y críticas, gracias a Sharlee Trujeque y a Hector Ledezma, Yo Soy Daniel Monti y nos vemos la próxima semana. Abur.

We deal in “LAMP” Technologies.

We are expert in Application development & Customization of Open Source platforms.

Our coding teams have a lot of experience in building web applications for e-learning, e-commerce, content management, realty, CRM and other domains. We are also skilled in modifying and integrating popular open source applications .

Our work Specialty:

1- PHP and Mysql .
2- Full Joomla Customization (Theme ,Component,Module,Plugins).
3- Full Drupal Customization (Theme,Modules).
4- Full Moodle Customization (Theme, Modules).
5- Full Magento Cutomization.
6- Joomla + Moodle Integration.
7- Drupal + Moodle Integration.

For development work we put in a lot of effort to work together with clients to understand and clarify scope. Thereafter, we adhere to a transparent, process-driven development methodology:-

- Analysis
- Construction
- QA
- UAT

Url : www.maantech.com

We are always ready for working with you.

Додаємо статичну сторінку в Magento

Сьогодні розглянемо проблему додавання статичної сторінки в Magento.

В переважній більшості випадків це такі сторінки як «Про нас» (About Us), «Інформація про доставку» (Shipping information), «Приватність та безпека покупок» (Privacy & Security), «Повернення товару» (Return Policy) і т.д.

CMS сторінки можуть містити відформатований HTML чи простий текст.

Поїхали!

Йдемо в «Панель адміністратора»(Admin Panel) www.yourmagentosite/admin і логуємося

Логуємося в Панель адміністратора

Manage Pages

Заходимо в CMS->Manage Pages і натискаємо Add New Page. Ми перейдемо на нашу новостворену сторінку та розглянемо її детальніше.

Під Page Information ми бачимо три закладки:

1. General Information (загальна інформація)
2. Custom Design (індивідуальні налаштування макету)
3. Meta Data (мета інформація)

Закладка General Information

• Page Title — Назва сторінки, яка буде відображатися в заголовку браузера і в списку сторінок в CMS->Manage Pages.
• SEF URL Identifier — це ідентифікатор посилання на вашу сторінку. Якщо ви ввели туди about-us то шлях на вашу сторінку буде мати наступний вигляд www.yourmagentosite/about-us
• Status — Enabled: сторінка активна, Disabled: вимкнена.
• Content — поле в яке ви вводите контент, що повинен бути на сторінці.

Створюємо нову сторінку - загальна інформація

Закладка Custom Design

• Custom Theme — можна вибрати для сторінки іншу тему (ми ж залишаємо це поле так як є)
• Custom Theme From/Custom Theme To — можна задати початкову і кінцеву дату активності нашої вибраної теми (теж залишаємо поля так як вони є)
• Layout — тут вибираємо який темплейт ми будемо використовувати: з однією колонкою, з двома чи трьома. Ми вибрали з двома колонками в якого ліва колонка вужча.
• Layout Update XML — дуже важливе поле. Дає змогу робити зміни в макеті (layout), які впливатимуть тільки на цю сторінку. Наприклад, можна додати додатковий клас на <body> чи підключити інший темплейт сторінки.

Створюємо нову сторінку - Custom Design

Закладка Meta Data

• Keywords — додаємо ключові слова які будуть відноситись до цієї сторінки.
• Description — додаємо опис сторінки (якщо потрібно)

Створюємо нову сторінку - Meta Data

Натискаємо «Save Page» і наша сторінка створена.

Подібні статті:

• Як створити та редагувати статичний блок Static Block в Magento?

There are numerous ways to integrate Magento with Drupal. Here I will share my experiences while working on that with very smart people at Optaros. I don’t take credit for all the points in this post, because they are the product of the whole team.

The motivation for this kind of integration is the innovative look into where e-commerce is moving. To get a grasp of it look at OCentric. To keep it short, content is free advertisement for products. It allows customers to get more input about products and provides the meat for search engines to index.

Briefly, there are several main approaches to integrate Drupal and Magento:

1. let Magento be the main component, while leaving Drupal just as a subcomponent
2. let Drupal be the main component, and have Magento as an e-commerce  module
3. let  both Magento and Drupal be main components

These are general approaches and each of them have different pros and cons. They will be further detailed by usecases, complexity, technicalities, etc. in the following sections.

Moreover, we will release much of the code as open source, so it’s not only a theoretical discussion here:)

Magento as the Main Component

This is probably the most acceptable approach in terms of implementation complexity. Moreover you can choose different level of complexity to implement.

The straightforward solution is to integrate on the service layer. Meaning that whenever we are on the e-shop product page we have to call a Drupal service to bring related content, for instance blog posts. The same holds for category pages. How to do that:

• Create a Drupal module that allows you assigning categories and products  to a content node in Drupal
• Implement XML-RPC client on Magento side and use it to talk to services on Drupal in order to pull the content (e.g. using view.get or node.get funuctions)
• Rewrite the category and product controllers on Magento to take the content from Drupal into account

There are some challenges in taking this way. They are mainly for those who want to implement features in a generic way. Specifically, whenever you add a CCK field or a feature like rating to a content type, you have some work to do on the Magento side. Namely, you need to modify layout and write templates to handle this additional data coming from Drupal. Hence it’s pretty cumbersome to use Drupal community contributed modules as you need to do some coding on Magento side for every new Drupal feature. This is quite easy when the content from Drupal is read-only, but as soon as you want commenting, rating, flagging, etc. it becomes an issue, because you need to not only redo rendering on Magento but also map the functionality.

A more complex path to take  is to integrate the whole Drupal rendering engine into Magento, however, this means a very tightly coupled architecture… Still, if you plan to use many many many of the Drupal features it may make sense. This will require writing a Drupal module for Magento that will adapt every Drupal core function to Magento. Could end up as a very complicated solution.

We chose the XML-RPC because of the given time frame and specific requirements. Normally a product or a category will be associated with a very specific set of content types, and therefore the fully generic solution may not pay off.

By the way there is already a CMS module for Magento as part of the core. And the question is why would one want to struggle integrating Drupal instead of using that CMS module? Moreover, with enterprise 1.6 version of Magento the module offers quite cool features. Some things from the top of my head to consider:

• Drupal has a solid community, and it is more stable and feature-rich than the Magento CMS module will ever be (of course it’s good as soon as you make the Drupal-Magento integration reasonably flexible)
• There is the CCK module that allows to very quickly add additional fields to a content type and make it available to the content producing team
• Content versioning, workflow, etc. is easy in Drupal
• …more ?

Drupal as the Main Component

This approach has been already taken by others and you can start digging for it here. We’ve tried out the available modules but didn’t stick with them… Basically there the implementation is based on the notion of synchronizing Magento products, categories, orders, etc.  into Drupal using a cron job.

In general, although Drupal-as-the-main-component approach in the end may give a lot of  flexibility, it may be too complex to implement. Imagine that the whole Magento frontend functionality needs to be rewritten for Drupal. Magento would then only be an e-commerce backend (the admin part) accessible via Web services. Of course you’d be able to use plenty of Drupal modules as well as flexible templating without any hassle, have better performance, and many other goodies but it just looks too expensive to implement.

Still, bringing only a part of Magento into Drupal makes a lot of sense (as in that module that synchronizes products and orders into Drupal using cron job). In this case it’s a decision to make whether the site is more about content or about commerce. When it’s about content, then you don’t really care about SEO for products, fancy business logic, etc.

Both Mangento and Drupal as the main Components

This is reasonable when the content will be displayed on the Drupal site and e-shop on the Magento site. Meaning that no proxying for content happens behind the scenes. So if a product has a blog post attached, then on the product page you’ll have a link (maybe even the post itself loaded using Ajax call) and clicking it will open a Drupal page with that blog post.

One of the challenges here is to maintain two different themes in order not to harm user experience. So that when the customer clicks on the blog link inside the product page the blog is displayed with the same look and feel as the shop. For that you can’t avoid coding on two different frameworks. Apart from theming SEO will have to be also maintained on both components.

Another challenge would be the ability to mix content with product information on the same page. Some kind of communication on the service layer will be necessary for that, which means that it’s not really reasonable to use this dual approach with such a usecase present.

It may make sense, however, to take this path when there are only some of the things to be shared between both components, e.g. users, and everything else is completely separate. For example, when a company has an e-commerce site, a customer community site, and a corporate site.

Additional Points for Integration

The end user display is only one part of the story. When you integrate this kind of monster systems to work seamlessly you get trapped with other things besides templating.

One of them is single sign on. A good thing to do here is to use CAS. Drupal already has the CAS module. Magento, however, needs one (we’ve been writing one). The good news that all the low level protocol implementation is available for PHP as open source.

Another thing is search. Independently of the integration approach chosen eventually you want to search for products and content in the same search box. This may become pretty challenging but it’s not impossible. We’ve got a proof of concept for the store front in Magento, where we leverage Solr search. It performs really well for our suggest box functionality.

Calendar shows furthur up on the page. It has to show underneath the text filed.

Solution

Go to file js/calendar/calendar.js

Somewhere around line number 1459 spot the lines

if (Calendar.is_ie) {
br.y += document.body.scrollTop;
br.x += document.body.scrollLeft;
} else {
br.y += window.scrollY;
br.x += window.scrollX;
}


change this to

if (Calendar.is_ie) {
br.y += document.body.document.documentElement.scrollTop;
br.x += document.body.document.documentElement.scrollLeft;
} else {
br.y += window.scrollY;
br.x += window.scrollX;
}


Courtesy: Magento – IE hack for calendar.js positioning – ‘How do I’ Questions – eCommerce Software for Growth

I’ve been doing some work with the Magento e-commerce platform lately and my task was to create a new payment method to use during the standard checkout process.

I’ve come to the conclusion that Magento is very annoying to develop for if you know nothing about the platform. Yes the platform is open source but they also have a commercial version, therefore it seems they have tried to make it hard for you to know the complete ins and outs of the system. I.E. if something seems like too much of a task to develop, a company would likely purchase the commercial version and get it developed by the platform developers rather than do it themselves.

You also have to remember that Magento is built on top of the Zend framework, so when you are developing for it documentation does not all reside on the Magento site, you will have to look into how the Zend framework works as well.

Finally, note that by default the Magento checkout process uses AJAX to submit the form, making this a very annoying module to debug. Thankfully Magento makes it easy to log values and throw exceptions which ‘pause’ the checkout process.

After much searching online, it seems that any available tutorials for custom payment methods either don’t work, are incomplete or worked in previous versions but are now updated. I developed this using version 1.3.2.2 of Magento.

I’m writing this tutorial with the intention of it being the definitive guide to creating a custom payment method.

* You’ll notice that I’m using PHP comments in XML code snippets. This is because WordPress isn’t letting me post normal XML comments You’ll have to change/remove them if you plan to copy and paste.

Prerequisites

1. Creating the module

2. Configuration through the admin

4. Payment adapter model class

Prerequisites

There are a few things you need to note now to avoid confusion later down the line.

For your module, you need the main name and a simpler alias for it. I.E. if your module was called MyPaymentMethod, your alias could be mypayment. Keep the full name and the alias in mind. The full name will be used in class and folder names but the alias will be used when referencing the module anywhere else.

For this tutorial I will be using ModuleName for the full name, modulename for the module alias, and MyModules as the module namespace.

Magento names it’s classes after their path. I.E. you are going to have a class which handles all of this payment method logic, and it’s path will be something like app/code/local/MyModules/ModuleName/Model/PaymentLogic.php. It’s class name will be MyModules_ModuleName_Model_PaymentLogic. Remember this as it helps when trying to figure out where to find a referenced class etc.

1. Creating the module

OK so first we need to create the initial module and make sure Magento knows that it exists. Lets create the folder structure;

app/
---- code/
-------- local/
------------ #1 MyModules
---------------- #2 ModuleName
-------------------- #3 Block
-------------------- #4 etc
-------------------- #5 Model


#1 In Magento terms, MyModules would be the module’s namespace. I.E. you’ll likely have one namespace for multiple modules. The namespace can be called anything but should be UpperCamelCase. If you take a look in app/code/core you will see a folder called Mage – this is the namespace for most of Magento’s core modules.

#2 This is your actual module name. This should be UpperCamelCase.

#3 This folder is used to contain block classes that are used in your module.

#4 This is where your module configuration will go.

#5 The class that handles all of your payment gateway logic will go here. This is also a good place to put any third party libraries or custom classes you may use.

config.xml

Create the file config.xml in app/code/local/MyModules/ModuleName/config. This file is the main module configuration file. For now, you want it to look like this;

<?xml version="1.0" encoding="UTF-8"?>
<config>

    /**
     * register the full module name and it's
     * version
     */
    <modules>
        <MyModules_ModuleName>
            <version>0.1.0</version>
        </MyModules_ModuleName>
    </modules>

    /**
     * global module configuration
     */
    <global>

        /**
         * register the module's model group
         * note that we use the module's alias
         * mentioned in the prerequisites
         */
        <models>
            <modulename>
                <class>MyModules_ModuleName_Model</class>
            </modulename>
        </models>

        /**
         * set which resources the module will
         * use when setting up, writing to the db
         * and reading from the db. we're going
         * to use the core connections.
         */
        <resources>
            <modulename_setup>
                <setup>
                    <module>MyModules_ModuleName</module>
                </setup>
                <connection>
                    <use>core_setup</use>
                </connection>
            </modulename_setup>
            <modulename_write>
                <connection>
                    <use>core_write</use>
                </connection>
            </modulename_write>
            <modulename_read>
                <connection>
                    <use>core_read</use>
                </connection>
            </modulename_read>
        </resources>
    </global>
</config>

Now the module has it’s basic configuration but Magento doesn’t care because the module is not yet registered.

MyModules_All.xml

Create the file MyModules_All.xml in app/etc/modules. This is where we register the module. You want this file to look like this;

<?xml version="1.0"?>
<config>
    <modules>
        <MyModules_ModuleName>
            <active>true</active>

            /**
             * for now we're telling the system that
             * this module is just local, it's not a core
             * or community module and resides in
             * app/code/local.
             */
            <codePool>local</codePool>
        </MyModules_ModuleName>
    </modules>
</config>

The module is now registered and Magento knows about it. But what can you do with it? Well, this is a payment method module, so we need to register it as a usable payment method. We also need to be able to set what fields are configured in the administration section that can be used when authenticating with the payment gateway etc.

2. Configuration through the admin

system.xml

Create the file system.xml in app/code/local/MyModules/ModuleName/etc. Here we will tell Magento to have a new section in the payment methods configuration area for configuring this module. We also set what fields we want there. For every field, we have an element like this;

<field_name translate="label">
    <label>Field name</label>
    <frontend_type>field type</frontend_type>
    <source_model>field source model class</source_model>
    <sort_order>1</sort_order>
    <show_in_default>1</show_in_default>
    <show_in_website>1</show_in_website>
    <show_in_store>0</show_in_store>
</field_name>

As you will see below. To start with, have the file looking like this;

<?xml version="1.0"?>
<config>
    <sections>

        /**
         * here we're telling the system we
         * we want to add a new config section
         * in the payment method area
         */
        <payment>
            <groups>
                <modulename translate="label" module="paygate">

                    /**
                     * human readable module name
                     * which appears as the name of the
                     * payment method in the admin section
                     */
                    <label>My Payment Module</label>

                    /**
                     * set where this method should appear
                     * in comparison to the other methods
                     * within the admin
                     */
                    <sort_order>670</sort_order>
                    <show_in_default>1</show_in_default>
                    <show_in_website>1</show_in_website>
                    <show_in_store>0</show_in_store>
                    <fields>

                        /**
                         * you need this field if you want the user to
                         * be able to disable/enable this payment
                         * method. leave this out if you don't want
                         * this to be optional
                         */
                        <active translate="label">
                            <label>Enabled</label>
                            <frontend_type>select</frontend_type>

                            /**
                             * we want to use the standard Magento
                             * yes/no select options
                             */
                            <source_model>adminhtml/system_config_source_yesno</source_model>
                            <sort_order>1</sort_order>
                            <show_in_default>1</show_in_default>
                            <show_in_website>1</show_in_website>
                            <show_in_store>0</show_in_store>
                        </active>

                        /**
                         * the below two fields are an example
                         * of fields you may need if integrating with
                         * a payment gateway's API. you will see how
                         * to retrieve these values in your code later
                         */
                        <api_key translate="label">
                            <label>API Key</label>
                            <frontend_type>text</frontend_type>
                            <sort_order>2</sort_order>
                            <show_in_default>1</show_in_default>
                            <show_in_website>1</show_in_website>
                            <show_in_store>0</show_in_store>
                        </api_key>
                        <api_secret translate="label">
                            <label>API Secret</label>
                            <frontend_type>text</frontend_type>
                            <sort_order>3</sort_order>
                            <show_in_default>1</show_in_default>
                            <show_in_website>1</show_in_website>
                            <show_in_store>0</show_in_store>
                        </api_secret>

                        /**
                         * having this field here allows the user
                         * to set whether we want payments to be
                         * authorised or authorised AND captured
                         * if you don't want the user to choose you
                         * can leave this field out
                         */
                        <payment_action translate="label">
                            <label>Payment Action</label>
                            <frontend_type>select</frontend_type>

                            /**
                             * we're using the source from the paygate
                             * module as it has the options we want. this
                             * is safe because the paygate module is a core
                             * Magento module and therefore will be there
                             * with any default install. if it makes you feel
                             * safer you can create your own field source model
                             * but that isn't covered in this tutorial
                             */
                            <source_model>paygate/authorizenet_source_paymentAction</source_model>
                            <sort_order>4</sort_order>
                            <show_in_default>1</show_in_default>
                            <show_in_website>1</show_in_website>
                            <show_in_store>0</show_in_store>
                        </payment_action>

                        /**
                         * what do you want the status to be of
                         * new orders made using this payment
                         * method?
                         */
                        <order_status translate="label">
                            <label>New order status</label>
                            <frontend_type>select</frontend_type>
                            <source_model>adminhtml/system_config_source_order_status_processing</source_model>
                            <sort_order>5</sort_order>
                            <show_in_default>1</show_in_default>
                            <show_in_website>1</show_in_website>
                            <show_in_store>0</show_in_store>
                        </order_status>

                        /**
                         * this field lets the user choose the
                         * name of the payment method as it
                         * appears to the normal user on your site
                         */
                        <title translate="label">
                            <label>Title</label>
                            <frontend_type>text</frontend_type>
                            <sort_order>6</sort_order>
                            <show_in_default>1</show_in_default>
                            <show_in_website>1</show_in_website>
                            <show_in_store>0</show_in_store>
                        </title>
                    </fields>
                </modulename>
            </groups>
        </payment>
    </sections>
</config>

Default configuration values

Before we go and test this, we should set some default values for the configuration fields we just created.

Open app/code/local/MyModules/ModuleName/etc/config.xml and add the following section;

<config>

    ...

    <default>
        <payment>
            <modulename>

                /**
                 * is this payment method enabled?
                 */
                <active>0</active>

                /**
                 * this is where we tell the system what
                 * class to use to handle all of the payment
                 * logic. we call this class the payment
                 * adapter model class. you can change the
                 * paymentLogic bit to be what you want
                 * but it has to be lowerCamelCase and
                 * the class name will have to be changed later
                 * on as you will see
                 */
                <model>modulename/paymentLogic</model>

                <order_status>pending</order_status>
                <title>Credit Card (My Payment Method)</title>

                <api_key>1234</api_key>
                <api_secret>1234</api_secret>

                /**
                 * this is the default set of allowed credit
                 * card types. leave this as it is for now
                 */
                <cctypes>AE,VI,MC,DI,SS</cctypes>

                /**
                 * this should be authorize or authorize_capture
                 * you can probably guess that authorize just
                 * authorizes the payment but authorize_capture
                 * processes it as well
                 */
                <payment_action>authorize_capture</payment_action>

                /**
                 * this field is used to say whether you only
                 * want this method to be used for certain
                 * countries but that is not covered by this
                 * tutorial
                 */
                <allowspecific>0</allowspecific>
            </modulename>
        </payment>
    </default>
</config>

Of course, if you have any of the fields in the above file configurable as set in system.xml, the user set value will be used.

Test progress so far

OK so now if you log into the Magento administration and go to System -> Configuration -> Payment methods you should see your new payment method somewhere in that list.

If you enable it it should then also be available if you checkout on your site as normal. Don’t complete any orders using it yet as there will be problems because we haven’t finished! We still need to create the most important part, the class which will handle all of the logic.

If you don’t see your payment method, please make sure you have completed the above steps correctly. Check for any simple mistakes and try clearing the Magento cache as well. The basic rule is; if it doesn’t appear in the payment method list in the administration section, there’s a problem with system.xml. If it doesn’t appear as a usable payment method when checking out, there could be a problem with config.xml.

4. Payment adapter model class

Create the file PaymentLogic.php in app/code/local/MyModules/ModuleName/Model/. This is where we will put all of our payment gateway logic. First, the contents of the file;

<?php
class CompanyName_NewModule_Model_PaymentLogic extends Mage_Payment_Model_Method_Cc
{
    /**
     * unique internal payment method identifier
     */
    protected $_code = 'newmodule';

    /**
     * this should probably be true if you're using this
     * method to take payments
     */
    protected $_isGateway               = true;

    /**
     * can this method authorise?
     */
    protected $_canAuthorize            = true;

    /**
     * can this method capture funds?
     */
    protected $_canCapture              = true;

    /**
     * can we capture only partial amounts?
     */
    protected $_canCapturePartial       = false;

    /**
     * can this method refund?
     */
    protected $_canRefund               = false;

    /**
     * can this method void transactions?
     */
    protected $_canVoid                 = true;

    /**
     * can admins use this payment method?
     */
    protected $_canUseInternal          = true;

    /**
     * show this method on the checkout page
     */
    protected $_canUseCheckout          = true;

    /**
     * available for multi shipping checkouts?
     */
    protected $_canUseForMultishipping  = true;

    /**
     * can this method save cc info for later use?
     */
    protected $_canSaveCc = false;

    /**
     * this method is called if we are just authorising
     * a transaction
     */
    public function authorize (Varien_Object $payment, $amount)
    {

    }

    /**
     * this method is called if we are authorising AND
     * capturing a transaction
     */
    public function capture (Varien_Object $payment, $amount)
    {

    }

    /**
     * called if refunding
     */
    public function refund (Varien_Object $payment, $amount)
    {

    }

    /**
     * called if voiding a payment
     */
    public function void (Varien_Object $payment)
    {

    }
}
?>

If the payment_action option of ‘Authorise’ has been selected, then only the authorize() method will be called and no payment can be taken automatically. If however the payment_action ‘Authorise and Capture’ was selected, then only the capture() method will be called and that method should probably authorise the payment before capturing the funds. A bit confusing and not explained anywhere but that’s how it works!

The Varien_Object $payment object holds all data to do with the transaction and also the order.

So that’s it! That’s the method I used to add a custom payment gateway to Magento. Please note: I don’t work with Magento anymore so if you have a complicated question which requires looking into Magento code, I probably won’t be able to answer it – but ask anyway just in case!

Problem Description:

Previously I had tried migrating an existing customer database from Xcart 3.5 to Magento. I was successful at exporting the database from Xcart, but, I was unsuccessful at importing all of the customer records into Magento. The import tool relies upon AJAX to accomplish the customer and product importing. I determined that Magento did not finish importing the customers because the PHP session was timing out. I tried setting the session within the Magento administrative interface. I set the session time to 86400 seconds (or 24 hours). This did not fix my problem.

Solution

I altered the main .htaccess file. I appended the following lines to the bottom of the file.

php_value session.cookie_lifetime 86400
php_value session.gc_maxlifetime 86400

Typically a PHP session will timeout after 24 minutes. I recommend altering your htaccess file only temporarily. By having a very long PHP session max life time for your PHP session you increase the chances of someone hacking your web site by using a technique called session fixation a method of session highjacking.

After you are done make sure to change the session time out value within the Magento adminstrative interface and remove the above lines from the htaccess file.

Vandaag iets nuttigs geleerd van een van onze klanten (poaa.com). Voor deze klant hebben wij een multi-shop Magento omgeving ontwikkeld.

Voor hun kerstspecials hebben ze een nieuwe categorie in Magento aangemaakt. Ze hebben eenvoudige HTML code gebruikt om de kerstcategorie extra aandacht te geven. Ik dacht dat je dit alleen kon doen door in je template de code te wijzigen, maar als je één categorie een aparte stijl wilt geven kan dat dus ook via de admin van Magento!

1) Voeg de HTML code toe in de benaming van je categorie. Als voorbeeld: <font color=”red”>jouw categorienaam name</font>
2) Op het moment dat je de categorie opslaat zal Magento een ‘lelijke’ URL aanmaken (aangezien de HTML code ook opgeslagen zal worden). Pas dit aan door handmatig de juiste URL in te voeren.

Hope this helps!

Bent u op zoek naar een ervaren Magento partner voor de ontwikkeling van uw webshop? Neem gerust contact met ons op!