How to add language icons in liferay DXP - liferay-7

How to add the Language icon image in liferay 7(liferay-ce-portal-7.0-ga4).
I have followed the steps mentioned in following article,
https://web.liferay.com/web/salman.khan/blog/-/blogs/add-a-new-language-to-liferay-detailed-step-by-step-
After the language configuration I can be able to see the languages but not the flags on web content forms.
So I created the custom theme to add the language file and added th_TH.png file in theme\src\images\language\th_TH.png. But din't work.
Then I tried the implementing the lexicon-icon approach mention in,
how can i add a new language in liferay 7?
Still I am not able to see the language images.
Please refer the screenshot for details,
Theme-layout and file location

To add a custom icon that is not supported yet you need to add 2 artefacts into the theme. Liferay using 2 things for displaying icons. Somewhere it uses png flag and somewhere svg you need to adjust both.
Have a look at this sample project. https://github.com/mir333/custom-flag-admin-theme
It takes the admin theme of Liferay (it is a copy so it needs to be kept in sync with updates) and adds a new flag to the admin theme. The magic is in adding the flag into the lexicon. Under the hood, it takes the added flag svg files and recompiles the icons.svg files to include it.

To anyone who still have issue showing the flag, I just want to point out that this helped me: https://stackoverflow.com/a/45907250
As described, open the icons.svg and add your flag's svg code in as a symbol with the id "xx-yy" (your language and country code, in lowercase).
The flag does not magically generate just from putting the flags-xx-YY.svg file into lexicon folder, not for me at least.

Related

Is it possible to build a LibreOffice document from code similar to the way a web page is built from HTML and CSS?

Is it possible to build a LibreOffice document from code similar to the way a web page is built from HTML and CSS? Can one write an ODF file in which the content and styling are separate, and then/view open in LibreOffice? If so, can one write the code in a text editor as done for HTML/CSS?
There area two reasons I now ask. 1) When I need to make a style change in LibreOffice I have to manually make the same adjustments in a hundred places, such as changing the style of block quotes. 2) I'd like to build documents from a database of text.
I found a question on this in relation to databases but it was about eight years old.
Thank you for any direction you may be able to provide.
Unzip an .odt file that contains styles. You will see two files, content.xml and styles.xml. Edit these files using a text editor and then zip the folder back up to get a modified .odt file.
Be aware that there are two types of styles in the XML files. Named styles are what most people think of as styles, whereas automatic styles are custom formatting, like when you select some text and change the font directly.
The link from tohuwawohu describes utilities to work programmatically with the file. Also as mentioned in the link, it's not too hard to write code yourself. For example in python, import the built-in libraries zipfile and xml.etree.

Rename README.md to custom name and use as a project description

