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

Base tag differs from actual URL #1710

Merged
merged 2 commits into from
Dec 15, 2016
Merged

Base tag differs from actual URL #1710

merged 2 commits into from
Dec 15, 2016

Conversation

rodfersou
Copy link
Member

@rodfersou rodfersou commented Aug 9, 2016

@rodfersou rodfersou force-pushed the issue_86 branch 2 times, most recently from 07aa14d to f5a7f6b Compare August 9, 2016 13:37
@rodfersou
Copy link
Member Author

@plone/framework-team can someone take a look at these PR please?

@jensens
Copy link
Sponsor Member

jensens commented Aug 26, 2016

@rodfersou needs rebase, thanks!

@rodfersou
Copy link
Member Author

@jensens done

@rodfersou
Copy link
Member Author

@jensens don't forget that this pull request is related with this pull request too: plone/plone.app.layout#87

@rodfersou
Copy link
Member Author

@rodfersou
Copy link
Member Author

@jensens @hvelarde green

@jensens
Copy link
Sponsor Member

jensens commented Aug 29, 2016

ok from my side. I'd like to have someone with more insight on base tag to have a quick look.

@thet, iirc you fiddled in past with base tags?

This needs merge together with plone/plone.app.layout/pull/87

@jensens jensens merged commit 189eb4f into 4.3.x Dec 15, 2016
@jensens jensens deleted the issue_86 branch December 15, 2016 16:46
@jensens
Copy link
Sponsor Member

jensens commented Dec 15, 2016

do we need this in 5.1 too or was this fixed there alrready?

@hvelarde
Copy link
Member

this is for Plone 4 only; on Plone 5 the <base> tag was removed long ago.

@rodfersou
Copy link
Member Author

👏

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

Successfully merging this pull request may close these issues.

3 participants