
Recherche avancée
Médias (91)
-
Richard Stallman et le logiciel libre
19 octobre 2011, par
Mis à jour : Mai 2013
Langue : français
Type : Texte
-
Stereo master soundtrack
17 octobre 2011, par
Mis à jour : Octobre 2011
Langue : English
Type : Audio
-
Elephants Dream - Cover of the soundtrack
17 octobre 2011, par
Mis à jour : Octobre 2011
Langue : English
Type : Image
-
#7 Ambience
16 octobre 2011, par
Mis à jour : Juin 2015
Langue : English
Type : Audio
-
#6 Teaser Music
16 octobre 2011, par
Mis à jour : Février 2013
Langue : English
Type : Audio
-
#5 End Title
16 octobre 2011, par
Mis à jour : Février 2013
Langue : English
Type : Audio
Autres articles (84)
-
Creating farms of unique websites
13 avril 2011, parMediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...) -
Le profil des utilisateurs
12 avril 2011, parChaque utilisateur dispose d’une page de profil lui permettant de modifier ses informations personnelle. Dans le menu de haut de page par défaut, un élément de menu est automatiquement créé à l’initialisation de MediaSPIP, visible uniquement si le visiteur est identifié sur le site.
L’utilisateur a accès à la modification de profil depuis sa page auteur, un lien dans la navigation "Modifier votre profil" est (...) -
Configurer la prise en compte des langues
15 novembre 2010, parAccéder à la configuration et ajouter des langues prises en compte
Afin de configurer la prise en compte de nouvelles langues, il est nécessaire de se rendre dans la partie "Administrer" du site.
De là, dans le menu de navigation, vous pouvez accéder à une partie "Gestion des langues" permettant d’activer la prise en compte de nouvelles langues.
Chaque nouvelle langue ajoutée reste désactivable tant qu’aucun objet n’est créé dans cette langue. Dans ce cas, elle devient grisée dans la configuration et (...)
Sur d’autres sites (9293)
-
Anomalie #2964 (Rejeté) : Développement boite d’options inverser
26 mars 2013, par Eric CamusSPIP 3.0.7 et IE8. Le développement des boites d’option cachées par l’activation d’une fonction comme dans ’Configuration->Interactivité->Notification->Envoyer les annonces à l’adresse’ ne se développent pas en cliquant sur les casses à cochés mais se développent sur l’inverse (’Ne pas envoyer (...)
-
Announcing Long Term Support in Piwik 2 – The analytics platform for your mission critical projects
11 janvier 2016, par Matthieu Aubry — About, DevelopmentWe are proud to announce our Long Term Support (LTS) for Piwik 2.X !
Why Long Term Support (LTS) ?
Part of our mission is to ready Piwik for the enterprise — and ready the enterprise for Piwik. Our fast release cycle and our ability to quickly innovate has served us well for the past seven years and has lead Piwik to being one of the most popular open source projects, used by over one million websites worldwide. But Piwik’s success today has also shown us that this fast release cycle is not suited for all users and customers. Like most large open source projects (such as Ubuntu, Firefox, Debian, Symfony, Node.js, etc.) at Piwik we now also offer a Long Term Support release which gives users the confidence that Piwik can be used for mission critical projects for months to come.
What does LTS mean for Piwik ?
For the duration of the LTS period, Piwik 2.X will continue to receive the following fixes :
- Critical bugs causing data loss or data corruption.
- Major and Critical security issues.
Our goal is to offer you a Piwik LTS release that you can trust for all your mission critical projects.
How long will Piwik 2.X be supported ?
Piwik 2.X will be supported for at least 12 months after the initial release of Piwik 3.0.0.
Piwik 3.0.0 is expected to be released in the second half of 2016.
This means that Piwik 2.X will be supported at least until the second half of 2017.Which Piwik version is LTS ?
The latest Piwik 2.16.X release is our Long Term Support version.
How do I benefit from the LTS version ?
To get the full benefits of Piwik LTS, please make sure you are using the latest LTS version. First, update to the latest Piwik 2.X version, then Configure Piwik to use the LTS release channel and then update to the latest LTS version.
How do I configure Piwik to use the LTS version ?
By default, Piwik will not use the LTS version. When you use the one-click update your Piwik instance will be updated to the very latest release : when Piwik 3.0.0 will be released, the one click update will update your instance to 3.0.0. It is however possible to configure your Piwik so that you will stay on Piwik 2.X and keep using the LTS Long Term Support version :
- Login Piwik as the Super User,
- Go to Settings > General > Update settings,
- Under “Release channel” click “Latest stable 2.X Long Term Support version”, and click “Save”.
How do I get professional Piwik Support ?
If you need professional support for your Piwik service get in touch with the Piwik experts.
For other questions, feedback or discussion, feel free to join our forums and comment on this LTS forum post.
We wish you all a fantastic year 2016 !
-
Mirror not found when trying to install FFMPEG on CENTOS7
31 octobre 2016, par PeterI’m on a dedicated server with Root access. not familiar with servers. Im trying to install FFMpeg on my server but following online instructions I’m getting errors can’t figure out how to solve it. So any light on this will be very appreciated.
[root@ns335004 ~]# yum update
base | 3.6 kB 00:00:00
http://apt.sw.be/redhat/el7/en/x86_64/dag/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below knowledge base article
https://access.redhat.com/articles/1320623
If above article doesn't help to resolve this issue please create a bug on https://bugs.centos.org/
One of the configured repositories failed (DAG RPM Repository),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Disable the repository, so yum won't use it by default. Yum will then
just ignore the repository until you permanently enable it again or use
--enablerepo for temporary usage:
yum-config-manager --disable dag
4. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=dag.skip_if_unavailable=true
failure: repodata/repomd.xml from dag: [Errno 256] No more mirrors to try.
http://apt.sw.be/redhat/el7/en/x86_64/dag/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Foundrepolist
[root@ns335004 ~]# yum repolist all
http://apt.sw.be/redhat/el7/en/x86_64/dag/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below knowledge base article
https://access.redhat.com/articles/1320623
If above article doesn't help to resolve this issue please create a bug on https://bugs.centos.org/
http://apt.sw.be/redhat/el7/en/x86_64/dag/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
repo id repo name status
C7.0.1406-base/x86_64 CentOS-7.0.1406 - Base disabled
C7.0.1406-centosplus/x86_64 CentOS-7.0.1406 - CentOSPlus disabled
C7.0.1406-extras/x86_64 CentOS-7.0.1406 - Extras disabled
C7.0.1406-fasttrack/x86_64 CentOS-7.0.1406 - CentOSPlus disabled
C7.0.1406-updates/x86_64 CentOS-7.0.1406 - Updates disabled
C7.1.1503-base/x86_64 CentOS-7.1.1503 - Base disabled
C7.1.1503-centosplus/x86_64 CentOS-7.1.1503 - CentOSPlus disabled
C7.1.1503-extras/x86_64 CentOS-7.1.1503 - Extras disabled
C7.1.1503-fasttrack/x86_64 CentOS-7.1.1503 - CentOSPlus disabled
C7.1.1503-updates/x86_64 CentOS-7.1.1503 - Updates disabled
base/7/x86_64 CentOS-7 - Base enabled: 9,007
base-debuginfo/x86_64 CentOS-7 - Debuginfo disabled
base-source/7 CentOS-7 - Base Sources disabled
c7-media CentOS-7 - Media disabled
centosplus/7/x86_64 CentOS-7 - Plus disabled
centosplus-source/7 CentOS-7 - Plus Sources disabled
cr/7/x86_64 CentOS-7 - cr disabled
dag/7/x86_64 DAG RPM Repository enabled: 0
epel/x86_64 Extra Packages for Enterprise Linux 7 - x86_64 enabled: 10,764
epel-debuginfo/x86_64 Extra Packages for Enterprise Linux 7 - x86_64 - Debug disabled
epel-source/x86_64 Extra Packages for Enterprise Linux 7 - x86_64 - Source disabled
epel-testing/x86_64 Extra Packages for Enterprise Linux 7 - Testing - x86_64 disabled
epel-testing-debuginfo/x86_64 Extra Packages for Enterprise Linux 7 - Testing - x86_64 - Debug disabled
epel-testing-source/x86_64 Extra Packages for Enterprise Linux 7 - Testing - x86_64 - Source disabled
extras/7/x86_64 CentOS-7 - Extras enabled: 393
extras-source/7 CentOS-7 - Extras Sources disabled
fasttrack/7/x86_64 CentOS-7 - fasttrack disabled
nux-dextop/x86_64 Nux.Ro RPMs for general desktop use disabled
nux-dextop-testing/x86_64 Nux.Ro RPMs for general desktop use - testing disabled
plesk-php-5.6 PHP v 5.6 for Plesk - x86_64 enabled: 31
plesk-php-7.0 PHP v 7.0 for Plesk - x86_64 enabled: 28
updates/7/x86_64 CentOS-7 - Updates enabled: 2,560
updates-source/7 CentOS-7 - Updates Sources disabled
repolist: 22,783I also tried :
sudo yum clean metadata
sudo yum clean allBut still having same 404 Error.
Thanks.