You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This caused some javascript issues when using a view with a custom traverser (something like: @@custom-view/foo/bar).
What I experienced was that some JS ajax calls were done to my context url rather than my "traversed conxtet" URL:
I solved this issue by setting data-base-url to context_state.current_base_url().
Should we rename the data-base-url to data-context-url?
Is it right that in the case of a view like @@custom-view/foo/bar the data-base-url should be the context URL?
What version of Plone/ Addons I am using:
Plone 6.0-latest, but this also happens on Plone 6.1.
The text was updated successfully, but these errors were encountered:
Question
I have some doubts about the
plone_patterns_settings
view.The
data-base-url
is defined asself.context.absolute_url()
, see:Products.CMFPlone/Products/CMFPlone/patterns/view.py
Line 26 in 26c659a
This caused some javascript issues when using a view with a custom traverser (something like:
@@custom-view/foo/bar
).What I experienced was that some JS ajax calls were done to my context url rather than my "traversed conxtet" URL:
I solved this issue by setting
data-base-url
tocontext_state.current_base_url()
.Sample Code:
Should we rename the
data-base-url
todata-context-url
?Is it right that in the case of a view like
@@custom-view/foo/bar
thedata-base-url
should be the context URL?What version of Plone/ Addons I am using:
Plone 6.0-latest, but this also happens on Plone 6.1.
The text was updated successfully, but these errors were encountered: