Recherche avancée

Médias (1)

Mot : - Tags -/biographie

Autres articles (51)

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

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Amélioration de la version de base

    13 septembre 2013

    Jolie sélection multiple
    Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
    Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)

Sur d’autres sites (3665)

  • Anomalie #4532 (Nouveau) : Parse error en php 8

    26 juillet 2020, par Franck D

    Hello

    Spip et plugin_dist à jour de ce jour !
    easyphp (windows 10 (1909))
    easyphp
    Apache 2.4.43 x64
    PHP 8.0.0 alpha3 x64
    MySQL 8.0.20 x64

    Avant même de pouvoir faire l’installation, quand je vais sur le site, j’ai :
    Parse error : syntax error, unexpected token "match", expecting "(" in C :\Program Files (x86)\EasyPHP-Devserver-17\eds-www\test13\ecrire\inc\filtres.php on line 3114

    Je pense que le changement vient de :
    https://wiki.php.net/rfc/match_expression_v2

  • New cookie behaviour in browsers may cause regressions

    24 février 2020, par Matomo Core Team — Community, Development

    Last year the Chromium browser team announced they would change their default behaviour for cookies. In particular about a property called samesite. Over the last few months, we have made various changes to our cookie handling to get Matomo ready for this. Depending on your setup and the features you use, some things may not work anymore.

    You can avoid most of the issues by using HTTPS on your Matomo, and ideally also use HTTPS on your website(s).

    If you are not running the latest version of Matomo yet (3.13.3 at the time of writing), then we highly recommend that you upgrade as soon as possible. Previous versions are not compatible with these cookie browser changes.

    Opt out screen

    If you embed the opt out screen on your website running on HTTP, there is a chance the Matomo opt out no longer works. In these cases it may still work over http:

    • when the privacy policy page that embeds the opt out screen (via iframe) also has the Matomo JavaScript tracker embedded,
    • and when both the opt out and the JS tracker point to the same Matomo installation.

    In other cases when HTTP is used, the opt out feature will likely be broken.

    We recommend you test whether the opt out on your site still works by opening your privacy policy page in an incognito browser window. Then test to opt out of tracking, and then reload the page. If the checkbox “You are not opted out. Uncheck this box to opt out.” is still ticked, then your opt out is not working.

    If the opt out is not working anymore, it is most likely due to HTTP being used. In that case you should change the opt out URL to HTTPS. For example change from &lt;iframe src=”<strong>http://</strong>…” to &lt;iframe src=”<strong>https://</strong>...” . If your Matomo doesn’t support HTTPS yet, you will need to contact your webhoster or system administrator to get SSL enabled on your Matomo domain.

    JavaScript tracker

    In most cases, everything related to the JavaScript Tracker will still work as expected.

    But there is an edge case : when you are also reading Matomo’s cookie server side. You may be affected by this edge case issue when :

    • you track part of the user behaviour in the browser (using Matomo JS Tracker),
    • and also track user behavior in your server (for example using one of Matomo SDKs in PHP, Java, Python, C#, etc.).

    In that case, for you to still be able to read the so-called visitorId on your server, we recommend you add this line to your JS tracking code :

    _paq.push([‘setSecureCookie’, location.protocol === 'https:']);

    The cookie can be only retrieved if your website is loaded through HTTPS.

    Should you have any questions, or notice anything isn’t working as expected, please visit our forum.

    Third party cookies

    If you are using third party cookies, using HTTPS on your Matomo is now a requirement to make them work across different domains. Otherwise Chrome and in the near future other browsers would not accept the cookie. If you don’t know if you are using third party cookies or first party cookies, you’re likely using first party cookies and this does not affect you.

  • Android Video color effect issue using FFMPEG [on hold]

    8 juin 2016, par umesh mishra

    I m facing one problem. when we use library for effect that i have mentioned below video is created only 1/3 of actual video size. please tell me what is issue. and also doesn’t work on marshmallow.
    https://github.com/krazykira/VidEffects/wiki/Permanent-video-effects