Sur d’autres sites (7085)

• Anomalie #4401 (Nouveau) : Erreur bloquante avec sql_showtable() en sqlite

  20 novembre 2019, par tcharlss (*´_ゝ｀)

  Glop,

  (Constaté sur un SPIP 3.2.4)

  La fonction spip_sqlite_showtable() renvoie un tableau incorrect pour `field` dans certains cas (cf. les clés `6` et `4` ci-dessous) :
  

  var_dump(sql_showtable(’spip_billets_types’)) ;
  array (size=2)
  
    ’field’ => 
  
      array (size=18)
  
        ’id_billets_type’ => string ’INTEGER NOT NULL’ (length=16)
  
        ’id_billetterie’ => string ’bigint ( 21 ) NOT NULL DEFAULT 0’ (length=32)
  
        ’titre’ => string ’text NOT NULL DEFAULT "" COLLATE NOCASE’ (length=39)
  
        ’descriptif’ => string ’text NOT NULL DEFAULT "" COLLATE NOCASE’ (length=39)
  
        ’quota’ => string ’int ( 11 ) NOT NULL DEFAULT 0’ (length=29)
  
        ’prix’ => string ’decimal ( 20 ’ (length=13)
  
        6 => string ’) NOT NULL DEFAULT 0’ (length=20)
  
        ’taxe’ => string ’decimal ( 4 ’ (length=12)
  
        4 => string ’) NOT NULL DEFAULT 0’ (length=20)
  
        ’selection_min’ => string ’int ( 11 ) NOT NULL DEFAULT 0’ (length=29)
  
        ’selection_max’ => string ’int ( 11 ) NOT NULL DEFAULT 0’ (length=29)
  
        ’date_fin’ => string ’datetime NOT NULL DEFAULT "0000-00-00 00:00:00"’ (length=47)
  
        ’date_debut’ => string ’datetime NOT NULL DEFAULT "0000-00-00 00:00:00"’ (length=47)
  
        ’maj’ => string ’TIMESTAMP’ (length=9)
  
        ’composition’ => string ’varchar ( 255 ) NOT NULL DEFAULT ’’ COLLATE NOCASE’ (length=50)
  
        ’composition_lock’ => string ’tinyint ( 1 ) NOT NULL DEFAULT 0’ (length=32)
  
        ’rang’ => string ’int NOT NULL DEFAULT 0’ (length=22)
  
        ’id_profil’ => string ’bigint(21) NOT NULL DEFAULT 0’ (length=29)
  
    ’key’ => 
  
      array (size=2)
  
        ’PRIMARY KEY’ => string ’id_billets_type’ (length=15)
  
        ’KEY id_billetterie’ => string ’CREATE INDEX `spip_billets_types_id_billetterie` ON `spip_billets_types` (
  
      `id_billetterie`
  
  )’ (length=94)
  

  Et voici ce qu’on devrait avoir, selon la vraie déclaration des champs :
  

  ’field’=> array(
      ’id_billets_type’    => ’bigint(21) NOT NULL’,
      ’id_billetterie’     => ’bigint(21) NOT NULL DEFAULT 0’,
      ’rang’               => ’int NOT NULL DEFAULT 0’,
      ’titre’              => ’text NOT NULL DEFAULT ""’,
      ’descriptif’         => ’text NOT NULL DEFAULT ""’,
      ’quota’              => ’int(11) NOT NULL DEFAULT 0’,
      ’prix’               => ’decimal(20,6) NOT NULL DEFAULT 0’,
      ’taxe’               => ’decimal(4,4) NOT NULL DEFAULT 0’,
      ’selection_min’      => ’int(11) NOT NULL DEFAULT 0’,
      ’selection_max’      => ’int(11) NOT NULL DEFAULT 0’,
      ’date_fin’           => ’datetime NOT NULL DEFAULT "0000-00-00 00:00:00"’,
      ’date_debut’         => ’datetime NOT NULL DEFAULT "0000-00-00 00:00:00"’,
      ’maj’                => ’TIMESTAMP’
  ),
  

  Donc ça se plante sur les champs prix_ht et taxe qui sont tous les 2 identiques : decimal(20,6) NOT NULL DEFAULT 0.
  On dirait qu’il y a un souci soit quand il y a une parenthèse, soit quand il y a une virgule dans la déclaration d’une colonne.

  Du coup sur une table en Sqlite, la requête suivante ne passe pas :
  

  sql_alter(’TABLE spip_billets_types CHANGE prix prix_ht decimal(20,6) NOT NULL DEFAULT 0’)
  

  
  Car au moment de créer la table temporaire, la requête est erronée :
  

  2019-11-20 11:49:50 127.0.0.1 (pid 12659) :Pub:ERREUR : near "6" : syntax error - CREATE TABLE IF NOT EXISTS spip_billets_types_tmp (
          id_billets_type INTEGER NOT NULL,
          id_billetterie bigint ( 21 ) NOT NULL DEFAULT 0,
          titre text NOT NULL DEFAULT "" COLLATE NOCASE,
          descriptif text NOT NULL DEFAULT "" COLLATE NOCASE,
          quota int ( 11 ) NOT NULL DEFAULT 0,
          prix_ht decimal(20,6) NOT NULL DEFAULT 0,
          6 ) NOT NULL DEFAULT 0,
          taxe decimal ( 4 ,
          4 ) NOT NULL DEFAULT 0,
          selection_min int ( 11 ) NOT NULL DEFAULT 0,
          selection_max int ( 11 ) NOT NULL DEFAULT 0,
          date_fin datetime NOT NULL DEFAULT "0000-00-00 00:00:00",
          date_debut datetime NOT NULL DEFAULT "0000-00-00 00:00:00",
          maj TIMESTAMP,
          composition varchar ( 255 ) NOT NULL DEFAULT ’’ COLLATE NOCASE,
          composition_lock tinyint ( 1 ) NOT NULL DEFAULT 0,
          rang int NOT NULL DEFAULT 0,
          id_profil bigint(21) NOT NULL DEFAULT 0,
          PRIMARY KEY (id_billets_type))
  

  Allez, une petite une aspirine et je regarde la Regex qui décrypte la déclaration SQL : /^[^(),]*\(((?:[^()]*\((?:[^()]*\([^()]*\))?[^()]*\)[^()]*)*[^()]*)\)[^()]*$/

