Skip to content
Grav 2.0 is officially stable. Read the announcement →

Community guidelines

Please keep discussions civil and on-topic. Repeated violations may lead to a temporary ban.

gaetan Newcomer

@gaetzone · Joined 9 years ago · 6 posts · 1 topics · 2 reputation

Badges

✏️ First Post 💬 Conversation Starter

Recent posts

  • Merry Christmas & Happy New #2k18 · 8 years ago

    Merry xMAss to all the developers how are involved in this so nice Grav project. Cheers

  • # /bin/gpm return nothing · 9 years ago

    Filled correctly, off course. But with a local address. Maybe it is the problem. It's a shame that gpm is not returning an error. Maybe, this could be revised by a futur update of gpm.

  • # /bin/gpm return nothing · 9 years ago

    Well, I found the explanation. If custom_base_url is filled in system.yaml, bin/gpm is not working. Maybe because I am working on a local machine.

  • # /bin/gpm return nothing · 9 years ago

    Sure the # was mentioned to show that I am using bin/gpm in a terminal. I have done a fresh reinstall of the Grav Skeleton and erased the user directory with mine. bin/gpm is working now. I do not und

  • # /bin/gpm return nothing · 9 years ago

    thanks for your reply Makary bin/gpm is actually executable. And if I override the gpm file with the one from the official repository, same pb appear.

  • # /bin/gpm return nothing · 9 years ago

    Hi everyone, On my local machine with Ubuntu 16.04, I have updated Grav core from 1.3.3 to 1.3.8 by using the command line # bin/gpm self-upgrade. All ran perfectly and I get now the new Grav version