The plugin needs to be added to the list of core extensions here libraries/src/Extension/ExtensionHelper.php

Thank you @brianteeman for review, will update the pr soon with the changes.

It might be that we have to move this to 6.1 as soon as we have created a 6.1-dev branch necause 6.0 has already had feature freeze with 6.0.0-beta1.

Thanks @brianteeman and @richard67 for the review. I’ve made all the suggested changes. I really appreciate your time and feedback.

@Dileepadari Now you have produced invalid SQL syntax in the update SQL scripts by using only a part of administrator/components/com_admin/sql/updates/mysql/6.0.0-2025-08-02.sql.

The correct syntax is (exmaple from the mentioned other SQL):

INSERT INTO `#__extensions` (`package_id`, `name`, `type`, `element`, `folder`, `client_id`, `enabled`, `access`, `protected`, `locked`, `manifest_cache`, `params`, `custom_data`, `ordering`, `state`)
SELECT 0, 'plg_schemaorg_article', 'plugin', 'article', 'schemaorg', 0, 0, 1, 0, 1, '', '{}', '', -1, 0
WHERE NOT EXISTS (SELECT * FROM `#__extensions` e WHERE e.`type` = 'plugin' AND e.`element` = 'article' AND e.`folder` = 'schemaorg' AND e.`client_id` = 0);

It is an INSERT INTO ... SELECT ... statement which should not have a VALUES key word.

Your statement has still VALUES but no SELECT.

This will result in an SQL syntax error.

So it seems you did not check your SQL e.g. in phpMyAdmin.

Thank you @Dileepadari this is a very nice addition to the workflow 👍

Hi @richard67, sorry for that. Can you let me know how can i test with PhpMyAdmin. Should I replace the #__extensions with the table name including table prefix?

Hi @richard67, sorry for that. Can you let me know how can i test with PhpMyAdmin. Should I replace the #__extensions with the table name including table prefix?

That would be one way to test it on the current Joomla installation.

Another way would be to copy the CREATE TABLE statement from the base.sql and use it as it is to create an #__extesions table without the suffix to be replaced, then you could fiddle with SQL in that table without having to replace the prefix in your SQL statement and without messing up the table from the Joomla installation.

And when developing database stuff for Joomla it is a good idea to have a PostgreSQL database in addition to the MySQL (or MariaDB).

Thanks for the info, it helps a lot in testing quickly.

thanks for adding the filter etc

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

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

@Dileepadari - thank you for the PR - are planning to work on this? as there are changes requested.

are planning to work on this? as there are changes requested.

Thank you for the reminder, will update this ASAP

I wanted to use this on a site and tested it by making an installable plugin from it. See github.com/HermanPeeren/workflow-plugins/tree/main/src/plg_workflow_category.

• an error when using this: a category is required, but in the initial stage the plugin prevents saving any category. So I cannot save a new item. There should be a default category (to be set in the plugin parameters, not in the action form), which can default to the "uncategorised" category. And that category should be set for the initial stage of the workflow. More general this could be an improvement for the workflow plugins: if some value is set with a transaction, then we cannot set that value for the initial stage.
• I added some comments to the code to make it more general, not only com_content: split $context into the component name and the table name. Then instantiate the table directly from the component's MVCFactory.
• The processArticle() method (which should be renamed to processItem()) boots the component (here com_content) at every call, but it is called in a loop: $pks is an array, because it can be used in a batch command. Boot the component before the loop.
• the layout folder should not be anymore under <files> in the manifest. That js is now in the media folder.
• I think there are two superfluous lines changin the modified and modified_by properties.
• Some minor things, like adding a return type to a method (2x), and a static cal to a non-static method,

I wanted to use this on a site and tested it by making an installable plugin from it. See github.com/HermanPeeren/workflow-plugins/tree/main/src/plg_workflow_category.

• an error when using this: a category is required, but in the initial stage the plugin prevents saving any category. So I cannot save a new item. There should be a default category (to be set in the plugin parameters, not in the action form), which can default to the "uncategorised" category. And that category should be set for the initial stage of the workflow. More general this could be an improvement for the workflow plugins: if some value is set with a transaction, then we cannot set that value for the initial stage.
• I added some comments to the code in my repo to make it more general, not only com_content: split $context into the component name and the table name. Then instantiate the table directly from the component's MVCFactory.
• The processArticle() method (which should be renamed to processItem()) boots the component (here com_content) at every call, but it is called in a loop: $pks is an array, because it can be used in a batch command. Boot the component before the loop.
• the layout folder should not be anymore under <files> in the manifest. That js is now in the media folder.
• I think there are two superfluous lines changin the modified and modified_by properties.
• Some minor things, like adding a return type to a method (2x), and a static cal to a non-static method,

I wanted to use this on a site and tested it by making an installable plugin from it. See github.com/HermanPeeren/workflow-plugins/tree/main/src/plg_workflow_category.

• an error when using this: a category is required, but in the initial stage the plugin prevents saving any category. So I cannot save a new item. There should be a default category (to be set in the plugin parameters, not in the action form), which can default to the "uncategorised" category. And that category should be set for the initial stage of the workflow. More general this could be an improvement for the workflow plugins: if some value is set with a transaction, then we cannot set that value for the initial stage.
• I added some comments to the code in my repo (my comments start with HP:) to make it more general, not only com_content: split $context into the component name and the table name. Then instantiate the table directly from the component's MVCFactory.
• The processArticle() method (which should be renamed to processItem()) boots the component (here com_content) at every call, but it is called in a loop: $pks is an array, because it can be used in a batch command. Boot the component before the loop.
• the layout folder should not be anymore under <files> in the manifest. That js is now in the media folder.
• I think there are two superfluous lines changin the modified and modified_by properties.
• Some minor things, like adding a return type to a method (2x), and a static cal to a non-static method,

• Some minor things, like adding a return type to a method (2x), and a static cal to a non-static method,

Thanks @HermanPeeren for taking time and giving your detailed review and suggestions, I have updated the pr accordingly. Please test it if you get some time. Thanks everyone for the reviews.

Category is not displayed when edit item (the field is disabled)

Thanks @heelc29 for the review, I resolved all the comments you have given but for the category not showing part, I am not sure why its not displayed. The category change is disabled when you are editing the article but still you will be able to see the category. you will be able to set the category if you are creating the article or if the category is not set. Please provide me with theme details if you still can't see the category, I'll try to debug.

This pull request has conflicts, please resolve those before we can evaluate the pull request.

@Dileepadari why is the category change disabled? I might want to change the category myself?

@Dileepadari why is the category change disabled? I might want to change the category myself?

Hi @coolcat-creations , Thanks for the review, I think it makes sense to have flexibility over other workflows, I have implemented it and updated it here. Thanks for the suggestion.

@Dileepadari why is the category change disabled? I might want to change the category myself?

Hi @coolcat-creations , Thanks for the review, I think it makes sense to have flexibility over other workflows, I have implemented and updated it here. Thanks for the suggestion.