Recherche avancée

Sur d’autres sites (5327)

• To all Matomo plugin developers : Matomo 5 is coming, make your plugin compatible now

  5 mai 2023, par Matomo Core Team — Development

  We’re planning to release the first beta of Matomo 5 in a few weeks. For making it easy for Matomo users to be able to upgrade to this beta, it would be great to have as many plugins on the Marketplace as possible already updated and compatible with Matomo 5. Then many users would be able to upgrade to the first beta without any issues.

  Presumably, as you put your plugin on our Marketplace, you want people to use it. Making your plugin compatible with Matomo 5 helps ensure that people will be able to find and keep using your plugin. If your plugin is not compatible with Matomo 5, your plugin will be automatically deactivated in Matomo 5 instances. We’ll be happy to help you achieve compatibility should there be any issue.

  How do I upgrade my Matomo instance to Matomo 5 ?

  If you have installed your Matomo development environment through git, you can simply checkout the Matomo 5 branch “5.x-dev” and install its dependencies by executing these commands :

  • git checkout 5.x-dev
  • composer install

  Alternatively, you can also download the latest version directly from GitHub as a zip file and run composer install afterwards.

  How do I upgrade my plugin to Matomo 5 ?

  • We recommend you create a new branch for your plugin that supports Matomo 5. For example a branch named “5.x-dev“. This way you will be able to make changes to your plugin for Matomo 4 and Matomo 5 and release separate versions.
  • Check out our migration guide from Matomo 4 to Matomo 5 and make sure to review the list of all breaking changes.
  • Release a new version of your plugin in GitHub as usual.

  While there are some breaking changes in Matomo 5, most of our Platform APIs remain unchanged, and almost all changes are for rarely used APIs. Quite often, making your plugin compatible with Matomo 5 will just be a matter of adjusting the “plugin.json” file (as mentioned in the migration guide).

  You can find all developer documentation on our developer zone which has already been updated for Matomo 5.

  How do I know my plugin changes were released successfully ?

  If you have configured an email address within your “plugin.json” file, then you will receive a confirmation or an error email within a few minutes. Alternatively, you can also check out your plugin page on the Marketplace directly. If the plugin release was successful, you will see additional links below the download button showing which versions your plugin is compatible with.

  

  How can switch between Matomo 4 and Matomo 5 or downgrade to Matomo 4 ?

  To downgrade from Matomo 5 to Matomo 4 in your Matomo development environment :

  • check out the “4.x-dev” branch 
  • run “composer install” as usual

  When will the final Matomo 5 release be available ?

  We estimate the final stable Matomo 5.0.0 release will be released in approx. 2-3 months.

  What is new in Matomo 5 ?

  We don’t have a summary of the changes available just yet but you can see all closed issues within this release here.

  Any questions or need help ?

  If you have any questions, or experience any problems during the migration, don’t hesitate to get in touch with us. We’ll be happy to help get your plugin compatible and the update published. If you find any undocumented breaking change or find any step during the migration process not clear, please let us know as well.

  Thank you for contributing a plugin to the Marketplace and making Matomo better. We really appreciate your work !

• avcodec/mpegvideo : Deprecate mpeg_quant option for codecs != MPEG-4

  6 avril 2021, par Andreas Rheinhardt

  avcodec/mpegvideo : Deprecate mpeg_quant option for codecs != MPEG-4
  mpeg_quant may only be set for MPEG-4 and MPEG-2, yet for the latter
  
  it is no option as the code acts as if it were always set.
  
  So deprecate the option for all codecs for which it makes no sense.
  Furthermore, given that the code already errors out if the option is set
  
  for a codec that doesn't support it we can restrict the range of
  
  the option for all these codecs without breaking something. This means
  
  that the checks for whether mpeg_quant is set for these codecs can be
  
  removed as soon as AVCodecContext.mpeg_quant is removed.
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
  

  • [DH] libavcodec/mjpegenc.c
  • [DH] libavcodec/mpeg12enc.c
  • [DH] libavcodec/mpeg4videoenc.c
  • [DH] libavcodec/mpegvideo.h
  • [DH] libavcodec/mpegvideo_enc.c
  • [DH] libavcodec/version.h

• Try out the latest Piwik 3.0.0 beta version : Piwik 3.0.0 is almost here !

  15 novembre 2016, par Matthieu Aubry — Uncategorized

  Dear Piwik community,

  We are excited today to announce our publicly available Piwik 3.0.0 beta 3 release. We have been been working hard behind the scenes on the new 3.0.0 release for almost one year now. We, the passionate team at Piwik, are dedicated to bringing you a new and improved Piwik experience and invite you to join our beta channel to switch to Piwik 3 today !

  Enable the beta release channel

  Ready to enjoy a much faster Piwik experience and the magic of a modern user interface ? Follow the instructions here and you can upgrade to Piwik 3.0.0 beta in just one click.

  Please note that beta versions have a risk of containing bugs so we don’t recommend to use on a production server. If you find and report a bug in a beta version, we will aim to fix it as quickly as possible.

  Premium plugins in Piwik 3

  In the Piwik Marketplace you can discover & download plugins to enrich the functionality of your Piwik, as well as themes to change the look and feel of your Piwik user interface. The Marketplace integration was much improved in this new release, most notably : you can now purchase and download Premium plugins within Piwik !

  Important changes

  The Piwik 3 upgrade comes with some important changes that may require your attention which we detail in this blog post and in the developer changelog.

  The full list of more than 150 changes can be found in the Piwik 3 beta changelogs : beta 1, beta 2, beta 3.

  What to do next

  When you use the Piwik beta channel and if you come across any issues in Piwik such as a bug, feature missing, regression… let us know on our tracker and create a new issue so we can get this sorted.

  As we are in the final days of Piwik 3 development, we are looking forward to your feedback and help testing !

  Welcome to the future of Piwik,

  Happy Analytics !