Recherche avancée

Médias (91)

Autres articles (62)

  • Les statuts des instances de mutualisation

    13 mars 2010, par

    Pour des raisons de compatibilité générale du plugin de gestion de mutualisations avec les fonctions originales de SPIP, les statuts des instances sont les mêmes que pour tout autre objets (articles...), seuls leurs noms dans l’interface change quelque peu.
    Les différents statuts possibles sont : prepa (demandé) qui correspond à une instance demandée par un utilisateur. Si le site a déjà été créé par le passé, il est passé en mode désactivé. publie (validé) qui correspond à une instance validée par un (...)

  • Le plugin : Gestion de la mutualisation

    2 mars 2010, par

    Le plugin de Gestion de mutualisation permet de gérer les différents canaux de mediaspip depuis un site maître. Il a pour but de fournir une solution pure SPIP afin de remplacer cette ancienne solution.
    Installation basique
    On installe les fichiers de SPIP sur le serveur.
    On ajoute ensuite le plugin "mutualisation" à la racine du site comme décrit ici.
    On customise le fichier mes_options.php central comme on le souhaite. Voilà pour l’exemple celui de la plateforme mediaspip.net :
    < ?php (...)

  • Problèmes fréquents

    10 mars 2010, par

    PHP et safe_mode activé
    Une des principales sources de problèmes relève de la configuration de PHP et notamment de l’activation du safe_mode
    La solution consiterait à soit désactiver le safe_mode soit placer le script dans un répertoire accessible par apache pour le site

