[#47248] - [6.1] Fix workflow graph strings and assets
- Fixed in Code Base
- 13 Mar 2026
- Medium
- Build: 5.4-dev
- # 47248
- Diff
- Vikash-Kumar-23:fix-workflow-6.1
User tests: Successful: Unsuccessful:
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 :
Expected result AFTER applying this Pull Request
if workflow_enabled is off:
if workflow_enabled is on:
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
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Repository Administration com_admin SQL |
| Labels |
Added:
PR-5.4-dev
|
||
| Category | Repository Administration com_admin SQL | ⇒ | Libraries |
| Labels |
Added:
PR-6.1-dev
|
||
| Title |
|
||||||
| Labels |
Added:
bug
Removed: PR-5.4-dev |
||
@Dileepadari can you please check this PR. Thanks.
The workflow graph scripts are required only when workflows are enabled. Tested and confirmed that after this change the scripts and styles are no longer included unnecessarily. Thanks @Vikash-Kumar-23 for the pr.
Tested successfully on Joomla 6.1-dev.
I have tested this item ✅ successfully on de12316
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/47248.
I have tested this item ✅ successfully on de12316
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/47248.
| Status | Pending | ⇒ | Ready to Commit |
RTC
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/47248.
| Labels |
Added:
RTC
|
||
Thanks @Vikash-Kumar-23 and all testers.
| Status | Ready to Commit | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2026-03-13 17:17:48 |
| Closed_By | ⇒ | tecpromotion |
@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.