geschrieben von Covos
am 2. Januar 2018 - 15:24
In einem Magento 1.9 Shop fiel das Problem auf, dass es „plötzlich“ nicht mehr möglich war mit Geschenkgutscheinen (Extension „Gift Card“ von Magestore) zu zahlen. Die Gutscheine wurden zwar eingelöst und die Summe vom Gutscheinwert abgezogen jedoch blieb die Bestellsumme … Weiterlesen →
geschrieben von Covos
am 2. Januar 2018 - 14:56
  Wir haben in einem Magento 1.9.3.6 Shop die „Gift Card“ Extension von Magestore installiert. Weiterhin nutzen wir in diesem Shop auch die PayPal Plus Extension von i-ways für die Zahlungsabwicklung. Nun hatten wir das Problem, dass das Fenster von … Weiterlesen →
geschrieben von
am 31. Dezember 2017 - 14:33
No Clear Wins:

Two of the biggest mind shifts I’ve had to make in coming back to C programming have been strings and variable scope/lifetime. This Stack Overflow question is a nice encasulation of both. First off — strings aren’t a first class type in C. They’re just a char array of individual characters, with a NULL character as the final element. This might not seem that bad, until you remember that arrays aren’t the simple “lists of stuff” you might be used to in higher level languages. In C, an array is a literal allocation of “N” bytes of RAM. Arrays are […]

geschrieben von
am 31. Dezember 2017 - 13:19
Two of the biggest mind shifts I’ve had to make in coming back to C programming have been strings and variable scope/lifetime. This Stack Overflow question is a nice encasulation of both. First off — strings aren’t a first class type in C. They’re just a char array of individual characters, with a NULL character as the final element. This might not seem that bad, until you remember that arrays aren’t the simple “lists of stuff” you might be used to in higher level languages. In C, an array is a literal allocation of “N” bytes of RAM. Arrays are […]
geschrieben von Elizabeth Van Dyke
am 29. Dezember 2017 - 3:34

Get to know Magento Master Alessandro Ronchi, COO & Magento Specialist at Bitbull

geschrieben von
am 28. Dezember 2017 - 14:37
The Odd Semantics of Magento 2’s referenceBlock:

In Magento 1, it was pretty common to write a bit of layout update XML that looked like the following. skin_js This XML translates roughly into the following PHP pseudo code $block = $layout->getBlock(‘head’); $block->setLabel('skin_js’); Or, in plain english, Magento fetches a reference to the already instantiated block object named head, and then calls this block’s setLabel method. This syntax has survived, mostly, into the Magento 2 era. Although the Magento provided “dev docs” say the syntax is “not recommended“, action methods still work Does this Work […]

geschrieben von
am 27. Dezember 2017 - 13:01
In Magento 1, it was pretty common to write a bit of layout update XML that looked like the following. <reference name="head"> <action method="setLabel"> <label>skin_js</label> </action> </reference> This XML translates roughly into the following PHP pseudo code $block = $layout->getBlock('head'); $block->setLabel('skin_js'); Or, in plain english, Magento fetches a reference to the already instantiated block object named head, and then calls this block’s setLabel method. This syntax has survived, mostly, into the Magento 2 era. Although the Magento provided “dev docs” say the syntax is “not recommended“, action methods still work <referenceBlock name="catalog-search-advanced-link"> <action method="setLabel"> <argument name="value" xsi:type="string">Does this Work</argument> </action> […]
geschrieben von Elizabeth Van Dyke
am 26. Dezember 2017 - 23:19

On stage or in business, it's curtains if you fail to empathize with your audience

geschrieben von Elizabeth Van Dyke
am 26. Dezember 2017 - 21:00

Winners to be announced and celebrated at Imagine!

geschrieben von
am 26. Dezember 2017 - 15:10
Layout XML Merging in Magento 2:

One of the bigger changes to Magento 2’s layout system is how a end-user-programmer uses layout handles. In Magento 1, layout handles were top level configuration nodes in a set of layout update xml files In Magento 2, layout handles are individual XML files (which I’ve been calling layout handle XML files) #File: path/to/module/view/layout/handle_name.xml One interesting side effect of this is, unlike Magento 1, Magento 2’s layout XML files are susceptible to node level merging. i.e. — consider this core XML file #File: vendor/magento/module-catalog-search/view/frontend/layout/default.xml <?xml version=“1.0”?> […]

geschrieben von
am 26. Dezember 2017 - 13:50
One of the bigger changes to Magento 2’s layout system is how a end-user-programmer uses layout handles. In Magento 1, layout handles were top level configuration nodes in a set of layout update xml files <handle_name> <!-- layout update xml nodes --> </handle_name> In Magento 2, layout handles are individual XML files (which I’ve been calling layout handle XML files) #File: path/to/module/view/layout/handle_name.xml <!-- layout update xml nodes --> One interesting side effect of this is, unlike Magento 1, Magento 2’s layout XML files are susceptible to node level merging. i.e. — consider this core XML file #File: vendor/magento/module-catalog-search/view/frontend/layout/default.xml <?xml version="1.0"?> […]
geschrieben von
am 24. Dezember 2017 - 17:30
Magento 2’s Poorly Named Layout Argument Nodes:

Magento 2 introduced a new node type to its Layout XML DSL — the and node. #File: vendor/magento/module-shipping/view/frontend/layout/sales_guest_view.xml Track your order Like so much of Magento — the names of these new nodes hide their purpose from developers. All the nodes do ensure a value will be set on the final block object. i.e. The above code will set a label property on the tracking-info-link block (instantiated from the PHP class Magento\Shipping\Block\Tracking\Link). This means you can access the property from your phtml […]

geschrieben von
am 24. Dezember 2017 - 13:51
Magento 2 introduced a new node type to its Layout XML DSL — the <arguments/> and <argument/> node. #File: vendor/magento/module-shipping/view/frontend/layout/sales_guest_view.xml <referenceBlock name="sales.order.view"> <block class="Magento\Shipping\Block\Tracking\Link" name="tracking-info-link" template="Magento_Shipping::tracking/link.phtml"> <arguments> <argument name="label" xsi:type="string" translate="true"> Track your order </argument> </arguments> </block> </referenceBlock> Like so much of Magento — the names of these new nodes hide their purpose from developers. All the <argument/> nodes do ensure a value will be set on the final block object. i.e. The above code will set a label property on the tracking-info-link block (instantiated from the PHP class Magento\Shipping\Block\Tracking\Link). This means you can access the property from your phtml […]
geschrieben von Elizabeth Van Dyke
am 22. Dezember 2017 - 2:55

Here are some of the most popular content resource to help inspire you in 2018

geschrieben von Elizabeth Van Dyke
am 21. Dezember 2017 - 1:11

The first in a new series of interviews with Magento trailblazers

geschrieben von Elizabeth Van Dyke
am 19. Dezember 2017 - 22:21

Gorilla Group’s survey of B2B business leaders

geschrieben von
am 19. Dezember 2017 - 17:05
Getting out of the Block Business:

This in an interesting Magento layout technique that came my way via Vinai Kopp (of Mage2.tv fame). Magento 2’s automatic constructor dependency injection system presents a problem for class trees with multiple levels of inheritance. First, programmers end up needing to call parent constructors with the right arguments, and in the right order. Second, class hierarchies also create confusion w/r/t the object manager’s configuration — namely, which constructor should the object manager reference when looking for arguments to instantiate and inject? Magento 1’s block class hierarchy has a lot of inheritance. Magento 1 plugins modeled on the core code also […]

geschrieben von Elizabeth Van Dyke
am 19. Dezember 2017 - 4:00

Digital success stories from our B2B clients

geschrieben von
am 18. Dezember 2017 - 13:30
This in an interesting Magento layout technique that came my way via Vinai Kopp (of Mage2.tv fame). Magento 2’s automatic constructor dependency injection system presents a problem for class trees with multiple levels of inheritance. First, programmers end up needing to call parent constructors with the right arguments, and in the right order. Second, class hierarchies also create confusion w/r/t the object manager’s configuration — namely, which constructor should the object manager reference when looking for arguments to instantiate and inject? Magento 1’s block class hierarchy has a lot of inheritance. Magento 1 plugins modeled on the core code also […]