Recherche avancée

Médias (0)

Mot : - Tags -/gis

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (103)

  • Diogene : création de masques spécifiques de formulaires d’édition de contenus

    26 octobre 2010, par

    Diogene est un des plugins ? SPIP activé par défaut (extension) lors de l’initialisation de MediaSPIP.
    A quoi sert ce plugin
    Création de masques de formulaires
    Le plugin Diogène permet de créer des masques de formulaires spécifiques par secteur sur les trois objets spécifiques SPIP que sont : les articles ; les rubriques ; les sites
    Il permet ainsi de définir en fonction d’un secteur particulier, un masque de formulaire par objet, ajoutant ou enlevant ainsi des champs afin de rendre le formulaire (...)

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

Sur d’autres sites (10979)

  • 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.

  • avpacket : Replace av_free_packet with av_packet_unref

    23 octobre 2015, par Luca Barbato
    avpacket : Replace av_free_packet with av_packet_unref
    

    `av_packet_unref` matches the AVFrame ref-counted API and can be used as
    a drop in replacement.

    Deprecate `av_free_packet`.

    • [DBH] avconv.c
    • [DBH] avplay.c
    • [DBH] doc/APIchanges
    • [DBH] doc/examples/avcodec.c
    • [DBH] doc/examples/transcode_aac.c
    • [DBH] libavcodec/avcodec.h
    • [DBH] libavcodec/avpacket.c
    • [DBH] libavcodec/jpeglsenc.c
    • [DBH] libavcodec/libxvid.c
    • [DBH] libavcodec/mpegvideo_enc.c
    • [DBH] libavcodec/utils.c
    • [DBH] libavcodec/version.h
    • [DBH] libavdevice/alsa_dec.c
    • [DBH] libavdevice/jack.c
    • [DBH] libavdevice/oss_dec.c
    • [DBH] libavdevice/pulse.c
    • [DBH] libavdevice/sndio_dec.c
    • [DBH] libavdevice/v4l2.c
    • [DBH] libavdevice/vfwcap.c
    • [DBH] libavfilter/vsrc_movie.c
    • [DBH] libavformat/4xm.c
    • [DBH] libavformat/adxdec.c
    • [DBH] libavformat/amr.c
    • [DBH] libavformat/asfdec.c
    • [DBH] libavformat/avformat.h
    • [DBH] libavformat/avidec.c
    • [DBH] libavformat/avs.c
    • [DBH] libavformat/c93.c
    • [DBH] libavformat/cdg.c
    • [DBH] libavformat/cdxl.c
    • [DBH] libavformat/dfa.c
    • [DBH] libavformat/dsicin.c
    • [DBH] libavformat/dss.c
    • [DBH] libavformat/dxa.c
    • [DBH] libavformat/electronicarts.c
    • [DBH] libavformat/flic.c
    • [DBH] libavformat/g723_1.c
    • [DBH] libavformat/gsmdec.c
    • [DBH] libavformat/hls.c
    • [DBH] libavformat/hnm.c
    • [DBH] libavformat/idcin.c
    • [DBH] libavformat/ilbc.c
    • [DBH] libavformat/img2dec.c
    • [DBH] libavformat/ingenientdec.c
    • [DBH] libavformat/internal.h
    • [DBH] libavformat/ipmovie.c
    • [DBH] libavformat/iv8.c
    • [DBH] libavformat/lxfdec.c
    • [DBH] libavformat/matroskadec.c
    • [DBH] libavformat/matroskaenc.c
    • [DBH] libavformat/mmf.c
    • [DBH] libavformat/mp3enc.c
    • [DBH] libavformat/mpc.c
    • [DBH] libavformat/mpegts.c
    • [DBH] libavformat/mux.c
    • [DBH] libavformat/mxfenc.c
    • [DBH] libavformat/ncdec.c
    • [DBH] libavformat/nsvdec.c
    • [DBH] libavformat/nuv.c
    • [DBH] libavformat/psxstr.c
    • [DBH] libavformat/rawdec.c
    • [DBH] libavformat/rl2.c
    • [DBH] libavformat/rmdec.c
    • [DBH] libavformat/rpl.c
    • [DBH] libavformat/rtpdec_asf.c
    • [DBH] libavformat/rtpdec_mpa_robust.c
    • [DBH] libavformat/rtpdec_qt.c
    • [DBH] libavformat/rtpdec_xiph.c
    • [DBH] libavformat/sapdec.c
    • [DBH] libavformat/seek-test.c
    • [DBH] libavformat/sierravmd.c
    • [DBH] libavformat/spdifdec.c
    • [DBH] libavformat/thp.c
    • [DBH] libavformat/utils.c
    • [DBH] libavformat/vqf.c
    • [DBH] libavformat/wc3movie.c
    • [DBH] libavformat/westwood_vqa.c
    • [DBH] libavformat/wvdec.c
    • [DBH] libavformat/yop.c
    • [DBH] tools/pktdumper.c
  • lavc : Make AVPacket.duration int64, and deprecate convergence_duration

    26 septembre 2015, par wm4
    lavc : Make AVPacket.duration int64, and deprecate convergence_duration
    

    Note that convergence_duration had another meaning, one which was in
    practice never used. The only real use for it was a 64 bit replacement
    for the duration field. It’s better just to make duration 64 bits, and
    to get rid of it.

    Signed-off-by : Vittorio Giovara <vittorio.giovara@gmail.com>

    • [DBH] doc/APIchanges
    • [DBH] libavcodec/audio_frame_queue.c
    • [DBH] libavcodec/audio_frame_queue.h
    • [DBH] libavcodec/avcodec.h
    • [DBH] libavcodec/avpacket.c
    • [DBH] libavcodec/parser.c
    • [DBH] libavcodec/version.h
    • [DBH] libavformat/framecrcenc.c
    • [DBH] libavformat/matroskadec.c
    • [DBH] libavformat/matroskaenc.c
    • [DBH] libavformat/md5enc.c
    • [DBH] libavformat/mov.c
    • [DBH] libavformat/r3d.c
    • [DBH] libavformat/utils.c