Closed petemolinero closed 1 year ago
Sounds like you're getting an older version pulled in by composer - something before 1.1. What PHP version are you running?
Composer version 2.3.10 2022-07-13 15:48:23
Thats your composer version, I need PHP. For context this package is PHP 8+ so if you're below that you'd need to update.
Oops, yep, I misread that. My PHP version is 7.4.30
, which would explain it. Thanks!
Thanks for the quick replies! Should be a simple resolution. Also, what's the technical answer to my Change the structure tree in content/collections/pages.yaml
confusion up above?
Yes its the latter (though I've personally found you dont need this step if everything is running from eloquent).
Closing this. I've added a PR to fix that tree
filepath typo.
I just installed a fresh installation of Statamic 3.4 (actually, I tried this first with Statamic 3.3.67, with the same result). Then I did the following commands/tasks from within the Statamic root directory:
composer require statamic/eloquent-driver
✅php artisan vendor:publish --tag="statamic-eloquent-config"
✅content/collections/pages/home.md
✅tree
incontent/collections/pages.yaml
to{}
... My copy ofcontent/collections/pages.yaml
does not have atree
key. Not sure if I'm supposed to add one with the value of{}
, or am supposed to actually be modifying the file incontent/trees/collections/pages.yaml
. I'm guessing the latter? I've tried both. Maybe ✅php artisan vendor:publish --provider="Statamic\Eloquent\ServiceProvider" --tag=migrations
. I got a message sayingNo publishable resources for tag [migrations]. Publishing complete.
Is that normal? ✅php artisan vendor:publish --tag="statamic-eloquent-entries-table"
✅php artisan migrate
✅At this point, according to the readme, I might be done? It says:
Problem is, the entire contents of my
config/statamic/eloquent-driver.php
file are as follows:I also tried running things like
php please eloquent:import-collections
, and got an error saying:I also noticed that there was a migration to add an entries table, but no migrations for any other type of content.
Is this normal and I'm just missing something? How do I get things other than entries to be database-based?