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

Changing the encoder in "Advanced Configuration" does not work. THe system continues to use the old encoder. #9064

Closed
walt93 opened this issue May 18, 2024 · 2 comments
Labels

Comments

@walt93
Copy link
Collaborator

walt93 commented May 18, 2024

Describe the bug
Changing the encoder does not work; the system continues to use the old encoder.

To Reproduce
Steps to reproduce the behavior:
0. Because your encoder does not work (is stuck, see previous bug report), install a new one.

  1. Go to Site Configurations
  2. Click on Advanced Configuration
  3. Enter the address of your new encoder
  4. Save the configuration
  5. Open the encoder
  6. Observe that it is the previous encoder. The one you just provisioned is not used.

Expected behavior
The system to use the encoder it is told to.

@walt93 walt93 added the bug label May 18, 2024
@walt93
Copy link
Collaborator Author

walt93 commented May 18, 2024

Update: After doing a clear cache directory / Rebuild site map it will now open the newly provisioned encoder.

You should not need to do the chicken dance when we have changed configuration and hit "Save". "Save" should flush the cache.

@DanielnetoDotCom
Copy link
Member

I am not sure what you mean, Is it still a problem with the new encoder?

@walt93 walt93 closed this as completed May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants