New features and improvements included in Dynamicweb 8.7.1

Release: 27th October 2015
Check 8.7.1 Important notes before upgrade.

SUMMARY

Dynamicweb release 8.7.1 is now ready for download.

A minor service release, Dynamicweb 8.7.1 offers additional improvements to usability for you and your customers, a new international payment provider for websites and mobile apps, and more than 30 bug fixes.

Ecommerce

Stripe has been added as a new payment provider for both websites and mobile apps, allowing you to accept payment from anyone, anywhere – or at least from the US, Canada, UK, Australia and most European countries including Denmark, Norway and Sweden. Stripe is fully integrated with recurring orders and saved cards functionality introduced in 8.7.0. Working with product variants has become easier, with a new interface for adding and managing product groups and options. Shipping methods now has a field for adding an icon, which can then be rendered in the frontend for an immediate visual representation of the shipping provider. And anonymous carts can now be merged with existing saved carts on login. Finally, the Quickpay payment window has been updated to match their API changes, and recurring orders has seen extensive improvement, and is now based on an order template.

Content

The item field type ’user field’ now allows you to add user groups, rather than just individual users, making it possible for you to work with users in items in an easier, dynamic manner. The Extranet module now supports password recovery based on user name. The item publisher now supports using secondary sorting criteria, giving you tighter control over item content published. When using a @Translate tag or the Translate method in Razor, and the provided key does not exist in the translation file, the key is now added to the XML file - with the specified default value if specified (Only new translations method).The keys are added to the translations.xml in the designs folder when the frontend pages are loaded. And Forms-for-Editors has been made even more user-friendly, with the option to create receipts with a rich-text editor rather than a receipt template.

Marketing

The ever-popular News V2 module now supports social media publishing directly from the backend, making it easier for your editors to publish to multiple platforms – sharing your content to all your social media networks.

Platform

The new indexing engine now supports grouping variants in a query, and the query publisher can now output the Lucene score in addition to the query result.


Online Marketing


Ecommerce

  • Recurring order templates

    Area: Orders\Recurring orders
    Description:
    Recurring orders are now based on "template orders" that are placed in a "Recurring orders" node in Ecommerce when created. Recurring orders is implemented with the Stripe payment provider together with the Saved card functionality. When a recurring order is created in frontend, an order template is created in "Recurring orders". The first real order and the following recurring orders are based on this order template. When the scheduled task for recurring orders runs (default is every 1 hour) and start date is reached, the actuel orders are recalculated and created (and e-mailed - if setup). Recurring orders requires a reference to a credit card and automatically saves the credit card token in the AccessUserCard table when the order template is submitted. The default templates, InformationRecurringOrders and ReceiptRecurringOrders, are updated with Start date fields. A new default template InformationSavedCardsAndRecurring with Saved card and Recurring orders functionlity is added.

    Version: 8.7.1.0
  • Tags for recurring order type

    Area: Orders\Recurring orders
    Description:
    2 new tags are available in the order receipts: Ecom:Order.IsRecurringOrder and Ecom:Order.IsBasedOnRecurringOrder in order to differentiate the receipts for an "order template"/subscription and the acual order, that are sent when the recurring order is created.

    Version: 8.7.1.0
  • Stripe Checkout Handler

    Area: Payment\Stripe
    Description:
    New checkout handler - mainly for the US market - is implemented in 8.7.1.0. Stripe Checkout is an embeddable payment form for desktop, tablet, and mobile devices. It works within your site -customers can pay instantly, without being redirected away to complete the transaction. With Stripe Checkout it is possible for returning customers to save credit cards and use them later without re-entering their card number.

    Version: 8.7.1.0
  • Error logging

    Area: Saved cards
    Description:
    When using a saved card, we now save validation errors and messages that we have received from the payment gateway, to help the user when administering cards. The errors/messages are listed in the Saved card section in User Management or in Customer Center.

    Version: 8.7.1.0
  • Possible to set a Default card.

    Area: Saved cards
    Description:
    In the Saved card sections in User Management and in Customer Center, it is now possible to define a default card. A default card is preselected in the payment step in the checkout flow.

    Version: 8.7.1.0
  • Add an image field for a shipping method

    Area: Shipping
    Description:
    You can select an image as icon for a shipping method and use it in frontend with Ecom:Cart.Shippingmethod.Icon Ecom:Cart.Shippingmethod.Icon.Clean

    Version: 8.7.1.0
  • Modernize variant group and options UI.

    Area: Variants
    Description:
    The UI for making variant groups in the management center has been modernized to be more inline with the rest of the system.

    Version: 8.7.1.0

Content

  • User groups as item field

    Area: Items
    Description:
    A new item field where you can select a user (like the product item field). When editing an user item in the frontend (using Item publisher or Item creator) the field is not rendered.

    Version: 8.7.1.0
  • Print out a message if @TemplateTags is in templates

    Area: Templates\Razor
    Description:
    If @TemplateTags() has been left in any Razor template, the template will now print out that it contains @TemplateTags, which it should not due to performance. Even if the @TemplateTags() is commented out in Razor, it still poses a problem: I.e. @*/@TemplateTags()*/ will not print the tags, but will still invoke that Tagexists returns true which gives a performance overhead.. So if that is present in a razor template, Dynamicweb will add the warning "TemplateTags() in code ({0}). Remove before going live..." printed out in the browser. {0} will be the template name

    Version: 8.7.1.0
  • Automatically add translation keys to translation.xml

    Area: Templates\Translate
    Description:
    When using a @Translate tag or the Translate method in Razor, and the provided key does not exist in the translation file, the key is now added to the XML file - with the specified default value if specified (Only new translations method). The keys are added to the translations.xml in the designs folder when the frontend pages are loaded.

    Version: 8.7.1.0
  • Pasword recovery based on username

    Area: User Management
    Description:
    Password recovery in extranet module login mode now supports recovery based on username

    Version: 8.7.1.0

Platform


Integration