FPA reports language constants as components from JCE Topic is solved

[toivo]

The FPA lists language constants as site components.

Test Environment

Wampserver 3.3.1 64bit on Windows 11
PHP 8.1.16
Joomla 4.2.9
JCE 2.9.36 free version
FPA 1.6.6

Example

Components :: Site ::
Core ::
3rd Party:: WF_AGGREGATOR_AUDIO_TITLE (2.9.36) ? | WF_AGGREGATOR_DAILYMOTION_TITLE (2.9.36) ? | WF_AGGREGATOR_VIDEO_TITLE (2.9.36) ? | WF_AGGREGATOR_VIMEO_TITLE (2.9.36) ? | WF_AGGREGATOR_[youtube]_TITLE (2.9.36) ? | WF_FILESYSTEM_JOOMLA_TITLE (2.9.36) ? | WF_LINKS_JOOMLALINKS_TITLE (2.9.36) ? | WF_POPUPS_JCEMEDIABOX_TITLE (2.9.36) ? | WF_LINK_SEARCH_TITLE (2.9.36) ? | WF_ANCHOR_TITLE (2.9.36) ? | WF_ARTICLE_TITLE (2.9.36) ? | WF_ATTRIBUTES_TITLE (2.9.36) ? | WF_AUTOSAVE_TITLE (2.9.36) ? | WF_BROWSER_TITLE (2.9.36) ? | WF_CHARMAP_TITLE (2.9.36) ? | WF_CLEANUP_TITLE (2.9.36) ? | WF_CLIPBOARD_TITLE (2.9.36) ? | WF_CONTEXTMENU_TITLE (2.9.36) ? | WF_DIRECTIONALITY_TITLE (2.9.36) ? | WF_EMOTIONS_TITLE (2.9.36) ? | WF_FONTCOLOR_TITLE (2.9.36) ? | WF_FONTSELECT_TITLE (2.9.36) ? | WF_FONTSIZESELECT_TITLE (2.9.36) ? | WF_FORMATSELECT_TITLE (2.9.36) ? | WF_FULLSCREEN_TITLE (2.9.36) ? | WF_HELP_TITLE (2.9.36) ? | WF_HR_TITLE (2.9.36) ? | WF_IMGMANAGER_TITLE (2.9.36) ? | WF_KITCHENSINK_TITLE (2.9.36) ? | WF_LANGCODE_TITLE (2.9.36) ? | WF_LINK_TITLE (2.9.36) ? | WF_LISTS_TITLE (2.9.36) ? | WF_MEDIA_TITLE (2.9.36) ? | WF_NONBREAKING_TITLE (2.9.36) ? | JCE - Noneditable (1.0.0) ? | WF_PREVIEW_TITLE (2.9.36) ? | WF_PRINT_TITLE (2.9.36) ? | WF_REFERENCE_TITLE (2.9.36) ? | WF_SEARCHREPLACE_TITLE (2.9.36) ? | WF_SOURCE_TITLE (2.9.36) ? | WF_SPELLCHECKER_TITLE (2.9.36) ? | WF_STYLE_TITLE (2.9.36) ? | WF_STYLESELECT_TITLE (2.9.36) ? | WF_TABLE_TITLE (2.9.36) ? | WF_TEXTCASE_TITLE (2.9.36) ? | WF_VISUALBLOCKS_TITLE (2.9.36) ? | WF_VISUALCHARS_TITLE (2.9.36) ? | WF_WORDCOUNT_TITLE (2.9.36) ? |

[frostmakk]

The FPA read the manifest files. These "language constants" are how JCE name these components in the manifest.
They don't exist in the #_extensions table as indicated with a question mark in the FPA.
Here an example from root\components\com_jce\editor\extensions\aggregator\audio.xml:

Code: Select all

<?xml version="1.0" ?>
<extension version="3.4" type="plugin" group="jce" method="upgrade">
	<name>WF_AGGREGATOR_AUDIO_TITLE</name>
	<version>2.9.32</version>
	<creationDate>01-11-2022</creationDate>
	<author>Ryan Demmer</author>
	<authorEmail>[email protected]</authorEmail>
	<authorUrl>https://www.joomlacontenteditor.net/</authorUrl>
	<copyright>Copyright (C) 2006 - 2022 Ryan Demmer. All rights reserved</copyright>
	<license>GNU/GPL Version 2 or later - http://www.gnu.org/licenses/gpl-2.0.html</license>
	<description>WF_AGGREGATOR_AUDIO_DESC</description>
	<files>
		<filename>audio.php</filename>
		<folder>audio</folder>
	</files>

[toivo]

According to your manifest example, the type of the extension is supposed to be plugin, not component.

[frostmakk]

JCE has put it in the components folder, so that is where it is sorted. That's just how the FPA works.

[toivo]

So, the way JCE or the Widget Factory makes available its or TinyMCE's plugins is the primary reason and the logic in the FPA, to search manifests beyond the top level of components, is the secondary reason. Understood.