• I want to change the file name with exiftool. To “Result of adding time zone (+9) to CreateDate”

  7 décembre 2019, par user3474300

  I shot a video with a sony camera.
  A file with the extension .mp4 was created.
  I want to change the shooting date and time to a file name.
  The environment is Windows10.

  ---

  What I tried

  I first dragged and dropped the .mp4 video file to exiftool (-k) .exe.

  ExifTool Version Number         : 11.76
  
  File Name                       : C0001.MP4
  
  File Modification Date/Time     : 2019:10:23 13:10:49+09:00
  
  File Access Date/Time           : 2019:11:17 21:50:24+09:00
  
  File Creation Date/Time         : 2019:11:17 21:50:21+09:00
  
  MIME Type                       : video/mp4
  
  Major Brand                     : Sony XAVC
  
  Create Date                     : 2019:10:23 04:10:32
  
  Modify Date                     : 2019:10:23 04:10:32
  
  Track Create Date               : 2019:10:23 04:10:32
  
  Track Modify Date               : 2019:10:23 04:10:32
  
  Media Create Date               : 2019:10:23 04:10:32
  
  Media Modify Date               : 2019:10:23 04:10:32
  
  Time Zone                       : +09:00
  
  Last Update                     : 2019:10:23 13:10:32+09:00
  
  Creation Date Value             : 2019:10:23 13:10:32+09:00

  I then typed the following command at a Windows 10 command prompt :

  C:\hoge>"exiftool(-k).exe" -r "-FileNamehoge/C0001.MP4
  
  Warning: Error removing old file - C:/hoge/C0001.MP4
  
      1 directories scanned
  
      1 image files updated
  
  -- press RETURN --

  The following file was created.

  2019-10-23_04-10-32 - C0001.MP4

  ---

  How can I output the following file ?

  I don’t know how to add time zone (+9) to CreateDate.

  2019_1023_131032.MP4

• Berlin website owners need consent for using Google Analytics

  19 novembre 2019, par Joselyn Khor — Uncategorized

  Website owners in Berlin need consent for using Google Analytics

  According to the Berlin Data Protection Office, if you’re a website owner collecting and sending data to third-party services (like Google Analytics) who are also using that data “for own purpose uses” in Berlin, you are now required to ask for specific consent from visitors in order to collect that information. 

  This means you can only use Google Analytics or similar services once you’ve gotten consent from visitors. In contrast, Matomo does not use information from Cloud or On-Premise users for “own purpose uses”.

  Consent is also needed when keystrokes or mouse movements are recorded. That means you need users to consent to your usage of features like Heatmaps and Session Recordings.

  It’s advised that website owners in Berlin should check their websites for third-party content and tracking mechanisms. If you do use these third-party functions that require consent, you must either get consent or remove the functions. Consent is only effective if the visitor (whose data you’re collecting) is informed and agrees to their data being processed.

  Currently this applies to website owners in Berlin, and should likely be applied for the whole of Germany to be on the safe side.

  Further reading :

  • Learn more about Matomo’s Cloud Data Processing Agreement
  • Read about asking for consent in Matomo
  • To use Matomo Analytics and be compliant with the regulation we recommend you learn how to make Matomo GDPR compliant in 12 steps.

  And learn more about all the features in our GDPR user guide and privacy user guide. You can also learn more about GDPR through our blog posts.