Recherche avancée

Sur d’autres sites (5204)

• Anomalie #4803 (Nouveau) : Nouvelles URLs possiblement en doublon si pages uniques

  31 mai 2021

  Sur un site avec des URLs arborescentes.

  J’ai une rubrique non publiée intitulée « Abonnements » et qui possède l’url boutique-livres/abonnements (dans la table, url = abonnements).
  Je crée une page unique avec le même titre, elle se voit attribuée l’url abonnements, mais l’url finale est celle de la rubrique : boutique-livres/abonnements (avec #URL_ARTICLE, « voir en ligne », etc.).

  url	type	id_objet	date	id_parent	segments	perma	langue
  abonnements	rubrique	1145	2017-12-19 15:32:01	706	1	0	fr
  abonnements	article	100812	2021-05-31 09:48:17	-1	1	0

  J’hésite à ouvrir un ticket sur le plugin pages uniques, j’imagine que c’est le id_parent = -1 qui brouille les cartes.
  Peut-être que c’est un cas de figure qui devrait être pris en compte dans urls avancées ?

• Seeking with the activeX VLC plugin has a bad response rate

  24 juin 2017, par Vitalis Hommel

  I am using axVLCPlugin.input.time = pos; where pos is the new time to browse through a video clip in small resolution (240p) in a VLC activeX part of my program using a slider, which updates pos.

  On an older laptop this worked flawlessly, with no delay. On my new laptop, this works only with significant delay, meaning that once I enter a new position, it takes about 1 second to show this position of the video on screen in the VLC activeX plugin. Previously it was instant.

  Is this

  1. a VLC issue(2.2.6 umbrella) ?
  2. a Visual Studio issue(VS 2017) ?
  3. a video encoding issue(ffmpeg version N-86482-gbc40674 - ffmpeg -i inputfile.extension output.mp4) ?
  4. a video codec issue ?

  EDIT : fortunately I found that the activex-plugin has an output. This is what it gives me : https://pastebin.com/GEKb22Gg - still unclear what that means

  How to track down the cause and solve it ?

• Performance optimizations you can apply today to load the Piwik JavaScript tracker faster

  20 avril 2017, par InnoCraft — Community, Development

  When you track your website with Piwik or any other analytics solution, you need to embed a JavaScript file in order to track page views, events, clicks, and more. At InnoCraft, it is our daily business to help Piwik users to make the most out of their Piwik. We often see similar problems of websites loading unnecessarily slower because the tracking file is not loaded as fast as it should be. There are many ways you can improve the performance but avoiding the most important mistakes will help you to not lose revenue and conversions because of this today. Below you find a few steps that will boost the loading of your Piwik JavaScript tracking file.

  Cache piwik.js

  The most important step is to make sure to configure your server in a way so the piwik.js JavaScript tracker file will be cached once it has been loaded and not requested again on subsequent page views. Learn more about browser caching.

  Enable GZIP

  We recommend enabling GZIP as it reduces the size the user needs to load when the piwik.js file is requested. For the standard Piwik tracker, this will reduce the size from about 60KB to 20KB.

  Preload DNS

  Often a Piwik is hosted on a different domain and when the browser loads the JavaScript tracker file, it needs to first perform a DNS lookup to find the IP address for this domain. By adding the below snipped for your Piwik domain, it can boost the performance of loading the tracker file by 10ms to 50ms.

  <link rel="dns-prefetch" href="//example.innocraft.cloud">

  Preload resource

  To boost the loading of the Piwik tracking file, you can add the following HTML into the header of your website :

  <link rel="preload" href="https://yourpiwikdomain.com/piwik.js" onload="embedTracker()" type="script" crossorigin>

  In Chrome, Opera, and soon in more browsers this will load the JavaScript tracker file without blocking the “onload” event. As a result, as soon as you embed the tracking code, the JavaScript tracker might be already loaded. How “preloading” affects your website always depends and maybe you rather want to preload more important resources than the tracking code, but it is an option to consider. If you load your JavaScript tracker file in the <head> of your website, this should not be needed.

  Advanced options

  If you want to go even further, you can think about serving the JavaScript tracking file via a CDN, merging the JavaScript tracker file content with your other JavaScript files, making use of service workers (and even track data offline), and more. Feel free to get in touch with us if you have any questions.

  More performance improvements

  Read our first blog in the series at Different ways of embedding the Piwik tracking code for faster website performance