Nice idea.
It would be useful since tooltips have been removed from admin.

Impossible to guess without seeing the code

@hgh-esn
By the way: I've read your 3.9-documentation that you've linked to in your first comment. Are you aware that fields system_data and custom_data are removed from table #__extensions in Joomla 4?
See further discussion here: #19348
The discussion/the issue is still open if the related PRs shall be reverted but...

@ghazal

It would be useful since tooltips have been removed from admin.

I don't see the connection with this issue. And old hover tooltips for descriptions will be replaced by another solution as far as I know.

@ReLater

Are you aware that fields system_data and custom_data are removed from table #__extensions in Joomla 4?

... yes I am - and was surprised about that. But in my J4-patch I have created a new field named "note" in #__extensions. So it should be not a problem.

The only problem that I have at the moment is the duplicate display of the note-field in the formview. If this is cleared I will make all necessary steps to get it into the core.

@ReLater
In j3.X, there is some much useful information in those "old hover tooltips". I really hope devs developing j4 extensions will get the drift, ie their removal.
So, I assumed that any additional information, wherever it is, would be welcomed.

@ReLater, @brian

here comes a screenshot from the file, that - for me - produces the messing code.

the original file is: .../administrator/components/com_plugins/tmpl/plugin/edit.php

The green framed area is code, I putted in.

When I comment out the code in the red frame, the issue isn't there - but also the fields "Status" and "Access" are missing ;).
So I think the issue comes from the "LayoutHelper::render('joomla.edit.global', $this)" statement.

This morning I inspected the code around 'joomla.edit.global'
(we find it in: ".../layouts/joomla/edit/global.php") ;)

`<?php
/**

• @Package Joomla.Site
• @subpackage Layout
• @copyright Copyright (C) 2005 - 2019 Open Source Matters, Inc. All rights reserved.
• @license GNU General Public License version 2 or later; see LICENSE.txt
  */

defined('JPATH_BASE') or die;

use Joomla\CMS\Component\ComponentHelper;
use Joomla\CMS\Factory;
use Joomla\CMS\Language\Multilanguage;

$app = Factory::getApplication();
$form = $displayData->getForm();
$input = $app->input;
$component = $input->getCmd('option', 'com_content');

if ($component === 'com_categories')
{
$extension = $input->getCmd('extension', 'com_content');
$parts = explode('.', $extension);
$component = $parts[0];
}

$saveHistory = ComponentHelper::getParams($component)->get('save_history', 0);

$fields = $displayData->get('fields') ?: array(
'transition',
array('parent', 'parent_id'),
array('published', 'state', 'enabled'),
array('category', 'catid'),
'featured',
'sticky',
'access',
'id',
'language',
'tags',
'note',
'version_note',
);
...`
When I comment out the 'note' field, my problem is solved.

My decision is to build in a code-switch as:
If ($component !== 'com_plugins' { .... do that above } else { ... do that above without the fields 'note', 'version_note' }

In first tests it runs perfect. 👍

do that above without the fields 'note', 'version_note'

You don't have to exclude 'version_note' because this field doesn't exist in plugins. No "automatic" output will happen then.

What I would do:

• Leave the note field where it is without changing the JLayout file. Remove your custom green output block for note. Create a pr with the basic changes and wait for comments if somebody doesn't want the field where it automatically is. That's one of the reasons why we are on GitHub. You can change and adjust your pr stepwise. The first step is that it works and others can test the functionality.
• or (I think that should work too but haven't checked it): Populate $displayData['fields'} before the JLayout is called.
• or create an override for JLayout /layouts/joomla/edit/global.php only for com_plugins.

Again: That's what I would do (starting with the first solution) but I don't have to decide that.

Hi to all,

at the moment, I'm gathering all informations together to make a branch later.
But I have some questions.

The feature needs a new field named "note" in the db-table "#__extensions".
In my test-environment I used phpMyAdmin to create the field via an ALTER table command.

In Joomla, this field must be created on installation. Therefore I have identified a file "joomla.sql" in the folders

../installation/sql/mysql/ and ../installation/sql/postgresql/

Questions:

Database:

1. What is the difference-usage for those two folders?
2. Are that the areas, where to define the sql for db-tables for full-installations?
3. Where are the areas, when using an Joomla-update-package?

Languages:
I have to setup 2 language-keys for the note-field.
This entries must be in the language-folder/-file: /administrator/language/en-GB/en-GB.com_plugins.ini

How is the process to get the international-translation?

What is the difference-usage for those two folders?

One is for mysql databases the other one for postgresql databases. Both can be used in Joomla.

Are that the areas, where to define the sql for db-tables for full-installations?

Yes.

Where are the areas, when using an Joomla-update-package?

administrator/components/com_admin/sql/updates/

How is the process to get the international-translation?

"Automatically". Your pr gets a "Language Change" label. You don't have to do more. Just en-GB.*.ini

Set to "closed" on behalf of @Quy by The JTracker Application at issues.joomla.org/joomla-cms/24920

See PR #24966