Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[4.0] Reset workflow when changing the category #22180

Closed

Conversation

bembelimen
Copy link
Contributor

Pull Request for Issue #21973 .

Summary of Changes

Resets the workflow, when the category is changed and a new workflow applied

Testing Instructions

  • Create 2 workflows and assign them to 2 different categories

  • Create an article for category 1

  • Execute transitions

  • Change the category

  • Do the same with the batch => move

Expected result

if category is changed and they have different workflows the new workflow is assigned

@brianteeman
Copy link
Contributor

I was concerned that when you changed the category what would happen to the stage/transition/condition of the item if the new workflow had different stage/transition/condition.

I didn't get as far as testing that because if you change the category then the stage/transition/condition changes to the default one.

To test this yourself create two identical workflow and assign each to a category

Create an article in category 1 and change the state to unpublished
Then change the category of the article to category 2 and it will be automatically published (the default of the new workflow)

I know that this PR says it "resets" the workflow so in that case it could be said to be correct as it does what you say but without any notification in joomla itself it is definitely never going to be expected that changing the category of an article could publish it.

Sorry but I don't have any suggestion as I cannot see a way around this other than only having one workflow enabled per site


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

@brianteeman
Copy link
Contributor

I have tested this item 🔴 unsuccessfully on 3b50277


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

@brianteeman
Copy link
Contributor

I am at a drupal sprint and just checked how their workflow stuff works specifically the multiple workflows.

Drupal does allow multiple workflows on the site but you can only have one workflow for each content-type. There is no way to change a workflow based on taxonomy which in our terms means one workflow per component. /cc @wilsonge

@wilsonge
Copy link
Contributor

So you're suggesting that we shouldn't allow changing of workflows in a given category?

@brianteeman
Copy link
Contributor

I am saying more than that - there should only be one workflow per component

@bembelimen
Copy link
Contributor Author

I still think, that changing a category should not change the workflow, but I also think, that Joomla! shouldn't limit itself in terms of the number of workflows, just because Drupal does it... because Joomla! can handle unlimited workflows per component...

@brianteeman
Copy link
Contributor

My point as shown by examples above is that we are not able to have multiple workflows per component that actually work

@csthomas
Copy link
Contributor

I still think, that changing a category should not change the workflow...

Me too. The approver may want to move the article to a more appropriate category or subcategory not visible by author.

@brianteeman
Copy link
Contributor

Thats the entire point. If you move content then you expect it to work the same as everything else in the category. Remember that you could have a stage called X than has condition Y in category 1 but a stage called X with a condition Z in the new category. How can you tell the difference

@bembelimen bembelimen closed this Oct 27, 2018
@bembelimen bembelimen deleted the workflow-category-switch branch December 30, 2018 23:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants