bug PR-6.1-dev Pending

User tests: Successful: Unsuccessful:

avatar Vikash-Kumar-23
Vikash-Kumar-23
27 Feb 2026

Pull Request resolves #47224

  • I read the Generative AI policy and my contribution is either not created with the help of AI or is compatible with the policy and GNU/GPL 2 or later.

Summary of Changes

Testing Instructions

Install Joomla 6.1-dev.

Go to Content -> Articles -> Options.

Set Enable Workflows to No.

Open any article for editing.

View the page source (Ctrl+U) and search for workflow-graph.

Result: No assets or strings should be found.

Return to Options and set Enable Workflows to Yes.

Refresh the article edit page and view source again.

Result: workflow-graph-client assets should now be present, confirming the feature still works when enabled.

Actual result BEFORE applying this Pull Request

Even if workflow_enabled is off :
Screenshot (1582)
Screenshot (1584)

Expected result AFTER applying this Pull Request

if workflow_enabled is off:
Screenshot (1586)

if workflow_enabled is on:
Screenshot (1588)

Link to documentations

Please select:

  • Documentation link for guide.joomla.org:

  • No documentation changes for guide.joomla.org needed

  • Pull Request link for manual.joomla.org:

  • No documentation changes for manual.joomla.org needed

avatar Vikash-Kumar-23 Vikash-Kumar-23 - open - 27 Feb 2026
avatar Vikash-Kumar-23 Vikash-Kumar-23 - change - 27 Feb 2026
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 27 Feb 2026
Category Repository Administration com_admin SQL
avatar Vikash-Kumar-23 Vikash-Kumar-23 - change - 27 Feb 2026
Labels Added: PR-5.4-dev
avatar joomla-cms-bot joomla-cms-bot - change - 27 Feb 2026
Category Repository Administration com_admin SQL Libraries
avatar Vikash-Kumar-23 Vikash-Kumar-23 - change - 28 Feb 2026
Labels Added: PR-6.1-dev
avatar richard67 richard67 - change - 28 Feb 2026
Title
Fix workflow 6.1
[6.1] Fix workflow graph strings and assets
avatar richard67 richard67 - edited - 28 Feb 2026
avatar Vikash-Kumar-23 Vikash-Kumar-23 - change - 2 Mar 2026
Labels Added: bug
Removed: PR-5.4-dev
avatar richard67
richard67 - comment - 5 Mar 2026

@Vikash-Kumar-23 When GitHub shows that the branch is not up to date, it does not need to use the branch update button every time. It is only a problem if there are conflicts shown, which is not the case here. SO no need to use the branch update button all the time.

avatar tecpromotion
tecpromotion - comment - 9 Mar 2026

@Dileepadari can you please check this PR. Thanks.

Add a Comment

Login with GitHub to post a comment