Easyling Release Notes November, 2022

November was a month of smaller tweaks, improvements, and bugfixes. The good news is that there was a bunch of them. My favourite is that code completion is now available in the JS and CSS editors. Just press Ctrl + Space! We also added a default usage alarms for new projects. Read the full article for the details.

Code completions

Injected JavaScript gives you full control of the behaviour of the translated websites. You can change as little or as much as you want. However, until now, the best way to work with it was by editing your code in a separate tool, like Notepad++, and copying it to the Dashboard.

With the release this month, code completions became available. This way, you can edit code more effectively directly on the Dashboard. This could be especially useful if you start by asking ChatGPT to write code for you and need to debug it.

We also added a reminder about this to the bottom of the screen.

Default alarm

Alarm is a feature that can be immensely useful. However, we found that it’s seriously under-utilised. With our old pay-as-you-go pricing model, this can lead to a situation where lots of resources were accidentally used, incurring significant cost. Turning the Alarm feature on by default allows you to be notified of such scenarios.

The default configuration notifies you if there are over 10 page views/second. It should not trigger during project setup. If it does, We recommend that you check out what causes it to do so to avoid unnecessary cost. If in doubt, please don’t hesitate to reach out to us at support@easyling.com.

Naturally, when the project goes live, this setting may need to be changed if you expect lots of traffic.

Fixes and tweaks

We also made quite a few smaller changes. It’s getting quite late when I’m writing this, so please allow me to just drop them in the list below.

• The cost of exporting content was highlighted on the Dashboard.
• You can now import both .xlf and .xliff files.
• We optimised the way Work Packages are generated and changed the push notifications on the Dashboard accordingly. Work Package generation processes with multiple target languages will finish faster.
• We fixed an error that prevented some users from logging in.
• We added gclsrc as a default ignored query parameter for new projects. This query is used by Google Ads. As it doesn’t change the content of the website, it can safely be ignored. Ignoring such queries allows you to keep the Pages list cleaner.
• We made sure the open in new tab icon, like when you open a link to our documentation, is consistently on the right of the links.
• We fixed a bug where were Crest, our client-side translation engine, handled embedded HTML snippets incorrectly.
• As well as other sections of the Crawl wizard, the final step was tweaked, so that the settings are more transparent.
  
• We clarified the wording of the Show subscription details toggle under Account settings. It now highlights that this setting is for your account only. It doesn’t prevent others from seeing your balance if they are invited to your project.
• We fixed a bug where the Assign Translation Memory dialog would break when there are too many target languages.
• In the crawl wizard, on step 4, you can enter a regular expression to exclude pages from the crawl’s scope. We changed this field, so that you can now enter an expression that only matches a substring of the path to exclude it. For example, if you wanted to exclude all the release notes on www.easyling.com, you could just enter /release-notes/, instead of having to enter .*/release-notes/.*. If you are familiar with Java, the change was that we changed from using the matches() method to find().
• We added a dedicated button under Account settings to change your profile picture as just clicking on the old picture wasn’t visible enough.