Updating to newer Grav versions

Hi, my team has a webpage in Grav v1.1.17 Admin v1.2.14 and I'm looking after that website now.

Should I update it to Grav v2.0 and how would I do that? I'm not a developer and any simple instructions would be helpful. I can't even apply the Step 1 - Back up your site in Assisted Migration to Grav 2.0 | Grav Documentation.

Thank you

@waters_admin, Are you sure you have a website running Grav v1.1.17, which is 10 years old????

A few notes:

• AFAIK, you cannot upgrade from Grav v1.1.17 to Grav v2.0 automatically.
• You'll need to upgrade to the latest stable version first: v1.7.52.
• I guess there will be many breaking changes when going from v1.1.17 to v1.7.52.
• "I'm not a developer": I'm sorry to say, but I doubt you will succeed as a non developer...

thanks, I know it is very old but still alive...

I should be able to get help from a developer though so we should be okay then

Would it actually be easier/less time consuming to start from scratch and rebuild the website (there's only about 10 pages) with the latest version of Grav rather than updating it?

@waters_admin:
Would it actually be easier/less time consuming to start from scratch and rebuild the website (there’s only about 10 pages) with the latest version of Grav rather than updating it?

I'd say it depends on what kind of theme and how many and what plugins you're using.

MY experience with Grav 2 is HORRIBLE.

I used grav as a multisite, working all like a charm since grav 2 shows up.

i started with a blank installation and started to migrate content as well as plugins and themes and NOTHING is working! Have to rework soooooo much that i think of changing to a complete different CMS as Grav2 feels completly different and with this upgrade experience i lost my confidence in grav at the moment completly.

Now, i had a small running grav2 installation (from, scratch, only demo content) and than oday the update to 2.0.1 was released and i updated my fresh installation: BOOM .. next error :

/var/www/html/grav-2/system/src/Pimple/Container.php

        $this->keys[$id] = true;
    }

    /**
     * Gets a parameter or an object.
     *
     * @param string $id The unique identifier for the parameter or object
     *
     * @return mixed The value of the parameter or an object
     *
     * @throws UnknownIdentifierException If the identifier is not defined
     */
    public function offsetGet(mixed $id): mixed
    {
        if (!is_string($id)) {
            throw new InvalidServiceIdentifierException($id);
        }

        if (!isset($this->keys[$id])) {
            throw new UnknownIdentifierException($id);
        }

        if (
            isset($this->raw[$id])
            || !is_object($this->values[$id])
            || isset($this->protected[$this->values[$id]])
            || !method_exists($this->values[$id], '__invoke')
        ) {
            return $this->values[$id];
        }

        if (isset($this->factories[$this->values[$id]])) {
            return $this->values[$id]($this);
        }

        $raw = $this->values[$id];
        $val = $this->values[$id] = $raw($this);
        $this->raw[$id] = $raw;

        $this->frozen[$id] = true;

Arguments

"Identifier "user" is not defined."

WTF!?

i'm very unhappy how those many changes killing all my months of work and seems forcing me to a complete different system with much better update/upgrade stability.

What are your experiences? Currently the last hours invested into "learning grav from the ground" with fresh install playing around getting errors over errors dissapoint me!

btw, i'm a quite experienced developer with 30+ years in php coding.

Grav itself is not fundamentally changed. All the libraries are updated to newer versions, and there is more security features. The new stuff for admin is completely new.

I can’t tell what your problem is as that error is not pointing to any specific code except a general class, the error in logs/grav.log would be more helpful. Also information about your PHP version, plugins, theme etc would help too.

I’ve upgrade many sites including getgrav.org itself which is big and complicated and has lots of custom plugins, without major issue. But I’m sure there are billions of combinations and custom themes I can’t predict. This is why Grav2 is a migration and not an upgrade. Thats why I built the migration plugin to help you test your site alongside your 1.7 site to find issues before you commit.

anyway, don't wanted to get help with that issues just wanted to get rid of my current migration frustration about all the (for now) unexplainable behaviours.

Next thing i tested is the maintenance plugin. i have this:

          {% if maintenance.active == false %}
          false
          {% else %}
          maintenance
          {% endif %}

at a navigation.html.twig inside a theme and it doesn't evaluate any more:

in debug bar - plugins - maintenance

array:5 [
  "enabled" => true
  "active" => true
  "allow_login" => true
  "login_access" => "site.login"
  "maintenance_page_route" => null
]

it always evaluate correct before, now it's always printing "false"

haven't read the full docs but it stated somewhere that the new evaluating security stuff is not effecting the theme files and those annoying bugfixing i would have to do so excessively that it feels like ... ok, let's redo the whole website incl. theming, dammned!

the plugin didn't helped as i get tons of 500 errors after that!

i can't check all of my 50+ plugins, themes etc. .... so i will test in maybe a week or two again and if it still feels like "i lost my favorite cms because of a major , all is now better and new, udate", well ... than it maybe time to change for a more "not so aggressive updates/upgrades" system, i came from wordpress and now it start feeling the same, each update brining new major testing and bugfixing work.

but hey .. maybe it's just to early released and you know what people say: "NEVER EVER use a .0 release!"

Hope experience will be better in a few weeks, so long i will stick with 1.7 and my next test will be with a website with mostly no plugins and no fancy theme ... but i prepare my head for another system change .... again AND LOTS of work. Hey, i have 4 site, 2 of them are heavily custom plugin depending.!

That doesn't make sense obviously, and of course simple twig like that should be working. Something else more fundamental is going on. If you want, you can zip up your site (remove anything personal), and host it somewhere, PM me a link to it and i'll take a look to see what the problem is... It's probably related to configuration, but easier for me to look at the whole thing rather than just random snippets that have no context. Cheers.

I can only fix bugs I can see and reproduce, so if there is a legitimate bug, please help me get it sorted by providing me a reproducible environment. I strongly believe it's a configuration thing, because i (and everyone else) is not seeing fundamental problems like this.

Thank you, i will try later as i told you with my simplest site, me, sometimes very ambitious, tried it with my most complex site and it failed ;)

So don't take it personal, i will definitely try as i love(d?) grav a lot, and my update experience in the past where really flawless!

Maybe i just have a bad day ? ;)

Thank you anyway for your time and effort you put into this, this alone is very respectful!

i currently trying to build up from scratch.

You migration tool doesn't help at my setup for some reasons, but by hand it worked .. slowly but is also good for learning the new things in grav and no unexplained errors popping up. I will let you know if a have further problems or better open threads for specific questions i already have ;)

Yesterday was a wired day for me and please excuse my rough words, which are no appropriate for all the effort you invest into grav and by the end of the year i will put you also on my donations list ;)

Thank you and please pardon me!