Recherche avancée

Médias (91)

Autres articles (73)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP 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, par

    Chaque 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 (...)

Sur d’autres sites (8855)

  • Join us for the Piwik Community Meetup 2015 !

    25 juin 2015, par Piwik Core Team — Community, Meta

    We’re excited to announce that our third Piwik Community Meetup will be held in Berlin on Tuesday, the 4th of August, 2015. Don’t miss this great opportunity to connect with other users and meet the core team behind Piwik. It’s free, so REGISTER TODAY ! And maybe you would like to share your Piwik use case ? We’re also waiting for your presentation ideas.

    We will cover some of the upcoming features, discuss the future of Piwik, share tricks and hacks to help you get the most out of your Piwik platform, and socialise. If you use Piwik to improve your websites and apps, or are just generally curious about digital analytics and marketing – this event is not to be missed. As our core team is scattered all over the world, this will be a rare opportunity for you to meet and talk to us all at once – especially for those of you interested in the platform, integrating your app with Piwik, and building plugins.

    After the official part, we would like to enjoy drinks with all the participants in the nearby bars. We hope you will be able to join us !

    All Piwik community members are warmly invited to take part in the meetup !

    Piwik Community Meetup 2015

    When ?

    Tuesday, the 4th of August, from 5-9pm

    Where ?

    Kulturbrauerei
    Schönhauser Allee
    Prenzlauer Berg area
    Berlin, Germany
    exact directions tbc.

    Languages :

    English and German

    Book tickets :

    BOOK YOUR FREE INVITATION HERE

    Open call for YOUR presentation ideas

    We would also like to hear how you use Piwik – we’ll be delighted if you’d share your interesting use case during the Meetup. Please send your presentation ideas (speaking time : 5 to 7 minutes) to : meetup@piwik.pro ! Deadline : 20th of July 2015.

    Contact the organisers :

    meetup@piwik.pro

  • Documentation #3972 : template variants and possible bug ?

    6 juillet 2017, par Kamran Mir Hazar

    I have SPIP 3.1.6 [23444].

    On Thu, Jul 6, 2017 at 8:20 PM, <> wrote :

    La demande #3972 a été mise à jour par nico d_.

    Hi,
    which version of SPIP are you using ?


    Anomalie #3972 : template variants and possible bug ?

    Auteur : Kamran Mir Hazar
    Statut : Nouveau
    Priorité : Normal
    Assigné à :
    Catégorie :
    Version cible :
    Resolution :
    Navigateur :

    Hello,
    The following template variants do not work for me :
    I have section number 101, with articles in fa and en languages in it.
    I have also files article.html for the main site’s language which is fa, and
    article.en.html for the en language articles. Both work fine in general. I
    created two other variants to apply articles in section 101 with two
    separate languages. They are : article=101.fa.html and article=101.en.html .
    SPIP ignores these two variants and proceeds article.html for fa language
    articles, and article.en.html for en language articles in section 101, like
    the other sections. I added also article=101.html to see if it works, but
    didn’t.
    I asked this in French and English mailing lists, but couldn’t find any
    solution.
    Thank you
    Kamran

    PS : I tried based of the following article :
    https://www.spip.net/en_article4363.html


    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

  • Libavcodec "the procedure entry point for av_frame_alloc could not be located" error in Visual Studio 2017 C++ project

    25 novembre 2019, par Aves

    I am trying to use libavcodec from ffmpeg library in C++ with Visual Studio 2017 Community. I downloaded the latest x64 dev and shared builds from zeranoe (version 20171217), set up include directories and additional libraries in Visual Studio for x64 build, added DLL files from shared package to my PATH.

    This is my sample test code :

    extern "C" {
    #include
    }
    int main() {
       avcodec_register_all();
       AVFrame *pAvFrame = av_frame_alloc();
       av_frame_free(&amp;pAvFrame);
       return 0;
    }

    The code compiles without problems but when I run the application I see a dialogue window with error message "the procedure entry point for av_frame_alloc could not be located in DLL" (actual message is not in English, this is the translated version).

    I tried to set Linker->Optimization->References to /OPT:NOREF as it was advised in the similar questions but it did not help.

    Dependency walker shows that av_frame_alloc is exported, "Entry Point" is not bound. A little bit strange is that av_frame_alloc is displayed in both avcodec-58.dll (as red) and avutil-56.dll (as green). Maybe the reason is that the application is trying to get this function from avcodec instead of avutil, but I’m not sure, since I did not check the source code of these libraries.

    So the question is how to set up such a simple FFMPEG-based C++ project in VS2017, where I’m wrong ?

    UPD. 1.

    Linker flags : /OUT :"C :\work\code\TestFfmpeg\x64\Release\TestFfmpeg.exe" /MANIFEST /NXCOMPAT /PDB :"C :\work\code\TestFfmpeg\x64\Release\TestFfmpeg.pdb" /DYNAMICBASE "c :\work\dev\ffmpeg-20171217-387ee1d-win64-dev\lib*.lib" "kernel32.lib" "user32.lib" "gdi32.lib" "winspool.lib" "comdlg32.lib" "advapi32.lib" "shell32.lib" "ole32.lib" "oleaut32.lib" "uuid.lib" "odbc32.lib" "odbccp32.lib" /DEBUG:FULL /MACHINE:X64 /OPT:NOREF /PGD :"C :\work\code\TestFfmpeg\x64\Release\TestFfmpeg.pgd" /MANIFESTUAC :"level=’asInvoker’ uiAccess=’false’" /ManifestFile :"x64\Release\TestFfmpeg.exe.intermediate.manifest" /OPT:ICF /ERRORREPORT:PROMPT /NOLOGO /TLBID:1