Search Engine: Elastic

Article ID: 120794, created on Mar 29, 2014, last review on Jun 1, 2016

  • Applies to:
  • Business Automation 5.5
  • Business Automation 5.4
  • Business Automation 6.0


There are random issues with an Online Store. These may include blank pages, incorrectly calculated or displayed prices, no results after clicking buttons, a String cannot be empty error while no field is highlighted/empty, a required resource not selected by default, constantly loading screens, and more.


There may be an issue with a customized layout template or store code or php memory_limit


If the issue happens after recent update first of all make sure that store was synchronized after update - check "Last Synchronization" date of store, but keep in mind that this date is not updated is store was synchronized from "Synchronize Store" event (PBA-74016). Synchronize store is needed.

The reason of issue may be seen in the Apache error log. Check /var/log/httpd/error_log on the Business Automation store server when a corrupted store screen is loading.

If there are no errors in the log, check if logging is enabled in /etc/php.ini. Required setting is:

log_errors = On

Enable logging and restart apache if needed.

If logging is enabled, but there are no errors in apache log enable Firebug and load the corrupted screen - check the errors in Firebug. The part of the code that is failing needs to be found in the customized Layout Templates.

If no errors are found, check the Page Source of the corrupted screen. Find the template that is loaded at the part of the screen with the issue. Check if this template exists in PBA Home> Products> Online Store > Layout Templates tab. If the template is in the list, it is most probably customized.

  1. Check that the syntax is correct
  2. If it is not possible to understand the cause, select the template, save its content somewhere, and press Reset To Default. After that, synchronize the store, clear your browser cache, reload the corrupted screen and check if the issue is gone. If the issue has been resolved, check the customized template to find how it needs to be corrected. This procedure falls out of Odin Technical Support scope.

Note that customization of several templates used on one screen can cause an issue. In these cases, several templates may need to be reset.

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 801221f8cd76fba7300d1e6817c8e08b 92711db0799e8aefe8e51f12dace0496 210d017ddc3a076d22f0f865b1cf0730 e12cea1d47a3125d335d68e6d4e15e07 3627d36199b8ff577605df76e2fa222b bb7e9177fb03488961a3ea554120f328

Email subscription for changes to this article
Save as PDF