Sur d’autres sites (6734)

  • Find out what people are searching when coming from search engines

    7 novembre 2017, par InnoCraft — Plugins

    At InnoCraft, we know that SEO is an important topic for most of you. If you have not heard of this term before, SEO stands for Search Engine Optimization. It consists in having your content website visible within the search result pages without paying for ads. SEO is also often referred as “natural” or “organic” traffic.

    In SEO, one of the most valuable data to analyze is the keyword used by the visitor to come to your website. Since 2011, major search engines decided to not disclose this data anymore, that’s the reason why you are seeing the “Keyword not defined” data within some of your Piwik reports, also called “not provided” :

    keyword not defined in Piwik

    Keyword not defined in Piwik

    The solution

    As your keyword data is collected by search engines, each of them provides the searched keywords within different services such as :

    • Google Search Console
    • Bing/Yahoo Webmaster tools
    • Yandex Webmaster

    Those services allow website owners to see how many times their website appeared within the SERP (Search Engine Results Page), how bots are crawling your pages, which search terms they used, and more. The drawback is, that they make take this data available only for a short period, you need to log in to all these services to get the insights you need and you cannot get aggregated overall keyword reports (over all search engines combined).

    The solution that gives you all this data in Piwik

    Would you like to know what the not defined search keywords in Piwik really are ? Would you like to combine keywords data from major search engines in one place ? Would you like to know how important your website is according to Google and Microsoft Bing and Yahoo ?

    At InnoCraft, the company behind Piwik, we created a plugin called “Search Engine Performance Keywords”. With this plugin, you will :

    1. be able to keep the search terms forever
    2. save time by crossing data from Google and Bing search within Piwik
    3. get an overview of how Google and Bing are crawling your site
    4. monitor search rankings and click-through rates for each keyword

    1 – Data ownership & data retention

    Once more, it is going back to Piwik roots. As Piwik is a Free software, you own the data you collect. Once the import is successful, you will be able to keep the keywords data as long as you wish. In the case of services such as Google Search Console, they will delete the data after 90 days !! Without our plugin you will not be able to analyze precisely how your SEO is doing month by month, year by year.

    2 – Save time by using a single interface

    Google and Bing have no interest in gathering data coming from various search engines… we do. As a result, with our plugin you can visualize the data coming from those two sources within a single report in order to analyze your SEO in a better way.
    You will not have to use spreadsheets anymore and no chance to miss some important keywords which you would maybe miss when you don’t aggregate them in a single report.

    3 – Crawl overview check

    Both Google and Bing have a crawl “budget”. This budget needs to be optimized in order for search engine bots to consider the most relevant pages. By gathering all the data within Piwik you will have a clear view of how well your website is appreciated by search engines :

    4 – Monitor search rankings

    The Search Engine Keywords Performance feature allows you to monitor search rankings for a given keyword and see his evolution :

    it also gives you the possibility to compare the performances of several keywords in order to see how your website is performing as a whole :

    How to get started ?

    The “Search Engine Keywords Performance” plugin has been developed by the InnoCraft team as a premium feature.

    If you are not sure, note that InnoCraft is offering an unconditional and hassle-free 30-day money back guarantee period.

    Once you have installed the plugin, follow the guide in order to have it up and running.
    The installation process is not difficult in itself but takes some time as it requires to access to Google and Bing APIs.

    If you enjoyed this article, you may appreciate the following one about how to integrate ad services to Piwik : Make better online marketing decisions with the AOM plugin.

  • How to contribute to open source, for companies

    18 octobre 2010, par Dark Shikari — development, open source, x264

    I have seen many nigh-incomprehensible attempts by companies to contribute to open source projects, including x264. Developers are often simply boggled, wondering why the companies seem incapable of proper communication. The companies assume the developers are being unreceptive, while the developers assume the companies are being incompetent, idiotic, or malicious. Most of this seems to boil down to a basic lack of understanding of how open source works, resulting in a wide variety of misunderstandings. Accordingly, this post will cover the dos and don’ts of corporate contribution to open source.

    Do : contact the project using their preferred medium of communication.

    Most open source projects use public methods of communication, such as mailing lists and IRC. It’s not the end of the world if you mistakenly make contact with the wrong people or via the wrong medium, but be prepared to switch to the correct one once informed ! You may not be experienced using whatever form of communication the project uses, but if you refuse to communicate through proper channels, they will likely not be as inclined to assist you. Larger open source projects are often much like companies in that they have different parts to their organization with different roles. Don’t assume that everyone is a major developer !

    If you don’t know what to do, a good bet is often to just ask someone.

    Don’t : contact only one person.

    Open source projects are a communal effort. Major contributions are looked over by multiple developers and are often discussed by the community as a whole. Yet many companies tend to contact only a single person in lieu of dealing with the project proper. This has many flaws : to begin with, it forces a single developer (who isn’t paid by you) to act as your liaison, adding yet another layer between what you want and the people you want to talk to. Contribution to open source projects should not be a game of telephone.

    Of course, there are exceptions to this : sometimes a single developer is in charge of the entirety of some particular aspect of a project that you intend to contribute to, in which case this might not be so bad.

    Do : make clear exactly what it is you are contributing.

    Are you contributing code ? Development resources ? Money ? API documentation ? Make it as clear as possible, from the start ! How developers react, which developers get involved, and their expectations will depend heavily on what they think you are providing. Make sure their expectations match reality. Great confusion can result when they do not.

    This also applies in the reverse — if there’s something you need from the project, such as support or assistance with development of your patch, make that explicitly clear.

    Don’t : code dump.

    Code does not have intrinsic value : it is only useful as part of a working, living project. Most projects react very negatively to large “dumps” of code without associated human resources. That is, they expect you to work with them to finalize the code until it is ready to be committed. Of course, it’s better to work with the project from the start : this avoids the situation of writing 50,000 lines of code independently and then finding that half of it needs to be rewritten. Or, worse, writing an enormous amount of code only to find it completely unnecessary.

    Of course, the reverse option — keeping such code to yourself — is often even more costly, as it forces you to maintain the code instead of the official developers.

    Do : ignore trolls.

    As mentioned above, many projects use public communication methods — which, of course, allow anyone to communicate, by nature of being public. Not everyone on a project’s IRC or mailing list is necessarily qualified to officially represent the project. It is not too uncommon for a prospective corporate contributor to be turned off by the uninviting words of someone who isn’t even involved in the project due to assuming that they were. Make sure you’re dealing with the right people before making conclusions.

    Don’t : disappear.

    If you are going to try to be involved in a project, you need to stay in contact. We’ve had all too many companies who simply disappear after the initial introduction. Some tell us that we’ll need an NDA, then never provide it or send status updates. You may know why you’re not in contact — political issues at the company, product launch crunches, a nice vacation to the Bahamas — but we don’t ! If you disappear, we will assume that you gave up.

    Above all, don’t assume that being at a large successful company makes you immune to these problems. If anything, these problems seem to be the most common at the largest companies. I didn’t name any names in this post, but practically every single one of these rules has been violated at some point by companies looking to contribute to x264. In the larger scale of open source, these problems happen constantly. Don’t fall into the same traps that many other companies have.

    If you’re an open source developer reading this post, remember it next time you see a company acting seemingly nonsensically in an attempt to contribute : it’s quite possible they just don’t know what to do. And just because they’re doing it wrong doesn’t mean that it isn’t your responsibility to try to help them do it right.

  • avutil/imgutils : Constify some pointees

    6 septembre 2023, par Andreas Rheinhardt
    avutil/imgutils : Constify some pointees
    

    This is done immediately without waiting for the next major bump
    just as in 9546b3a1cbcd94e9107f85c8f1d2175efc6cf083 and
    4eaaa38d3dfb8863a62f3646a62e4098b1c078d5.

    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>

    • [DH] doc/APIchanges
    • [DH] libavutil/imgutils.c
    • [DH] libavutil/imgutils.h
    • [DH] libavutil/version.h