Feature PR-6.0-dev Pending

User tests: Successful: Unsuccessful:

avatar raj20889
raj20889
1 Mar 2025

Pull Request for Issue #45010

Summary of Changes

  • Made the alias field always visible in the article edit form.
  • Removed the condition that restricted alias visibility to only new articles.
  • Ensured consistency in the form structure and UI.

Testing Instructions

  1. Go to Content → Articles → Edit any article.
  2. The alias field should now be always visible, even for existing articles.
  3. Save the article and verify that the alias updates correctly.

Actual Result BEFORE Applying This Pull Request

  • The alias field was only visible for new articles and hidden for existing ones.

Expected Result AFTER Applying This Pull Request

  • The alias field is always visible, allowing users to modify it when editing an article.

Link to Documentation

Please select:

  • Documentation link for docs.joomla.org:
  • No documentation changes for docs.joomla.org needed
  • Pull Request link for manual.joomla.org:
  • No documentation changes for manual.joomla.org needed
avatar raj20889 raj20889 - open - 1 Mar 2025
avatar raj20889 raj20889 - change - 1 Mar 2025
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 1 Mar 2025
Category Front End com_content
avatar raj20889 raj20889 - change - 1 Mar 2025
Title
Fix: Updated Joomla content form with proper tab handling, field rend…
Fix: Updated Joomla content form with proper tab handling, field rendering, and conditional visibility for images and metadata fields.
avatar raj20889 raj20889 - edited - 1 Mar 2025
avatar raj20889 raj20889 - change - 1 Mar 2025
The description was changed
avatar raj20889 raj20889 - edited - 1 Mar 2025
avatar raj20889
raj20889 - comment - 1 Mar 2025

Hey, I’ve submitted PR #45044 to always show the alias field in the article edit form.
Could someone please review it when they have time? Thanks!

avatar fgsw
fgsw - comment - 3 Apr 2025

@raj20889 Please change in the title "Fix:" to "[5.2]".

avatar HLeithner
HLeithner - comment - 15 Apr 2025

This pull request has been automatically rebased to 6.0-dev.

avatar richard67 richard67 - change - 28 Apr 2025
Title
Fix: Updated Joomla content form with proper tab handling, field rendering, and conditional visibility for images and metadata fields.
[6.0] Updated Joomla content form with proper tab handling, field rendering, and conditional visibility for images and metadata fields.
avatar richard67 richard67 - edited - 28 Apr 2025
avatar richard67 richard67 - change - 28 Apr 2025
Labels Added: Feature PR-6.0-dev
avatar richard67 richard67 - change - 28 Apr 2025
Build 5.2-dev 6.0-dev
avatar ceford ceford - test_item - 2 Jun 2025 - Tested unsuccessfully
avatar ceford
ceford - comment - 2 Jun 2025

I have tested this item 🔴 unsuccessfully on be56882

Testing this in 6.0.0-alpha1-dev: the summary says a lot but the diff only shows one line changed in one file. Should this be a front end test - in which case the instructions make no sense.

I applied the patch and got this error in all edit pages:

0 Call to undefined method Joomla\CMS\Form\Form::renderControlFields() 

Call Stack
# 	Function 	Location
1 	() 	JROOT/components/com_content/tmpl/form/edit.php:153
2 	include() 	JROOT/libraries/src/MVC/View/HtmlView.php:416
3 	Joomla\CMS\MVC\View\HtmlView->loadTemplate() 	JROOT/libraries/src/MVC/View/HtmlView.php:204
4 	Joomla\CMS\MVC\View\HtmlView->display() 	JROOT/components/com_content/src/View/Form/HtmlView.php:197
5 	Joomla\Component\Content\Site\View\Form\HtmlView->display() 	JROOT/libraries/src/MVC/Controller/BaseController.php:697
6 	Joomla\CMS\MVC\Controller\BaseController->display() 	JROOT/components/com_content/src/Controller/DisplayController.php:123
7 	Joomla\Component\Content\Site\Controller\DisplayController->display() 	JROOT/libraries/src/MVC/Controller/BaseController.php:730
8 	Joomla\CMS\MVC\Controller\BaseController->execute() 	JROOT/libraries/src/Dispatcher/ComponentDispatcher.php:143
9 	Joomla\CMS\Dispatcher\ComponentDispatcher->dispatch() 	JROOT/components/com_content/src/Dispatcher/Dispatcher.php:56
10 	Joomla\Component\Content\Site\Dispatcher\Dispatcher->dispatch() 	JROOT/libraries/src/Component/ComponentHelper.php:361
11 	Joomla\CMS\Component\ComponentHelper::renderComponent() 	JROOT/libraries/src/Application/SiteApplication.php:218
12 	Joomla\CMS\Application\SiteApplication->dispatch() 	JROOT/libraries/src/Application/SiteApplication.php:261
13 	Joomla\CMS\Application\SiteApplication->doExecute() 	JROOT/libraries/src/Application/CMSApplication.php:306
14 	Joomla\CMS\Application\CMSApplication->execute() 	JROOT/includes/app.php:58
15 	require_once() 	JROOT/index.php:32 
```<hr /><sub>This comment was created with the <a href="https://github.com/joomla/jissues">J!Tracker Application</a> at <a href="https://issues.joomla.org/tracker/joomla-cms/45044">issues.joomla.org/tracker/joomla-cms/45044</a>.</sub>
avatar brianteeman
brianteeman - comment - 2 Jun 2025

This is only for the front end com_content form. Knowing that the instructions make perfect sense.

avatar exlemor exlemor - test_item - 6 Jun 2025 - Tested successfully
avatar exlemor
exlemor - comment - 6 Jun 2025

I have tested this item ✅ successfully on be56882

Hello Raj, thanks for the work - I have tested this successfully.

I understand this is NOT in this PR, but this led me to realize that it would be great if the backend tooltip of hovering over the Check-In lock would include information on whether someone has checked out an article using Front-End or the Back-end - i.e. currently it only has:

Check-in
Emmanuel Lemor
Friday, 06 June 2025
22:53

This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/45044.

Add a Comment

Login with GitHub to post a comment