POS Plugins: Troubleshooting

October 27, 2022


In Berlin POS, some of the less common functionality has sometimes been provided in the form of "plugins".

One way to add a plugin is the "Javascript plugin URL" field on the "Configuration" screen in POS. It can be populated with a list of URLs, one per line — each URL pointing to a Javascript (.js) file.

 

What to do if a plugin, previously functional, is no longer loading?

In the past, a plugin may have been set up with a non-secure URL that starts with "http://".

Modern browsers enforce one rule to keep your interactions secure: if a website (or application) has been loaded over a secure connection (HTTPS), it will not be allowed to load images, script files and other assets over a non-secure connection (HTTP). The browser indicates a secure connection with a "https:" prefix or a padlock icon.
 


 



Therefore, if you are using POS over a secure connection, plugins with a "http:" URL may be not loading. This is also indicated as an error in browser console ("View > Developer > JavaScript Console" in Chrome, "Tools > Developer > Web Console" in Firefox)
 



We absolutely encourage and recommend to use Erply POS over secure connections. The best resolution is to upgrade the plugin URLs to HTTPS, too. If you notice a plugin being blocked, and it is configured with HTTP, try the following steps: 

  1. Take the URL and copy-paste it into a new browser tab.
  2. Replace "http:" in the beginning with "https:". Load the URL.
  3. Verify that the URL loads successfully. (The browser should display the plugin's source code; the exact content is unimportant, as long as it appears to load.)
  4. Make the same change (http -> https) in POS configuration, too, and save.