Skip to content

Add seperate Plone 5 profile#53

Merged
maethu merged 4 commits into
masterfrom
tg_plone5
Dec 16, 2019
Merged

Add seperate Plone 5 profile#53
maethu merged 4 commits into
masterfrom
tg_plone5

Conversation

@tinagerber

Copy link
Copy Markdown
Member

closes #52

@tinagerber tinagerber self-assigned this Nov 27, 2019
@tinagerber tinagerber requested a review from a team November 27, 2019 08:32
Comment thread ftw/referencewidget/profiles/default_plone5/registry.xml Outdated
Comment thread ftw/referencewidget/profiles/default_plone5/registry.xml Outdated
Comment thread ftw/referencewidget/profiles/default_plone5/registry.xml Outdated
Comment thread ftw/referencewidget/profiles/default_plone5/registry.xml
Comment thread ftw/referencewidget/profiles/default_plone5/registry.xml Outdated
Comment thread ftw/referencewidget/profiles/default_plone5/registry.xml Outdated
@tinagerber tinagerber force-pushed the tg_plone5 branch 2 times, most recently from 2fd4771 to 05596b0 Compare November 27, 2019 09:47
@tinagerber tinagerber requested a review from jone November 27, 2019 09:51

@djowett-ftw djowett-ftw left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please correct me if I'm wrong - but I'm concerned that this JS will still end up in the legacy bundle in production - we are declaring Shim resources with "deps" and the JS does not all seem to follow the RequireJS module pattern IIUC.

I think it would be worth testing this in production mode?

Comment thread ftw/referencewidget/profiles/default_plone5/registry.xml Outdated
@djowett-ftw

Copy link
Copy Markdown

Just to note - this references collective.js.jqueryui which breaks with this issue for Plone 5 resources. This unmerged PR seems to be the fix collective/collective.js.jqueryui#38, but until it's merged we'll need the branch it references

@tinagerber tinagerber requested a review from buchi December 9, 2019 14:09
@tinagerber tinagerber force-pushed the tg_plone5 branch 2 times, most recently from 1ab1c40 to d4d4a18 Compare December 9, 2019 14:54

@maethu maethu left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added a little fix and tested it with instance fg and instance console. It seems to work fine now.

@maethu maethu merged commit 8371618 into master Dec 16, 2019
@maethu maethu deleted the tg_plone5 branch December 16, 2019 07:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add separate plone 5 profile (include uninstall profile)

4 participants