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

dotCMS Cache problems editing workflows #13929

Closed
bryanboza opened this issue Mar 21, 2018 · 2 comments
Closed

dotCMS Cache problems editing workflows #13929

bryanboza opened this issue Mar 21, 2018 · 2 comments

Comments

@bryanboza
Copy link
Contributor

We have a cache error when you are editing some workflow scheme, this because we are not deleting the previous version from cache.

Expected Behavior

We need update this content in the cache when you save the changes

Current Behavior

We are not deleting the content from cache and for example:

If you archive some content and then you try to get the schemes of the content type via REST, we are getting the scheme with the archived property in false

Steps to Reproduce (for bugs)

  1. Create a new Workflow
  2. Associate this workflow to some content type
  3. Via REST try to get all the schemes of this content type using this rest: http://localhost:8080/api/v1/workflow/schemes/schemescontenttypes/{contentTypeId}
  4. Go via backend and archive this scheme
  5. Made again the same call to the rest

Your Environment

Tested in the last master // postgres // FF

@bryanboza bryanboza added this to the Cody Current milestone Mar 21, 2018
@bryanboza bryanboza changed the title dotCMS Cache editing workflows dotCMS Cache problems editing workflows Mar 21, 2018
@jgambarios
Copy link
Contributor

PR: #13930

jgambarios pushed a commit that referenced this issue Mar 21, 2018
* Fixing issues with the unit test

* #13581 fixing the sort on copy, the multitree was not respecting the treeorder

* #13929 fixing a cache issue for find by contenttype on workflows
@bryanboza
Copy link
Contributor Author

Fixed, tested on master and now we invalidate the cache when you save changes in the schema

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants