Recherche avancée

Sur d’autres sites (6311)

• Anomalie #3523 : Gestion des plugins avec spip 3.0.20

  4 août 2015, par Philippe MARECHAL

  Bonsoir et merci pour les retours.

  Le phpinfo est visible à cette adresse : http://pmarechal.fr/phpinfo.htm.
  La section zend opcache contient la conf opcache.

  Je suis sous PHP 5.5 (mais un autre hébergé a le même pb en 5.4) avec MySQL

  Concernant mon site :
  nativement sous SPIP 3.0.x, mis à jour au fur et à mesure de la sortie des nouvelles versions.
  La 3.0.20 fonctionnait sans pb jusqu’à la mise en place chez mon hébergeur Web4all d’un serveur dédié à l’administration des CMS (et utilisant opcache).
  Je suis ensuite passé à SPIP 3.1 beta, build 22323 (je suis un peu en retard...) pour voir si ça changeait quelque chose, mais le pb de lenteur est resté

• Anomalie #3608 (Nouveau) : Tables de la base de données indispo depuis l’espace privé quand le pré...

  29 novembre 2015, par Franck Dalot

  Bonjour
  SPIP 3.1.0-rc [22601]
  Php 5.4.45

  Lorsque l’on active le menu dev via en cochant la case "ecrire/ ?exec=configurer_preferences"
  et que l’on demande à voir les tables dans un site donc le préfix des tables n’est pas "spip" cela ne fonctionne pas, si l’on coche sur le nom d’une table.
  Par contre, cela fonctionne si dans l’URL je tape : ecrire/ ?exec=vertebres&table=spip_articles sauf que sur la page, cela écris "spip_articles" au lieu de "spip2_articles"
  Dans le cas présent, le préfix est "spip2"

  A savoir que cela fonctionnait en SPIP 3.1.0-beta [22455] avec un site dont le préfix est "spip1"
  Voir copies d’écran
  Franck

• To all Matomo plugin developers : Matomo 4 is coming, make your plugin compatible now

  6 août 2020, par Matomo Core Team — Development

  We’re planning to release the first beta of Matomo 4 in a few weeks. For making it easy for Matomo users to be able to upgrade to this beta, it would be great if as many plugins on the Marketplace as possible would be already updated and compatible with Matomo 4. Then many users would be able to upgrade to the first beta without any issues.

  Presumably, as you put your plugin on our Marketplace, you want people to use it. Making your plugin compatible with Matomo 4 helps ensure that people will be able to find and keep using your plugin. If your plugin is not compatible with Matomo 4, your plugin will be automatically deactivated. We’ll be happy to help you achieve compatibility should there be any issue.

  How do I upgrade my Matomo to Matomo 4 ?

  If you have installed your Matomo development environment through git you can simply checkout the Matomo 4 branch “4.x-dev” by executing these commands :

  • git checkout 4.x-dev 
  • composer install

  Alternatively, you can also download the latest version directly from GitHub as a zip file and run composer install afterwards. 

  How do I upgrade my plugin to Matomo 4 ?

  • We recommend you create a new branch for your plugin that supports Matomo 4. For example a branch named “4.x-dev“. This way you will be able to make changes to your plugin for Matomo 3 and Matomo 4 and release separate versions.
  • Check out our migration guide from Matomo 3 to Matomo 4 and the list of all breaking changes.
  • Release a new version of your plugin in GitHub as usual.

  While there were many breaking changes in Matomo 4, most of our Platform APIs remain unchanged, and almost all changes are for rarely used APIs. Often to make your plugin compatible it will just be a matter of adjusting the “plugin.json” file (as mentioned in the migration guide).

  You can find all developer documentation on our developer zone which has already been updated for Matomo 4.

  How do I know my plugin changes were released successfully ?

  If you have configured an email address within your “plugin.json” file, then you will receive a confirmation or an error email within a few minutes. Alternatively, you can also check out your plugin page on the Marketplace directly. If the plugin release was successful, you will see additional links below the download button showing which versions your plugin is compatible with.

  

  How can I downgrade to Matomo 3 or switch between Matomo 3 and Matomo 4 ?

  To downgrade from Matomo 4 to Matomo 3 :

  • check out the “3.x-dev” branch 
  • run a composer install as usual. 
  • run the SQL statements from this downgrade guide to restore the previous MySQL schema.

  When will the final Matomo 4 release be available ?

  We estimate the final stable Matomo 4.0.0 release will be released in approx. 3 months.

  What’s new in Matomo 4 ?

  We don’t have a summary of the changes available just yet but you can see all closed issues within this release here.

  Any questions or need help ? 

  If you have any questions, or experience any problems during the migration don’t hesitate to get in touch with us. We’ll be happy to help get your plugin compatible and the update published. If you find any undocumented breaking change or find any step during the migration process not clear, please let us know as well.

  Thank you for contributing a plugin to the Marketplace and making Matomo better. We really appreciate your work !