However, the module was a widget. I did not want to create a CMS page or block solely for inputting the widgets variable so I sorted out how to call the widget from inside a .phtml file in a Magento template.

The widget was Magentweet and had several things to configure when using it in the backend. I could add the same widget programmatically like this:

<?php $tweetblock =  $this->getLayout()->createBlock(’magentweet/user’);

$tuser = $tweetblock->setData(’tuser’,'groupdeal_nl’);

$nb = $tweetblock->setData(’nb’, 5);

$link = $tweetblock->setData(’link’,'#1E7EC8′);

$link_a = $tweetblock->setData(’link_a’,'#000′);

$desa = $tweetblock->setData(’desa’,'enable’);

echo $tweetblock->setTemplate(’magentweet/user.phtml’)->toHtml(); ?>

Of importance here is not that a widget block is created through a regular createBlock() statement. The trick is the setData() statements. In a widgets Block code you can easily see which data the widget expects, and you can set the widget’s data accordingly from the template instead of through elaborate WYSIWYG cms procedures.

1. Using Magento functionality inside CMS pages;
2. Using other content blocks inside CMS pages;
3. Linking to other pages within the shop.

Check it out at their blog, I look forward to toying around with it :-)

This places webshop developers in an interesting situation: they have to make the decision to make or buy, placing them in the shoes of software buyers instead of makers. Below are some advantages and disadvantages of deciding to build a module from scratch, using a commercially available module, and building a custom module with a commercial module as the basis.

Building from scratch:

- Advantage: You can build the module exactly as the client likes

- Advantage: You can sell the module (on the internet, in other projects) well if you negotiate the intellectual property (IPR) for it with your client

- Disadvantage: Time and money

- Disadvantage: Amount of coordination required

Only using the commercial module

- Advantage: Quick implementation

- Advantage: Functioning of the module is the responsibility of the module’s owner

- Disadvantage: Will often not fit situation perfectly

- Disadvantage: Depend on original builder for support / updates

- Disadvantage: Effort to show end clients that bought module suits their needs but in a slightly different than specified way

Buying a commercial module, customizing it

- Advantage: Can fit the desired situation pretty well

- Advantage: Moderate effort,

- Disadvantage: Depend on original module builder for support / updates

- Disadvantage: Highly sensitive to changes in functionality of the bought commercial module

- Disadvantage: Difficult to sell end result as a commercial module so end result is only applicable in one project

The more standard it is what you want to implement the wiser and more likely it is that there’s already a module available that does what you want. If you have a more specific need, then it’s a make or buy decision where time (including time to market) is the biggest factor.

Open file app/code/core/Mage/Newsletter/model/Subscriber.php. Disable the line containing “sendConfirmationSuccessEmail() in the function called “subscribeCustomer()”). Now, your customers will not receive newsletter confirmation emails on importing.

Background: the dataflow customer import saves customer data using a regular save action on the customer object. The newsletter module of Magento listens for a customer save event and fires the subscribeCustomer() function when that happens. Of course, enable the line you edited in the subscribeCustomer() function again after you’re done!

There’s a pretty convincing video on their site, showing that the tool can at least be well used for quick mockups and prototyping. Anyway, check it out at http://www.ixedit.com/.

Update: http://www.magentocommerce.com/extension/171/fooman-google-analytics-plus. This module tracks performance of different parts of the one page checkout!

p.s.:

Of course, I won’t be going so far as to block users from websites or forcing them to upgrade to IE6. Possibly blocking or sending away 30% of your potential buyers on an eCommerce / Magento platform is of course a ragingly bad idea…

 For invitation based shops, I always wonder what the revenue would have been without closing the shop off to invited members…