
Recherche avancée
Autres articles (54)
-
Gestion générale des documents
13 mai 2011, parMédiaSPIP ne modifie jamais le document original mis en ligne.
Pour chaque document mis en ligne il effectue deux opérations successives : la création d’une version supplémentaire qui peut être facilement consultée en ligne tout en laissant l’original téléchargeable dans le cas où le document original ne peut être lu dans un navigateur Internet ; la récupération des métadonnées du document original pour illustrer textuellement le fichier ;
Les tableaux ci-dessous expliquent ce que peut faire MédiaSPIP (...) -
Des sites réalisés avec MediaSPIP
2 mai 2011, parCette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page. -
HTML5 audio and video support
13 avril 2011, parMediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
For older browsers the Flowplayer flash fallback is used.
MediaSPIP allows for media playback on major mobile platforms with the above (...)
Sur d’autres sites (6252)
-
Anomalie #4276 : fonctions non définies dans porte_plume_pipelines.php
24 janvier 2019, par François PalangiéBonjour,
Vous avez raison c’est la version 1.18.3 que j’ai maintenant, 1.18.1
devait être le numéro de version avant que je réinstalle la dernière
version de SPIP.Le problème était le même avec la 18.1.1 et la 18.1.3 . Le problème est
intervenu un matin sans que j’ai rien changé, je suppose que c’est mon
hébergeur qui a changé l’environnement et que c’est la cause du
problème... mais c’est curieux que cela produise ce type d’erreur !Cordialement,
François
Le 24/01/2019 à 12:59, redmine@spip.org a écrit :
La demande #4276 <https://core.spip.net/issues/4276#change-14694> a
été mise à jour par Franck D .- Statut changé de /Nouveau/ à /Fermé/
Hello :-)
Spip 3.2.3 est dispo avec la version 1.18.3 de porte plume
https://zone.spip.net/trac/spip-zone/browser/spip-zone/_core_/tags/spip-3.2.3/plugins/porte_plume/paquet.xml#L4
J’ai vérifier le zip et c’est bien le cas
https://files.spip.net/spip/archives/SPIP-v3.2.3.zip !
Vous êtes sûr de la version que vous avez ?
Franck
Anomalie #4276 : fonctions non définies dans
porte_plume_pipelines.php
<https://core.spip.net/issues/4276#change-14694>- Auteur : François Palangié
- Statut : Fermé
- Priorité : Normal
- Assigné à :
- Catégorie :
- Version cible :
- Resolution :
- Navigateur :
Environnement :
- SPIP 3.2.3 [24211]
- Porte plume 1.18.1 - stable
- Site : https://voyart.org
- PHPinfo : https://voyart.org/phpinfo.php
Problème :
Le site fonctionne, mais quand on tente d’accéder à la partie
privée on a ce message d’erreur, qui persiste même après une
réinstallation de SPIP :
Fatal error : Uncaught Error : Call to undefined function barre_outils_css_icones() in /var/www/vhosts/voyart.org/httpdocs/plugins-dist/porte_plume/porte_plume_pipelines.php:152
Stack trace :
#0 /var/www/vhosts/voyart.org/httpdocs/plugins-dist/porte_plume/porte_plume_pipelines.php(129) : porte_plume_insert_head_css(’<script type="t...', true)<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Anomalie: Document distant .zip uploadés et non gardés distants (Fermé)" href="https://core.spip.net/issues/1">#1</a> /var/www/vhosts/voyart.org/httpdocs/ecrire/inc/utils.php(199): porte_plume_insert_head_prive_css('<script type="t...')<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Anomalie: Filtres sur chaines de langues de nouveau cassés (Fermé)" href="https://core.spip.net/issues/2">#2</a> /var/www/vhosts/voyart.org/httpdocs/tmp/cache/charger_pipelines.php(596): minipipe('porte_plume_ins...', '<script type="t...')<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Anomalie: problème de gestion de cache lors de l'installation de SPIP (Fermé)" href="https://core.spip.net/issues/3">#3</a> /var/www/vhosts/voyart.org/httpdocs/ecrire/inc/utils.php(265): execute_pipeline_header_prive_css('<script type="t...')<br /><a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Evolution: forum privé->public (Fermé)" href="https://core.spip.net/issues/4">#4</a> /var/www/vhosts/voyart.org/httpdocs/tmp/cache/skel/html_c44cf6e196e37af7575f04c7aba04247.php(72): pipeline('header_prive_cs...', '<script type="t...')<br /><a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Evolution: traduction francophone de la zone utilisant Trac (Fermé)" href="https://core.spip.net/issues/5">#5</a> /var/www/vhosts/voyart.org/httpdocs/ecrire/public/parametrer.php(128): html_c44cf6e196e37af7575f04c7aba04247(Array, Array)<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Anomalie: Renseigner les champs "component", "version", .. (Fermé)" href="https://core.spip.net/issues/6">#6</a> /var/www/vhosts/voyart.org/httpdocs/ecr in /var/www/vhosts/voyart.org/httpdocs/plugins-dist/porte_plume/porte_plume_pipelines.php on line 152</p><br />
<br />
<br />
<p>Le problème est contourné en renommant le répertoire <br />plugin-dist/porteplume<br />Le problème ne dépend pas du navigateur firefox, edge, chrome<br />Aucun problème sur le SPIP de développement installé avec <br />EasyPHP-devserver sur mon ordinateur perso</p><br />
<br />
<br />
<hr /><br />
<br />
<br />
<p>Vous recevez ce mail car vous êtes impliqués sur ce projet.<br />Pour changer les préférences d'envoi de mail, allez sur <br /><a class="external" href="http://core.spip.net/my/account">http://core.spip.net/my/account</a></p><br />
<br />
<br />
</blockquote><br />
<br />
<p>---<br />Cet email a fait l'objet d'une analyse antivirus par AVG.<br /><a class="external" href='http://www.avg.com/'>http://www.avg.com</a></p> -
New Challenges
1er janvier 2014, par silviaI finished up at Google last week and am now working at NICTA, an Australian ICT research institute.
My work with Google was exciting and I learned a lot. I like to think that Google also got a lot out of me – I coded and contributed to some YouTube caption features, I worked on Chrome captions and video controls, and above all I worked on video accessibility for HTML at the W3C.
I was one of the key authors of the W3C Media Accessibility Requirements document that we created in the Media Accessibility Task Force of the W3C HTML WG. I then went on to help make video accessibility a reality. We created WebVTT and the <track> element and applied it to captions, subtitles, chapters (navigation), video descriptions, and metadata. To satisfy the need for synchronisation of video with other media resources such as sign language video or audio descriptions, we got the MediaController object and the @mediagroup attribute.
I must say it was a most rewarding time. I learned a lot about being productive at Google, collaborate successfully over the distance, about how the WebKit community works, and about the new way of writing W3C standard (which is more like pseudo-code). As one consequence, I am now a co-editor of the W3C HTML spec and it seems I am also about to become the editor of the WebVTT spec.
At NICTA my new focus of work is WebRTC. There is both a bit of research and a whole bunch of application development involved. I may even get to do some WebKit development, if we identify any issues with the current implementation. I started a week ago and am already amazed by the amount of work going on in the WebRTC space and the amazing number of open source projects playing around with it. Video conferencing is a new challenge and I look forward to it.
-
New Challenges
1er janvier 2014, par silviaI finished up at Google last week and am now working at NICTA, an Australian ICT research institute.
My work with Google was exciting and I learned a lot. I like to think that Google also got a lot out of me – I coded and contributed to some YouTube caption features, I worked on Chrome captions and video controls, and above all I worked on video accessibility for HTML at the W3C.
I was one of the key authors of the W3C Media Accessibility Requirements document that we created in the Media Accessibility Task Force of the W3C HTML WG. I then went on to help make video accessibility a reality. We created WebVTT and the <track> element and applied it to captions, subtitles, chapters (navigation), video descriptions, and metadata. To satisfy the need for synchronisation of video with other media resources such as sign language video or audio descriptions, we got the MediaController object and the @mediagroup attribute.
I must say it was a most rewarding time. I learned a lot about being productive at Google, collaborate successfully over the distance, about how the WebKit community works, and about the new way of writing W3C standard (which is more like pseudo-code). As one consequence, I am now a co-editor of the W3C HTML spec and it seems I am also about to become the editor of the WebVTT spec.
At NICTA my new focus of work is WebRTC. There is both a bit of research and a whole bunch of application development involved. I may even get to do some WebKit development, if we identify any issues with the current implementation. I started a week ago and am already amazed by the amount of work going on in the WebRTC space and the amazing number of open source projects playing around with it. Video conferencing is a new challenge and I look forward to it.