Alfresco digitale workspace localization issue - docker

I have installed Alfresco using docker images as explained in this Angel Borrow's github repos. All goes fine.
But some translation key are not processed. On this image you can see that the translation key "LOGIN.LABEL.USERNAME" is not replaced by it' value.
There are several other issues like that on some popups in ADW (Alfresco Digital Workspace) app.
What is the best way to fix that?
PS : The same localization issues also exist on alfresco cloud.

The first think to check is if you have an adBlock extension activated on your browser page, if it's the case, disable adblock for Alfresco digitale workspace and reload.
You can debug error by using developer tools on your browser (F12)
in network you can see errors related to labels blocked and have more details.
O.

Related

Is there other way to get the Microsoft Edge DevTools Preview without Microsoft store?

I always debug the WebView control with VS, I refer to the this official document Debug a WebView control in a UWP App.
Recently, I found there is a best way to debug the WebView control by using the
Microsoft Edge DevTools Preview App.
The problem is that it seems the only way to install the tools is Microsoft Store. Unfortunately the Miscrosoft Store is blocked on my machine, I want to know is there any other way to get the Microsoft Edge DevTools Preview tool? Any help would be appreciated, thank you in advance.
I found this article https://windowsreport.com/download-microsoft-store-apps-without-store which seems to show a way of doing this.
I cannot state if it definitely works yet as I have to wait for my IT to department to decide if it can be allowed.
Steps are:
Visit https://store.rg-adguard.net/
Enter https://www.microsoft.com/en-gb/p/microsoft-edge-devtools-preview/9mzbfrmz0mnj
Download the file ending in appxbundle (to it's own directory not just "downloads")
Open Powershell as Admin
Execute something like Add-AppxPackage -Path "C:\Users\WindowsReport\Downloads\ee2546d7-f0e5-4aa2-be54-032299162322" (change path to the download directory you used earlier)
If you get errors you may need to download additional files from the same place you got the appxbundle file

Atlassian JavaScript load error We tried to load scripts but something went wrong

We tried to load scripts but something went wrong.
Please make sure that your network settings allow you to download scripts from the following domain:
https://aid-frontend.prod.atl-paas.net/atlassian-id/front-end/4.5.0
Tried Google Chrome, Firefox, Internet explorer also tried with different PC.
Not able to login into bitbucket
I'm using Chrome Version 77.0.3865.120 (Official Build) (64-bit). I got the same error trying to log in to my group's Atlassian site, and I was able to fix it by specifically allowing JavaScript from Atlassian:
Open Chrome settings
Click on Advanced
Click on Privacy and Security
Click on Site Settings
Click on JavaScript
Make sure JavaScript is set to allowed
Next to Allow, click Add
Paste the URL from the error message in and click Add
I've faced a similar problem recently while traveling and trying to work from a new location.
First I've tried the steps from the previous answer which unfortunately didn't help me (but they definitely may be useful in a different case scenario).
I'm renting a house with an existing pre-configured WIFI router which I could get an access to manage it over the web UI.
I'm not sure which of the following helped me. I did the following changes to the router configuration:
Added the 8.8.8.8 as a primary DNS Server
Enabled IPV6
Disabled the built-in firewall (this one is the more likely one which fixed the issue)

How to debug VSTS extension build summary tab without deploying to VSTS service?

I need to develop a fairly complex UI for VSTS build summary tab. I'm using VS Code as the code editor. Following url describes how to debug using Edge browser, however this approach require constantly packaging and deploying extension to VSTS making it time consuming.
https://www.visualstudio.com/en-us/docs/integrate/extensions/test/debug-in-browser
I tried to directly load the .html (summary tab) using View In Browser extension and following message displayed in browser console,
No handler found on any channel for message:
{"id":1,"methodName":"initialHandshake","instanceId":"VSS.HostControl","params":[{"notifyLoadSucceeded":true,"vssSDKVersion":2}],"jsonrpc":"2.0","handshakeToken":"4234q23rqfafaf23r"}
Is there any better way of debugging the application while developing?
You can develop locally. Since VSTS uses an iframe to show your extension's content, you can run a local server and reference that in the vss-extension.json manifest.
First, in the vss-extension.json, set the baseUri property to where you are running your project locally, such as https://localhost:8889. You need to be running it as https for VSTS to serve the content, as otherwise you will get a "Mixed Content" error and VSTS will refuse to display your extension's content.
Then, publish your extension and run it locally. Wha-la, you should have local development. There may be more trial and error needed, let me know if there's any steps that I'm missing.
If the link still works (you know how the Interent is), this starter project is a great start: https://github.com/Microsoft/vsts-extension-multivalue-control
No, you can’t debug the extension code without deploying extension to VSTS, the extension must be deployed to the VSTS before debug the code.
After initial deployment you may be able to use Fiddler to return your files directly from disk using FiddlerScript or the AutoResponder feature.

Find features of a non Microsoft program

I'm not sure how to even ask this question, but let's say I have a program such as Google Chrome. How would I find out the "features" of it so I can use PowerShell to modify it.
For example, how would I have Chrome open a web page and click a button.
I know for IE, you can use $ie.document.getElementById("loginform").submit() to click a button.
Thank you,
Tony
You can't ever really get the same amount of control over non-Windows programs using Powershell.
In terms of Chrome, you could simply open the browser and go to a webpage with:
$Start-Process "chrome.exe" "www.google.com"
There is generally not that much more for further functionality, but with Chrome you may be able to do things like change settings and configuration. Check out the (large) JSON file Preferences and other config files, which you can find in Chrome's local appdata folder (Win+R, %localappdata%, Google/Chrome/User Data/Default). I'm not too sure but it may also be a bad idea to mess around with these files.
I also did a Google search and found this third party powershell tool for browsers, called Selenium. Here's the list of extensions.

Jenkins HTML Publisher Plugin: No external links with Jenkins 1.643

I have a Jenkins job, where I generate an HTML-Page as a post buildstep, containing an image link ( HTML img tag). This HTML page is published by the HTMLPublisher Plugin for each job.
This has always worked great. But since I have updated Jenkins to v. 1.643, I only see a blank page when I click the published HTML page.
I've tried out a lot of things and found out the following strange behaviour:
Since the update, I cannot embed external links into the HTML-pages I publish.
If I embed an image from an external location (img src="somelocation/xxx.jpg), the image won't be displayed.
If I examine the HTML page with Firefox, I can see that the image tag is greyed out like it was invisible, but it is not.
If I embed a normal hyperlink, pointing to an external location, I can see the link in the displayed page, but when I click on it, nothing happens.
It is like Jenkins would not permit external links in this context.
Please help me out here :)
Thank you!
Edit:
Thanks to Dave Bacher, he gave me the right hint.
Look at this page to see Jenkins' new security policy.
https://wiki.jenkins-ci.org/display/JENKINS/Configuring+Content+Security+Policy#ConfiguringContentSecurityPolicy-Implementation
You have to relax the rules, so that embedding external images is allowed again.
For testing it, just type the following in your script console:
System.setProperty("hudson.model.DirectoryBrowserSupport.CSP", "sandbox; img-src *;")
This will allow embedding images from any external website.
If you run Jenkins on Ubuntu and you want to set this permanently, just edit the file /etc/default/jenkins. Under # arguments to pass to java add the following line:
JAVA_ARGS="-Dhudson.model.DirectoryBrowserSupport.CSP=\"sandbox; img-src *;\""
The issue you're seeing is likely related to recent security fixes. See the Configuring Content Security Policy wiki page for details on how to relax the Jenkins configuration.
The CSP header sent by Jenkins can be modified by setting the system property hudson.model.DirectoryBrowserSupport.CSP:
If its value is the empty string, e.g. java -Dhudson.model.DirectoryBrowserSupport.CSP= -jar jenkins.war then the header will not be sent at all.
(Warning!) This is potentially very unsafe and should only be used after reviewing the overall security setup.
You can experiment with different settings using the Jenkins Script Console.
Also as the wiki page notes, make sure you've upgraded to HTML Publisher 1.10 (or later).
I know the original question was for Linux, but this will also help out the Windows users... If you have Jenkins installed as a service (starting from Jenkins.exe) you will need to change the arguments in jenkins.xml for that property to persist.
If you are going to use the unsafe blank option remember to put the parameter in quotes. Below is my example line from jenkins.xml:
<arguments>-Xrs -Xmx1048m -XX:MaxPermSize=512m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle "-Dhudson.model.DirectoryBrowserSupport.CSP= " -jar "%BASE%\jenkins.war" --httpPort=8080</arguments>
If you are using Red Hat then update JENKINS_JAVA_OPTIONS

Resources