Sur d’autres sites (6800)

• Piwik 2.1 – Changes for Plugin developers

  24 février 2014, par Piwik Core Team — Development

  This blog post is aimed at developers of Piwik Plugins. If you are simply using Piwik and not developing plugins for Piwik, you do not need to read this post.

  Piwik 2.1 will be released in a few days . This blog post will inform Piwik Plugin developers of the changes in Piwik 2.1 that may require that you update your plugin to work with this latest version.

  Breaking API changes

  Piwik can now handle an unlimited number of users having Super User access (#2589 #4564). In the past Piwik was limited to one Super User who was defined in the config file. From now on all users with Super User access are defined in the database the same way a regular user is. This brought some API changes but we will stay backward compatible until the first of April 2014. This gives you some time to migrate any custom plugins you may use. Although there is a layer for backward compatibility we recommend to make sure your plugin works with Piwik as soon as possible before April 1st.

  List of changes

  Deprecated methods

  The following methods are deprecated and we recommend to use the new methods from now on. There are also some methods which won’t be replaced so make sure to adjust the logic of your plugin.

  \Piwik\Piwik::isUserIsSuperUser => \Piwik\Piwik::hasUserSuperUserAccess
  
  \Piwik\Piwik::setUserIsSuperUser => \Piwik\Piwik::setUserHasSuperUserAccess
  
  \Piwik\Piwik::checkUserIsSuperUser => \Piwik\Piwik::checkUserHasSuperUserAccess
  
  \Piwik\Access::isSuperUser => \Piwik\Access::hasSuperUserAccess
  
  \Piwik\Access::checkUserIsSuperUser => \Piwik\Access::checkUserHasSuperUserAccess
  
  \Piwik\Access::setSuperUser => \Piwik\Access::setSuperUserAccess
  
  \FakeAccess::checkUserIsSuperUser => FakeAccess::checkUserHasSuperUserAccess
  
  \FakeAccess::setSuperUser => FakeAccess::setSuperUserAccess
  
  \Piwik\Piwik::isUserIsSuperUserOrTheUser => \Piwik\Piwik::hasUserSuperUserAccessOrIsTheUser
  
  \Piwik\Piwik::checkUserIsSuperUserOrTheUser => \Piwik\Piwik::checkUserHasSuperUserAccessOrIsTheUser
  
  \FakeAccess::getSuperUserLogin => No replacement
  
  \Piwik\Piwik::getSuperUserLogin => No replacement, returns the userLogin of the first Super User we find in the database 
  
  \Piwik\Piwik::getSuperUserEmail => No replacement, returns an empty string from now on
  
  \Piwik\Access::getSuperUserLogin => No replacement, returns the userLogin of the first Super User we find in the database

  Config Super User

  As mentioned, the Super User was defined in the config and you have accessed the Super User’s data either by using a convenient method like Piwik::getSuperUserLogin or directly via the Config object as follows :

  \Piwik\Config::getInstance->superUser

  As the config user is no longer defined in the config this will no longer work in the future. To stay backward compatible we return the first super user found in the database. This is not necessarily always the same user. So if you have used the super user login in some way in your plugin, make sure you are using the new function such as Piwik::getSuperUserLogin

  Extended Auth Interface

  The last change affects plugins who specify their own Authentication mechanism, for instance when using the custom LoginLDAP plugin. From now on the interface \Piwik\Auth (​https://github.com/piwik/piwik/blob/master/core/Auth.php) requires the methods setTokenAuth and setLogin. There is no backward compatibility layer but we had a look at some plugins defining a custom Authentication adapter to make sure those methods are already defined there as expected.

  For another example of a Login plugin, check out the LoginHttpAuth plugin on the Marketplace.

  After updating the plugin

  After you have made changes in your plugin to keep it compatible with Piwik 2.1, your plugin will no longer work with previous Piwik versions. Therefore you should define the minimum required version in your plugin.json file as follows :

  "require": {
  
   "piwik": ">=2.1" 
  
  }

  Summary

  Piwik 2.1 introduces some changes in the Piwik Core APIs. This blog post explains how to modify any Plugins compatible with Piwik 2.0 to be compatible with Piwik 2.1. Thank you for taking the time to update your plugins !

  Let us know if you have any feedback. Happy hacking !

  PS : if you use the Web Analytics APIs and the Web Tracking APIs, we guarantee that we will support backwards compatibility of our Web APIs.

• How to use c99conv.exe to convert C99 to C89

  21 février 2015, par loppp

  Background

  I got ffmpeg Windows libraries from Zeranoe FFmpeg builds but there’s a problem : When I tried to use the headers, I found some of the macros (e.g. av_ts2str) are written using C99 syntax.

  So now I am working on converting the headers to C89, which is compatible with MSVC (now I am using 2013).

  I downloaded c99conv.exe but when I execute it, I get errors :

  avcodec.h:31:10: fatal error: 'libavutil/samplefmt.h' file not found

  Question

  Am I on the right track that every ffmpeg Windows developer will go ? (I am just thinking is there any Visual Studio sln package, sure, with ffmpeg C89 headers, available so that Windows ffmpeg developers can start immediately from there, without wasting 2–5 days to just setup the environment… Sound greedy but it would great help for the newbies like me.)

  How to use c99conv.exe to convert these headers to C89 ?

• ffmpeg video conversion creates empty file when using php's exec()

  23 juillet 2014, par Rob Avery IV

  When I run ffmpeg with PHP’s exec() function to convert a video to flv, the flv file ends up empty. Here is the code I have that does the conversion :

      // Set our source file
  
      $srcFile = "/path/to/file/".$filename."mp4";
  
      $destFile = "/path/to/file/".$filename;
  
      $ffmpegPath = "ffmpeg";
  
  
  
      // Create our FFMPEG-PHP class
  
      $ffmpegObj = new ffmpeg_movie($srcFile);
  
  
  
      // Save our needed variables
  
      $srcWidth = makeMultipleTwo($ffmpegObj->getFrameWidth());
  
      $srcHeight = makeMultipleTwo($ffmpegObj->getFrameHeight());
  
      $srcFPS = $ffmpegObj->getFrameRate();
  
      $srcAB = intval($ffmpegObj->getAudioBitRate()/1000);
  
      $srcAR = $ffmpegObj->getAudioSampleRate();
  
  
  
      // Call our convert using exec()
  
      $command = $ffmpegPath . " -i " . $srcFile . " -ar " . $srcAR . " -ab " . $srcAB . "k -f flv -s " . $srcWidth . "x" . $srcHeight . " " . $destFile . "> /dev/null 2>/dev/null &";
  
      exec($command);

  Before I execute the code above, I have an mp4 file this is uploaded which is the one mentioned in the variable $srcFile. when uploaded, that file is not empty and I am to use it like a normal video file.

  Afterwards, there will be both filename.mp4 and filename (formated to flv video. yes, I’ve tried giving it an .flv extension and nothing different happens) files. filename ends up empty. To make sure it’s running the right command, I did an var_dump($command) to see the command that was actually running. I got this result :

  ffmpeg -i /path/to/file/filename.mp4 -ar 44100 -ab 70k -f flv -s 640x480 /path/to/file/filename

  I then run exec() function like this

  $output = "";
  
  exec($command, $output);
  
  var_dump($output);

  and like this

  $output = exec($command);
  
  var_dump($output);

  Both times, $output is presented as an empty array. Then, I run the ffmpeg command mentioned above through command line. And it worked. It created the flv file and it wasn’t empty and I was able to use as a regular video file with no problems.

  I also tried adding > /dev/null 2>/dev/null & at the end of the command and it still didn’t work.

  To sum up, so far, when ffmpeg is used to convert videos with php’s exec(), it creates the converted as an empty. Though, if I was to take the same command used with exec() and use it through command line, it works perfectly fine.

  I’m stumped. I’ve been tackling this for days and haven’t really gotten anywhere. Where I going wrong ? Is there a different or better way of doing this ? Am I missing something ?