Jump to content

vincent

Members
  • Posts

    10
  • Joined

  • Last visited

Everything posted by vincent

  1. Hi everyone, Hi @virtualgadjo, Thank you for your translation of the last master release. I also did some translations for it so I merged our works into a release. As a new master release will soon be released, don't forget to check the dev branch of the french repo : https://github.com/v-maillard/pw-lang-fr/compare/master...v-maillard:pw-lang-fr:dev?diff=split. I already translated for the 3.0.217's version of ProcessWire. So, if you start translating, you'll need to download this dev .zip ( https://github.com/v-maillard/pw-lang-fr/archive/refs/heads/dev.zip) first in order to have an up-to-date translation. Have a nice day, Vincent
  2. Hi everyone, Hi Chris, A few days ago, I manually integrated the @virtualgadjo changes. So we have a new release for the version on the repo 3.0.200: https://github.com/v-maillard/pw-lang-fr/releases/tag/v3.0.200 For the rest, I created a dev branch. It is on this branch that I started to push modifications concerning the dev version of ProcessWire (currently 3.206). The ongoing work is visible here: https://github.com/v-maillard/pw-lang-fr/compare/master...v-maillard:pw-lang-fr:dev?diff=split Have a nice day, Vincent
  3. Hi Chris, I understand your point of view completely. In the next few days, I will manually integrate your work (by tagging you because I think it's normal). I'll keep you posted, especially if I make any changes later. If you're interested, I'm thinking of listing some revisions and general rules that we could implement for the translation. I'll need to go back over the details and make suggestions. Have a good weekend, Vincent
  4. Hello Chris, I found this video (in french) that explains how to do a pull request: https://www.youtube.com/watch?v=U5xYWy6zJGY. The advantage is that you can have your own repository and I can easily integrate your commits. The drawback is that if you're not used to it, it may not be practical to use. Especially if I also make commits on my side or integrate other pull requests because you'll have to keep your fork up to date (https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork). If it's too complicated, I can do as I wrote above: integrate your work through a commit by tagging you. But I also thought of another solution: I can add you as a collaborator to the Github repository so that you can contribute directly. I understand what you have set up with the different repositories for the different versions of Processwire. But I think it's better to use the tags and releases to do it. For example, on the current repo, it is possible to download .zip files of old tags: https://github.com/v-maillard/pw-lang-fr/tags and install them directly by the admin. If you want to provide zips to your friends, it would be easier to use tags. To sum up: in my opinion, the best solution is pull requests (you can make pull requests from your repo fork). But if it's too complicated, the simplest solution is to add you as a collaborator (you'll have direct access to the repo). In any case, you'll have to work with .json files and we'll use tags to archive the versions in .zip. What solution do you prefer? Vincent
  5. Hello @virtualgadjo, First of all, sorry for the very late reply. I have let too much time pass without maintaining the French language pack. I am starting to use Processwire again for projects so I'll try to catch up. I'd be happy to integrate your work into the GitHub repository but you haven't made a pull request. Can you make one? Ideally, you don't want to go through a .zip, but keep the .json files so that versioning can be done. Or if you prefer, I can commit your work by tagging you. I will also update the readme to credit you. Once that's done, we can continue the translation work on the new versions. Have a nice day, Vincent
  6. Thanks for your response, Andreas. I forked the repository on Github but actually it is archived and in read-only mode. I can't add a pull request. I will wait to see if Pierre-Luc come here, or maybe contact him by PM.
  7. Hi everyone, I created a new version of this language pack for supporting ProcessWire 3.x : https://gitlab.com/vmaillard/pw_3.x_lang_fr Since the GitHub repository was last updated in December 2016, I don't know exactly what to do with my version. Should I create a new module in the Language Packs directory? There could be the "French Language Pack (fr-FR)" and the "French Language Pack (fr-FR) for ProcessWire 3.x". Have a nice day!
  8. Hi @BFD Calendar I know it’s been a long time since you have reported your issue-almost one year. But I experienced the same issue on the same provider (OVH) and I found a solution. Maybe it can help: in my client interface my global PHP configuration was still set to "Legacy", I changed it to « stable » and I am now able to use the Processwire upgrade module. It can also be done in the .ovhconfig file by changing "container.image=legacy" to "container.image=stable".
  9. @netcarver your version fixes the conflict in my installation. Thank you !
  10. Hello @adrian and @netcarver I think I have the same issue here. When I try to hide the tab "Settings", I can't add a new repeater field item on a page if I'm logged in as a non-superuser. With other choices ("Children", "Restore", etc) there is no conflict.
×
×
  • Create New...