Recherche avancée

Sur d’autres sites (5491)

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

  2 octobre 2016, par 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 !

• Evolution #3393 : suivi activité éditoriale : ne pas envoyer l’annonce de proposition de son propr...

  21 décembre 2017

  Je ne suis pas sur que cela soit pertinent :
  - on peut avoir un email collectif (un auteur collectif dont l’email est une liste de travail)
  - on peut vouloir avoir une trace par email de son activité web

• Easy Tricks for Finding WebM Videos in YouTube

  9 août 2010, par noreply@blogger.com (John Luther)

  Since the WebM project launch, YouTube has been encoding videos uploaded at 720p or higher resolution in the WebM format. Today, the one million most popular videos of any size on YouTube are also available in the WebM format.

  We have instructions on our project site for finding these videos but they require adding a special parameter onto the end of each search query. All of the browsers that support WebM can create search shortcuts with custom parameters, however, so we’ve compiled instructions for making it very simple to search for WebM videos in YouTube.

  Important : First, make sure you have a supported browser and are enrolled in the YouTube HTML5 beta by going to http://youtube.com/html5 and clicking Enter the HTML5 Beta.

  Creating a WebM Search Shortcut

  Firefox 4 Beta :
  

  1. Select Bookmarks > Organize Bookmarks. A bookmark manager dialog opens.
  2. In the left column, choose a location for the new bookmark you’re creating. Next, choose Organize > New Bookmark (on MacOS click the gear icon). The new bookmark dialog opens.
  3. In the Name box, type WebM.
  4. In the Location box, type http://youtube.com/results?search_query=%s&webm=1.
  5. In the Keyword box, type webm.
  6. Click Add.

  Google Chrome Early Release Channel :
  

  1. On Windows and Linux, click the Chrome wrench icon in the toolbar and select Options. On MacOS, select Chrome > Preferences.
  2. On the Basics tab, click the Manage button in the Default Search section.
  3. On Windows and Linux, click Add. On MacOS X, click the plus (+) button.
  4. In the Name box, type WebM.
  5. In the Keyword box, type webm.
  6. In the URL box, type http://youtube.com/results?search_query=%s&webm=1.
  7. Click OK.

  Opera 10.60 and later :
  

  1. Go to http://youtube.com.
  2. Right-click in the YouTube search box at the top of the page and select Create Search. On MacOS, use Ctrl+click if you don’t a secondary mouse button enabled.
  3. In the Name box, type WebM.
  4. In the Keyword box, type webm.
  5. In the Address box, type http://youtube.com/results?search_query=%s&webm=1.
  6. Click OK.

  
  

  
  Now you’re ready to search. In the location box of the browser, type webm monster trucks. The YouTube search results page will open with a selection of monster truck videos encoded in the WebM format. When watching a video, look for the HTML5 WebM indicator in the player control bar.

  If you can’t find WebM videos it is most likely a browser cookie problem. Your enrollment in the YouTube HTML5 beta test is stored in a browser cookie (not in your YouTube or Google account), and that cookie can expire. Visit http://youtube.com/html5 and opt-in again to re-set the cookie.

  Directly Accessing WebM Videos by URL

  To find out if any YouTube video is available in WebM, simply add &html5=True (make sure True is capitalized) to the end of the video URL. If there is a WebM version of the video, it will open instead of the Flash version. For example :
  

  • Flash version : http://www.youtube.com/watch?v=Dz6gFokvOr0
  • WebM version : http://www.youtube.com/watch?v=Dz6gFokvOr0&html5=True