
Recherche avancée
Médias (2)
-
Exemple de boutons d’action pour une collection collaborative
27 février 2013, par
Mis à jour : Mars 2013
Langue : français
Type : Image
-
Exemple de boutons d’action pour une collection personnelle
27 février 2013, par
Mis à jour : Février 2013
Langue : English
Type : Image
Autres articles (25)
-
Submit bugs and patches
13 avril 2011Unfortunately a software is never perfect.
If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
You may also (...) -
Gestion des droits de création et d’édition des objets
8 février 2011, parPar défaut, beaucoup de fonctionnalités sont limitées aux administrateurs mais restent configurables indépendamment pour modifier leur statut minimal d’utilisation notamment : la rédaction de contenus sur le site modifiables dans la gestion des templates de formulaires ; l’ajout de notes aux articles ; l’ajout de légendes et d’annotations sur les images ;
-
Encoding and processing into web-friendly formats
13 avril 2011, parMediaSPIP automatically converts uploaded files to internet-compatible formats.
Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
All uploaded files are stored online in their original format, so you can (...)
Sur d’autres sites (5848)
-
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> -
Documentation #3027 : Squelette Spip.net
18 novembre 2013, par Arnaud Dupin de BeyssatBonjour
Merci de la réponse.
Il s’agit notammen t du menu latéral de la page
http://www.spip.net/fr_rubrique135.html et des suivantes (filrtres,
critères ; etc.)
sans doute associéà<a class="external" href="http://www.spip.net/">www.spip.net</a><br /> /squelettes<br /> /branches<br /> /2008<br /> /inc-rubriques.html
Merci
ADBLe 16/07/2013 10:35, redmine@spip.org a écrit :
La demande #3027 a été mise à jour par b b.
Salut, de quelle page du site s’agit-il ?
Evolution #3027 : Squelette Spip.net
- Auteur : Arnaud Dupin de Beyssat
- Statut : Nouveau
- Priorité : Normal
- Assigné à :
- Catégorie :
- Version cible :
- Resolution :
Bonjour
Serait-il possible de passer la liste des rubriques du menu latéral
ordonné en alphabétique ? Cela faciliterait les recherches de balises, etc.
Actuellement, les lignes sont :
12
13 id_rubriqueid_rubrique=#ENVid_rubrique par num titre !par date
doublons>
14 #TITRE
15A la ligne 13, passer en par nom ai lieu de par num titre !par date
Merci
Vous recevez ce mail car vous êtes impliqués sur ce projet.
Pour changer les préférences d’envoi de mail, allez sur
http://core.spip.org/my/account -
GDPR compliance for Matomo’s Premium Features like Heatmaps & Session Recording, Form Analytics, Media Analytics & co
27 avril 2018, par InnoCraftThe General Data Protection Regulation (EU) 2016/679, also referred to as RGPD in French, Datenschutz-Grundverordnung, DS-GVO in German, is fast-approaching. It is now less than 30 days until GDPR applies to most businesses around the world on 25th May 2018. If you haven’t heard of this new regulation yet, I recommend you check out our GDPR guide which we continue to expand regularly to get you up to speed with it.
GDPR compliance in Matomo
We are currently adding several new features to Matomo to get you GDPR ready. You will have for example the possibility to delete and export data for data subjects, delete and anonymize previously tracked data, anonymize the IP address and location, ask for consent, and more. A beta version with these features is already available. We will release more blog posts and user guides about these features soon and just recently published a post on how to avoid collecting personal information in the first place soon.
If you are still using Piwik, we highly recommend you update to a recent version of Matomo as all versions of Piwik will NOT be GDPR compliant.
GDPR compliance for premium features
InnoCraft, the company of the makers of Matomo, are offering various premium features for your self-hosted Matomo so you can be sure to make the right decisions and continuously grow your business. These features are also available on the cloud-hosted version of Matomo.
If you are now wondering how GDPR applies to these features, you will be happy to hear that none of them collect any personal information except for possibly Heatmaps & Session Recording and the WooCommerce integration. All of them also support all the new upcoming GDPR features like the possibility to export and delete data. It is important that you update your Matomo Premium Features to the latest version to use these features.
Making Heatmaps & Session Recording GDPR compliant
We have added several new features to make it easy for you to be GDPR compliant and in many cases you might not even have to do anything. Some of the changes include :
- Keystrokes (text entered into form fields) are no longer captured by default.
- You may enable the capturing of keystrokes, and all keystrokes will be anonymized by default.
- You may whitelist certain form fields to be recorded in plain text. However, fields that likely contain personal or sensitive information like passwords, phone numbers, addresses, credit card details, names, email addresses, and more will be always anonymized to protect user privacy. (this has always been the case but we have now included many more fields).
How personal information may still be recorded
Nevertheless, Heatmaps and Session Recordings may still record personal or sensitive information if you show them as part of the regular website as plain text (and not as part of a form field). The below example shows an email address for a paypal account as well as a name and VAT information as a regular content.
To anonymize such information, simply add a
data-matomo-mask
attribute to your website :<span data-matomo-mask>example@example.com</span>
You can read more about this in the developer guide “Masking content on your website”.
WooCommerce Integration
The WooCommerce integration may record an Order ID when a customer purchases something on your shop. As the Order ID is an identifier which could be linked with your shop to identify an individual, it may be considered as personal information. Matomo now offers an option to automatically anonymize this Order ID so it is no longer considered as personal information. To enable this feature, log in to your Matomo and go to “Administration => Anonymize Data”.
GDPR compliance for third party plugins on the Matomo Marketplace
The Matomo Marketplace currently features over 80 free plugins. Over 50 of them are compatible with the latest Matomo 3.X version and most of them should support Matomo’s new GDPR features out of the box. If you are concerned by GDPR and are not sure if a third party plugin stores any personal information, we highly recommend you ask the developer of this plugin about the compliance.
You can find a link to the plugin’s issue tracker by going to a plugin page and then clicking on “Github” on the bottom right.
If you are a plugin developer, please read our developer guide “GDPR & How do I make my Matomo plugin compliant”.
The post GDPR compliance for Matomo’s Premium Features like Heatmaps & Session Recording, Form Analytics, Media Analytics & co appeared first on Analytics Platform - Matomo.