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

Image caption support in Plone 5.1.x #38

Closed
wants to merge 4 commits into from

Conversation

tuticapi
Copy link

@tuticapi tuticapi commented May 22, 2020

  • Change the image caption template to use <figure> and <figcaption>.

  • Add an ImageCaptioningEnabler utility which can be enabled via the portal registry setting plone.image_captioning.

Merge with:
plone/mockup#978
plone/Products.CMFPlone#3099
#38
plone/plone.app.upgrade#232

@mister-roboto
Copy link

@tuticapi you need to sign the Plone Contributor Agreement in order to merge this pull request.

Learn about the Plone Contributor Agreement: http://docs.plone.org/develop/coredev/docs/contributors_agreement_explained.html

@mister-roboto
Copy link

@tuticapi thanks for creating this Pull Request and help improve Plone!

To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass.

Whenever you feel that the pull request is ready to be tested, either start all jenkins jobs pull requests by yourself, or simply add a comment in this pull request stating:

@jenkins-plone-org please run jobs

With this simple comment all the jobs will be started automatically.

Happy hacking!

@mister-roboto
Copy link

@tuticapi thanks for creating this Pull Request and help improve Plone!

To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass.

Whenever you feel that the pull request is ready to be tested, either start all jenkins jobs pull requests by yourself, or simply add a comment in this pull request stating:

@jenkins-plone-org please run jobs

With this simple comment all the jobs will be started automatically.

Happy hacking!

@tuticapi tuticapi requested a review from esteele May 26, 2020 16:29
@tuticapi
Copy link
Author

@jenkins-plone-org please run jobs

@tuticapi
Copy link
Author

@jenkins-plone-org please run jobs

Copy link
Member

@thet thet left a comment

Choose a reason for hiding this comment

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

I wonder if we can just latest plone.outputfilters in Plone 5.1. There wasn't changed too much. I'd prefer that than to have to maintain two seperate branches.
One thing to note: we're changing the templates here from using the <dl/dt/dd> to <figcaption>, which is a major change. Not sure if that's OK, but let's first test the whole thing.

@thet
Copy link
Member

thet commented Jun 8, 2020

@tuticapi I started a new jenkins run with these 3 PRs together:
plone/mockup#978
plone/Products.CMFPlone#3099
#38

I didn't include the plone/plone.app.upgrade#232 because that would fail and is not necessary to check if all is still working on a fresh install.

This is the jenkins run: https://jenkins.plone.org/job/pull-request-5.1/304/

@thet
Copy link
Member

thet commented Jun 8, 2020

Uhm. I recognized, I wanted to check with plone.outputfilter master :/

@thet
Copy link
Member

thet commented Jun 8, 2020

OK, next try. I created a buildout.coredev branch for 5.1 which depends on plone.outputfilters master/4.0.1: plone/buildout.coredev#658

Now a new Jenkins run with these PRs:
plone/buildout.coredev#658
plone/mockup#978
plone/Products.CMFPlone#3099

(Side note: technically the mockup checkout doesn't do much because the tests don't build a JS bundle.)

This is the Jenkins run: https://jenkins.plone.org/job/pull-request-5.1/305/

Let's see what happens.

@thet
Copy link
Member

thet commented Jun 10, 2020

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.

4 participants