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
Containers as files outside default host #17749
Comments
jdotcms
added a commit
that referenced
this issue
Jan 15, 2020
…ner is not part of the current host, and also make several fixes to make it work on the edit mode
jdotcms
added a commit
that referenced
this issue
Jan 16, 2020
jdotcms
added a commit
that referenced
this issue
Jan 16, 2020
jdotcms
added a commit
that referenced
this issue
Jan 16, 2020
jdotcms
added a commit
that referenced
this issue
Jan 16, 2020
jdotcms
added a commit
that referenced
this issue
Jan 18, 2020
…t when it is a container in the default host
jdotcms
added a commit
that referenced
this issue
Jan 18, 2020
…t when it is a container in the default host 2
fmontes
pushed a commit
that referenced
this issue
Jan 27, 2020
* #17749 this first effort renders on the absolute path when the container is not part of the current host, and also make several fixes to make it work on the edit mode * #17749 start adding unit test * #17749 adding unit test for HostUtil * #17749 adding fixes and unit test * #17749 a new test case when the host does not exists, returns the default * #17749 Adding fixes to be able to add an container on non-default host when it is a container in the default host * #17749 Adding fixes to be able to add an container on non-default host when it is a container in the default host 2 * #17749 feedback done
Still not saving content. |
I would like to test this when there is a fix - I can help QA |
PR: #17950 |
Leaving all code changes related to this card into |
We will move the card to 5.2.7 |
PR: #18033 |
Note for QA:
|
How I tested:
Also In demo:
|
Fixed, tested on master // Postgres // FF |
This was referenced May 29, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Containers as files are not working properly outside default host.
parseContainer
directive).Any of these combinations (path without host, path with host, identifier) can be use with the same result.
The code is not going to find a host in the path even if the
parseContainer
have it and when there is no host the code will try to find the container in the default host instead of current host (https://github.com/dotCMS/core/blob/master/dotCMS/src/main/java/com/dotmarketing/portlets/containers/business/FileAssetContainerUtil.java#L165-L172), which is wrong, and when that happen no content can be add to the page.Things we saw:
/v1/page/{pageId}/content
(PageResource
) is called with containers without a host even if the template is using the host in theparseContainer
directive.http://localhost:8080/api/v1/page/render/folder1/page2?language_id=1
) is removing the host before to send it to the FE:Possible solutions
parseContainer
does not have it we could append the current host to it.If the
parseContainer
already has a host we should respect it.Acceptance Criteria
The text was updated successfully, but these errors were encountered: