- NTLM authenticationNTLM authentication
- BlogBlog
- BluemindBluemind
- BPMBPM
- CalendarCalendar
- CaptchEtatCaptchEtat
- CartCart
- Classified AdsClassified Ads
- Content IOContent IO
- ContentTypes EditorContentTypes Editor
- DashboardDashboard
- Data fillerData filler
- Datasources ExplorerDatasources Explorer
- Deploy starterDeploy starter
- ExchangeExchange
- External DataExternal Data
- ExtractionExtraction
- Extra User ManagementExtra User Management
- FAQFAQ
- FlipbookFlipbook
- FormsForms
- Front EditionFront Edition
- Front NotificationFront Notification
- GadgetsGadgets
- GlossaryGlossary
- GLPIGLPI
- Google CalendarGoogle Calendar
- HyperplanningHyperplanning
- InlinemediaInlinemedia
- Job OfferJob Offer
- Link directoryLink directory
- MapsMaps
- MobileAppMobileApp
- MultimediaMultimedia
- MyFavoritesMyFavorites
- NewsNews
- NewsletterNewsletter
- NextcloudNextcloud
- Personal pagesPersonal pages
- Subscription pageSubscription page
- Proxied ContentProxied Content
- Queries DirectoryQueries Directory
- Server DirectoryServer Directory
- Skin editorSkin editor
- Skin factorySkin factory
- SMSSMS
- Social networkingSocial networking
- SurveySurvey
- SyndicationSyndication
- TagcloudTagcloud
- TarteAuCitronTarteAuCitron
- Translation flaggingTranslation flagging
- UGCUGC
- User directoryUser directory
- Web analyticsWeb analytics
- Web Deploy starterWeb Deploy starter
- ZimbraZimbra
New content type
Starting with version 2.6.x, plugin flipbook adds a new content type, "Document PDF". (org.ametys.plugins.flipbook.Content.pdfDocument.
It inherits the same "Document" type from plugin multimedia. (org.ametys.plugins.multimedia.Content.document)
It is linked to a new creation right, "Create a document PDF".
plugin offers a default rendering with a preview of the 1st page of PDF and a link to open PDF in the e-reader PDF.
If you have a similar type of content in your application
You can choose to exclude this new type in your charter (content-types-default files.xml) to avoid duplication and a new graphic integration.
Or you can choose to migrate your existing content type to the new one (data migration required) and take over the existing graphic integration for the new type.
If you don't have a similar type of content in your application
You can choose to exclude this new type in your charter (content-types-default files.xml) if this is not desirable or to avoid a new graphic integration.
Or you can choose to propose this new type. If you don't like the default rendering, you'll need to integrate the graphics.
Back to top