I do apologize if similar question already put, but I haven't found one.
I would like to change the default project description file name (called README.md) to be a custom name (let's say XXX.md) and I wonder if it is possible to be the XXX.md the initial readme file for the project (typical situation: you open the project Code page and you will see the content of XXX.md down at bottom).
I would like to verify if this approach possible in general, but I am mainly interested in Github and Bitbucket services. I briefly checked project settings and I cannot find there such customization. Is it even possible?
GitHub, at least, doesn't provide the ability to do this. It is possible to use a different format (e.g., README.asciidoc or README.rst), but the root file must be called README.
Note that you can include other text markup documents like this and they'll be rendered if they're visited, it's just that they won't appear at the bottom of the file listing like a README will.

Howto to configure TCA settings and save them globaly

I'm configuring a new website with TYPO3 v. 9.5.
I would like to configure TCA settings to make it possible to force editors to fill fields in content elements like media or news.
In former times I was able to put this settings into a file typo3conf/extTables.php.
In my investigations I found, that I have to put configurations into a directory Configuration/TCA/Overrides of an extension.
I tested it with the extension tx_news like this:
I put this code in a file called test.php as a test and example.
This code forces the editor to always enter an archive date.
This works for me, but after an extension update, this code might be lost and I cannot configure the fields of core extensions for example to force an editor to always enter a title of a content element.
My question is, how can I store this configurations update save within the configuration environment?
Thank you in advance,
Ralf
Depending on your modifications you need to consider some aspects:
always use a filename according to the table your modifications belong.
so for the news records it should be: Configuration/TCA/Overrides/tx_news_domain_model_news.php
make sure your modifications are loaded after the first initial configuration: make a dependency to the original extension.

Changing the Moodle footer logo

How to change the Moodle logo which will be displayed at the footer page and change to some other logo? As per the given link 1 I have tried but I could not find the footer.html file in my themes folder.
So please help me with some other method (which does not use local machine because I'm working with a remote machine where I could access only the Moodle site, and nothing more than that) to change the logo and link of Moodle.
This depends on your theme - So you're not going to get a precise answer unless you post more details. But here's the gist:
Every theme is made in parts. Normally, you have a header, a content, a sidebar (or two) and a footer.
You want to be editing the footer file.
The footer file is going to be something within the lines of footer.html or footer.php... Something like that. Again, every theme is different so it could be called something completely different. Sometimes, you just need to dig around.
Please also consider that your footer file may also be contained in a sub-directory in your theme folder. So make sure you have a proper look before deciding to "call off the search".
Anyway, once you've found your footer file (Whatever it's called), you'll want to open it and find the image.
If the image is inserted as a HTML reference of location, you can find it by Ctrl+F and typing in the name of the image file. E.g. "footer.jpeg" or whatever.
If the image is inserted as a PHP relative reference, e.g. "$FooterImage" then don't change that, instead, find out where the variable is pointing to in terms of the file-path, and go and edit that image file via FTP instead. You don't have to keep the PHP variable, but I'd keep it in for code-integrity purposes.
Tip for the future: Please include information like name of theme and Moodle version. It enables us to help you better.
Clean Theme:
Things are a bit different with Clean Theme as it doesn't have a single footer file.
You need to go into all layout files one at a time.
Look for this div:
<footer id="page-footer">
...
</footer>
In this footer, you will find a PHP command that says:
echo $OUTPUT->home_link();
To remove the logo, remove this line.
To replace the logo, you can either:
Replace the "home_link" reference in PHP to point to the new image file.
Or
Remove the PHP line and replace it with
?><img src="link_to_your_image" alt="Logo"><?PHP
Remember, you will need to do this for all layout files.
Have a look at Footer replacement at the official Moodle Documentation. Hope that helps.

Why don't the Target 8 files implement the project as described in the tutorial?

In Target 8: Define a Custom DOM Tag, the reader is told about custom DOM tags that can be created by extending other tags. A sample is described for an example called "x-converter" before listing the files as "These files implement the app:".
The three files are...
a drseuss.html file (not sure why there's a sudden deviation in the project name and the HTML file, as opposed to the matching names in previous tutorials...),
a converter-element.html file,
and a convertercomponent.dart file.
I tried creating a new application in the latest Dart editor, and replaced the default HTML file contents with that of drseuss.html, replaced the default dart file contents with that of convertercomponent.dart, and added converter-element.html file.
After fixing an include issue (the file from the tutorial refers to drseuss.css and not the default project name's CSS file), I only see the following in the Chromium browser.
As you can see, the element described in the tutorial (converter-element) doesn't show up. Why don't the files provided for the project result in what's shown in the tutorial?
For reference, here's what's shown in the tutorial.
Web UI requires the build.dart script which compiles the various components into the executable output HTML+Dart.
Take a look at the parent folder in the github src that you reference, and you will see the build.dart script.
In addition, you will need the pubspec.yaml from that folder, too, which includes web_ui package, which brings in the dwc tool(Dart Web Components compiler) used by build.dart.
Take a look at the article Tools for Web UI for more information about dwc and build.dart, and Target 6 - Getting Started with Web UI which covers similar ground, but in a tutorial format.