Easyling Release Notes November, 2020

When you add features to a piece of software, you are likely to add bugs as well. We spent this month eliminating them from Easyling and adding some smaller quality of life changes to improve it. Our updated recommended settings are now used when starting a crawl is started when creating your project, Machine Translation credentials can be better managed and the Access-Control-Request-Headers is now forwarded to the source website. We also added another option to customise the experience on your Whitelabel. Read all the details below.

Default settings of crawls

For quite some time, the default was to gather everything we can to the project’s pages list. However, the more projects were created the more obvious the trend was: most images are logos and such and they aren’t localised. If we don’t localise them, what’s the point of crawling them in the first place?

With that realisation, we decided to change the crawler’s default options not to gather resources. If you want to localise an image, you can always just add it manually. It’s even easier than finding it in a huge list. An added benefit is that resources aren’t crawled so less requests are needed, which lowers the cost of the crawls.

Up until now, these defaults were only applied to crawls started through the Crawl Wizard. With this month’s update, crawls started from the project creation dialog also have these better defaults.

Machine Translation credentials

We thought MT credentials were a “set once and forget” kind of option and our design reflected that. With this update, it is now possible to save your settings if you don’t have an MT credential enabled (assuming that the engine is disabled anyway). This allows you to completely remove your key and prevent MT usage completely.

Access-Control-Request-Headers header

Cross-Origin Resource Sharing (CORS for short) is a great tool to use APIs that are on different domains. However, if the correct headers aren’t present, it can also cause headache. One such case is if you have 2 linked projects that should work together but they don’t. It turns out the issue on at least one such projects was that the Access-Control-Request-Headers header was blocked through the proxy. To fix it, we now pass it through.

This header is used for preflight requests to tell the server that the actual request will have the given set of headers. The server will reply with an Access-Control-Allow-Headers header which hopefully allows all of the headers in question. If you are interested, Mozilla’s web documentation has more details available here.

Hide comments on your Whitelabel

We received feedback that some users avoid using the external collaboration tools provided to them and just use the Workbench’s comments functionality. While we are happy that our feature is the most convenient, this can cause issues when it comes to organising comments if some of them are in your external tool and others are in the Workbench. As such, it is now possible to disable comments completely on the Workbench. If you wish to do so, just let us know on support@easyling.com.