Advanced search

On other websites (12572)

• Piwik 3 Development Update #4 – Important notes and breaking changes

  2 October 2016, by Piwik Core Team — Community, Development

  As mentioned in the previous development updates #1 New UI design, API changes & release date, #2 Git master branch will become Piwik 3 and #3 Marketplace we are actively working on the Piwik 3 update and we will release a first beta of it soon. While the update brings many new features and bugfixes, it also comes with some important changes that may require your attention which we detail in this blog post.

  Database updates

  To keep Piwik upgrades as easy as possible, we have usually avoided database schema changes that affect large tables during the Piwik 2.X release cycle. The Piwik 3 update will however require several database updates in order to fix some limitations and bugs in the Piwik database schema. If you have a fair amount of traffic and/or large Piwik database, we recommend to execute the database updates for Piwik 3 on the command line.

  If you struggle updating Piwik you can also get in touch with the Piwik Support and ask for a quote so we can help you with upgrading.

  New server & browser Requirements

  Piwik 3 updates the server requirements. Piwik 3 now requires:

  • PHP 5.5.9 or newer (we used to require PHP 5.3+),
  • MySQL 5.5 or newer or MariaDB (we used to require MySQL 4.1+).

  If you are still on an old PHP and MySQL version we highly recommend to update directly to PHP 7 and a recent MySQL version (MySQL 5.7+).

  Piwik 3 also drops support for the older browsers IE8 and IE9.

  Default filter_limit now applies to all HTTP API methods (#8458)

  In the past the default filter_limit of 100 rows was applied to HTTP API methods that return a report. This means that by default:

  • when you requested a method like SitesManager.getAllSites, UsersManager.getUsers or Goals.getGoals (which are not reports), we returned all rows.
  • when you fetched a report like Actions.getPageUrls (which is a report), the result was limited to 100 rows.

  This behaviour was inconsistent and it was hard to understand which methods apply the default limit and which did not. We now apply the default limit to all HTTP API methods by default.

  If your API consumer or app needs to fetch all results for an API method, you can append the following parameter to the URL: &filter_limit=-1. Alternatively, if you wish to change the default filter_limit automatically for all APIs, you can override the API_datatable_default_limit config setting in your config/config.ini.php file.

  For more information about the various APIs parameters you can use, see Piwik Analytics HTTP API Reference.

  Proxy client IP detection (#10342)

  This is only important if you are using the proxy_client_headers[] config in the config/config.ini.php file, ie. your Piwik server is behind a proxy.

  When Piwik is set up to fetch the client IP address from the proxy headers, and the header contained more than one IP address, we used to use the last IP address. From Piwik 3 we will be using the first IP address which is in line with the protocol definition. For example if HTTP_X_FORWARDED_FOR contains multiple IP addresses, we now use the first IP instead of the last one.

  Writable Piwik JavaScript Tracker file piwik.js

  From Piwik 3 we recommend to have the file /piwik.js writable in your Piwik directory, so that the PHP and webserver processes can edit this file. It is not required to have the file writable for Piwik to function well, but we are working on some enhanced features that will only work when the file is writable. If you don’t know whether this file is writable, go to “Administration => System Check” as a Super User and Piwik will display a warning if the file is not writable. If needed, you might be able to make the file writable by executing a command like chmod 0755 piwik.js or chown $webuser piwik.js (on Linux).

  Changes for plugin developers

  In the previous development updates we have already introduced some of the changes that affect Piwik plugin developers. We have made several improvements to the Marketplace that allow developers to promote their plugin better and to maintain their plugin page easier. We have also created a migration guide for plugin developers to make it easier to migrate a plugin to Piwik 3.

  For a list of all changes have a look at the developer changelog.

  Until our next Piwik 3 update, be well, and Happy Analytics!

• Exception in thread "main" java.lang.NoClassDefFoundError: Could not initialize class org.bytedeco.javacpp.avutil"

  12 December 2016, by Ajinkya

  public static class AVFormatContext extends Pointer {
  
      static { Loader.load(); }
  
      /** Default native constructor. */
  
      public AVFormatContext() { super((Pointer)null); allocate(); }
  
      /** Native array allocator. Access with {@link Pointer#position(long)}. */
  
      public AVFormatContext(long size) { super((Pointer)null); allocateArray(size); }
  
      /** Pointer cast constructor. Invokes {@link Pointer#Pointer(Pointer)}. */
  
      public AVFormatContext(Pointer p) { super(p); }
  
      private native void allocate();
  
      private native void allocateArray(long size);
  
      @Override public AVFormatContext position(long position) {
  
          return (AVFormatContext)super.position(position);
  
  }

  I’ve tried to run a java application with an FFMmpegFrameGrabber while trying to run on windows. However same jar file runs on linux with no exceptions.

  I have included javacpp and javacv jars .

  However while running on windows I am getting this error
  main" java.lang.NoClassDefFoundError: Could not initialize class org.bytedeco.javacpp.avutil"

  Stacktrace of exception

  Exception in thread "main" java.lang.NoClassDefFoundError: Could not initialize
  
  class org.bytedeco.javacpp.avutil
  
          at java.lang.Class.forName0(Native Method)
  
          at java.lang.Class.forName(Unknown Source)
  
          at org.bytedeco.javacpp.Loader.load(Loader.java:413)
  
          at org.bytedeco.javacpp.Loader.load(Loader.java:381)
  
          at org.bytedeco.javacpp.avformat$AVFormatContext.<clinit>(avformat.java:
  
  2719)
  
          at org.bytedeco.javacv.FFmpegFrameGrabber.startUnsafe(FFmpegFrameGrabber
  
  .java:391)
  
          at org.bytedeco.javacv.FFmpegFrameGrabber.start(FFmpegFrameGrabber.java:
  
  385)
  
          at testffmpeg.NewStreamer.StartandRestart(NewStreamer.java:191)
  
          at testffmpeg.NewStreamer.<init>(NewStreamer.java:95)
  
          at testffmpeg.NewStreamer.main(NewStreamer.java:91)
  
  </init></clinit>

• Préférence donnée à mp4 sur webm quand le fichier mp4 est chargé en tant que conversion d’un fichier webm

  21 January 2016

  Bonjour,
  le site AlterInfos - América latina (www.alterinfos.org) utilise depuis un an le plugin "Lecteur multimédia HTML5 pour MediaSPIP" qui marche super bien. Merci.
  Jusqu’à présent, les vidéos étaient surtout au format mp4. Mais dans un article récent, les vidéos ont été téléversés au format webm (VP9+Opus), puis, à partir de ces vidéos de référence, une conversion en mp4 a aussi été téléversée. Quand on visualise les vidéos dans Firefox (43, Debian Jessie 64) ou dans Chromium, c’est toujours le fichier mp4 qui est visualisé. Si on met la vidéo au format webm seulement, la vidéo est visualisée dans ce format.
  Ce n’est donc pas un problème de compatibilité du navigateur, mais plutôt peut-être que le fichier "conversion" (mp4) est traité avant le fichier "original" (webm). Si on regarde le code source de la page, le lien vers le mp4 apparaît avant celui en webm.
  Téléverser d’abord le fichier en mp4 puis charger ensuite en tant que "conversion du document" le fichier en webm règle le problème : c’est désormais le fichier en webm qui est joué "par défaut" quand on visualise la vidéo.
  Mais il me semble que ce serait plus logique que ce soit le document de référence et non sa conversion qui soit joué par défaut quand on visualise une vidéo.
  Ça permettrait aussi de choisir la vidéo qu’on souhaite diffuser "par défaut" (dans notre cas, la vidéo webm est beaucoup plus légère [car VP9 et opus], donc c’est assez logique de vouloir que ce soit la vidéo par défaut…
  Cordialement,
  Nicolas