Closed pawelandrzejewski89 closed 4 years ago
Yeah - I'm getting this too
This same issue is on another grav plugin: https://github.com/getgrav/grav-plugin-email/issues/128#issuecomment-590375041 and it also been reported a few days ago.
In both cases plugin's are using ResourceLocator form rocketheme vendor - maybe the issue is in communication between ResourceLocator and Plugin?
OK - just tested with grav version 1.6.17 and no problems.
There are inconsistencies upstream in the betas and release candidates for core 1.7, so the upcoming refactor for this plugin will be locked to Grav v1.6 until v1.7 stabilizes.
I can confirm that: 1.6.17 works, 1.6.19 also work , 1.6.20 also work,
1.6.21 doesn't work.
Info from other module: "The issue is caused by this change https://github.com/getgrav/grav/blob/1.7/UPGRADE-1.7.md#cli-1" "Here is the change itself getgrav/grav@48170d2"
Yes, these new changes need to be integrated for v2.0.0. It is unfortunate that they were introduced for 1.6.21, and not delayed until 1.7. This is why I need to have a distinct version for 1.6 and 1.7; there's just too many changes to integrate until 1.7 stabilizes.
Implemented for v2.0.0-beta.1, which is tested with Grav 1.6.22. The dependencies listed in blueprints.yaml should lock it to this version, if the GPM parses it correctly.
The refactor for v2.0.0 is now released, tested with Core v1.6.22 and v1.7.0-rc.7. Note that the plugin requires Grav v1.6.21 or higher, or v1.7.0-rc.6 or higher for testing-releases.
Hi, I'm trying to use the plugin to generate static content, but any try of use (index, page, test) returns same error: ``
Looks like it failed on content validation. Grav is up to date, plugins also are. Any idea?:)