OXID 7 Module (Twig) 1.1.0: What's New in This Update

Release News Graphic: New Module for OXID 7 with Twig Templates Now Available

Version 1.1.0 of our endereco module for OXID 7 is now available. This update is compatible with OXID eShop 7.1 to 7.5. It includes security improvements, full integration of the JS-SDK 1.14.5, and fixes a number of bugs, particularly for the APEX theme.

A Note Before We Begin: This module is intended exclusively for the Twig variant Designed for OXID 7. If you're still using the Smarty template system for your store, this update isn't for you.

 

What's new?

  • API Key Secured: Communication with the endereco API now takes place on the server side. The API key is no longer sent to the browser.
  • JS-SDK 1.14.5 Fully Integrated: Address validation now works correctly for countries with and without a state selection option. Outdated validation statuses are detected when the page is loaded and cleared.
  • Smart Autofill removed: The feature has been permanently disabled and removed from the configuration. In practice, it led to incorrect entries because customers did not notice that fields had already been filled in automatically.
  • Name verification defined more clearly: The setting was previously called „Title Check,“ even though it controls the entire name verification process and standardization. The name has been updated to better reflect its actual function.
  • Support for OXID 7.4 and 7.5: The module now officially supports the latest versions of OXID as well.
  • Referrer Secured: Previously, if no Referer header was detected, the internal server path was sent to the endereco API. Now, the store URL is used instead.
  • Cleaning Up in the Module: Outdated components from the OXID 6 era and unused code have been removed. This also resolves various PHP warnings.

 

Fixes

  • Server error during address verification: If no country was selected during registration or the „No title“ option was chosen, the address validation might have terminated with a 502 error. In both cases, the validation now completes successfully without terminating.
  • Special Characters in Country Names: Country names containing apostrophes (for example, „Côte d'Ivoire“) could prevent the address validation from starting correctly. Character processing now works reliably.
  • The test status was not saved: For newly created shipping addresses, guest orders, and registrations during checkout, the validation status was not saved correctly and was reset every time the page was reloaded. It is now saved correctly the first time it is saved.
  • Address Correction on the Order Page: Previously, when users clicked „Edit“ in the correction dialog, they were redirected to the address entry page, but the form did not open there. Now, the form opens correctly after the redirect.
  • Checkout Buttons in the APEX Theme: The „Continue“ button in the checkout process did not trigger the address validation, and the „Edit“ button closed the form again after the validation. Both buttons now work as intended.
  • Name Verification with an Incorrect Name: If a new shipping address was created in the APEX theme, the name validation might have used the previous name. The cached name is now reset when a new address is created.
  • Suggestions for countries were ignored: If the address validation suggested a country other than the one entered, the suggestion was not accepted. Country corrections are now processed correctly.
  • Suggested corrections in the admin area: Suggestions were not displayed on the “Customer Master Data” and “Addresses” pages in the admin area. They now appear correctly.

 

Update note

After the update, run the database migrations, clear the cache, and rebuild the database views.

Addresses that have already been verified will be re-verified once after the update because the internal calculation of the address hash has changed. This happens automatically the next time the address is used, and it is intended to work this way.

If you've made customizations to your OXID store, there are two more things you should keep in mind. First, the endereco API is now accessed via its own proxy controller instead of directly from the browser. Additionally, address storage now only works if the request comes from the session of the logged-in customer to whom the address belongs.

We recommend that you first perform the update in a test environment. You can also find the complete release notes under the Release Notes for OXID 7 and on GitHub.

 

Learn more about endereco

Everything about our Address validation, our Integrations for various e-commerce platforms and the OXID eShop Integration can be found on our website.

 

Share this post

Sign up for the newsletter