Replies: 4 comments 8 replies
-
|
Hey @YoBigRube, A few things:
Also, could you please share the output of |
Beta Was this translation helpful? Give feedback.
5 replies
-
|
Hey @joshuablum, Is there a way to run a command similar to this Rolling back from the most recent Whether I update the composer.json to |
Beta Was this translation helpful? Give feedback.
-
|
Hey @YoBigRube, Yes, you can run |
Beta Was this translation helpful? Give feedback.
-
|
Hey @joshuablum I'm restarting the process from scratch. Using the Initial Install ErrorI did encounter an error on the front-end immediately after Statamic install But, it looked like the errors are result of a bug that was fixed in v3.2 - I decided to leave that error as is and migrated the v2 content into the 3.0.49 project. I saw a post here that shows an error with the same message being fixed in 3.1.x. The migrate:site process for my v2 content to 3.0.49 ran successfully, but in addition to the front-end error, I'm seeing errors in the CP. Would you please explain what these errors are and how I fix them? Environment DetailsUsing Front-end ErrorsCP ErrorsIf I try and edit 1) any existing pages 2) any collections content 3) or click the navigation link to view the taxonomies in the cp I get these errors. I know that the cp error is speaking to a missing "content tree"; I haven't worked with Statamic trees before and I'm not sure how to correctly address it in this context. If I click the cp navigation to go to Blueprints I get this error: CP Dashboard had errors too: To get the dashboard to load without errors I edited Laravel.log Contents |
Beta Was this translation helpful? Give feedback.
-
|
Hey @YoBigRube, First question: Why start from scratch? Didn't you already make quite some progress? Not entirely sure this is the way to go here. About the error: Do you have any nav or collection tree that's empty? Could you please have a look at the files? Any collection that's orderable when it shouldn't be so it expects a tree? |
Beta Was this translation helpful? Give feedback.
-
|
Hey @joshuablum, Why I restarted from scratchThat's a fair question: Because I have several separate projects following this one that all need upgrading, I'm documenting the entire process for estimating and related. But, after realizing the way I'd started off this project wasn't the ideal method, it made sense to restart so that for each project moving forward I'm following the best practices. What you had said def made sense bcuz I think some of the errors I was having with my initial attempt were related to jumping directly to the most recent release vs incrementally upgrading from 2.x to 3.0.49+. Errors:There's 5 collections. 4 of them show that error when you try to view/edit them or their blueprint in the cp.There is a I had read the trees + strucutures docs early on after the The collection that I am able to access in the cp is the only one that doesn't have a tree collection-name.yaml file. The pages collection is an example of one that has cp error. (pages.yaml tree) |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Glad you were able to successfully load the Control Panel 👍 How many assets are we talking about? Are they local or are you using something like S3? Could you please try and run the following commands:
And thanks for sending over the log! I had a look at it and it seems like the issues I saw in there are resolved. Could you please clear the log and try to access the CP etc. again. If you encounter any errors those should be in the log then. |
Beta Was this translation helpful? Give feedback.
-
|
You should fix this first: |
Beta Was this translation helpful? Give feedback.
0 replies
-
Beta Was this translation helpful? Give feedback.
2 replies
-
|
that's a lot of questions, can you please break out your actual questions? |
Beta Was this translation helpful? Give feedback.
-
|
That error means you have a field that support multiple taxonomies but the data isn't right. You've got |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey there,
Please bare with me, this is a long post, thanks in advance for your help/patience.
I'm in the process of my first Statamic v2 to v3 migration based off the official upgrade docs. I successfully updated the v2 site to latest v2 version (in a separate repo), + successfully installed a clean v3 project in its own repository where I'm attempting the migration.
The migration tool results:
0 skipped, 0 errors, 17 warnings, 76 successful.Site Migration log file: There's a lot of duplication in the log, instead of posting all of it, below is an overview.
I noticed most warnings were mentioning the v2 site's related, taxonomy, and redactor field types. Most of the warnings looked like this message:
What I've attempted so far:
Based on the log message, I updated that referenced environment variable in config/statamic/sites.php to:
`'sites' => [
Which corresponds to my .env config with app url variable value of:
APP_URL=https://cindygallop-v3.testso I'm assuming that should prevent 404 errors?I'm not sure yet on any template errors as I'm trying to understand what's causing the errors with accessing the control panel. I don't understand what this messages is saying?
cp errors:
Illuminate \ View \ ViewException PHP 8.0.24 9.42.2 array_key_exists(): Argument #1 ($key) must be a valid array offset type (View: /var/www/html/vendor/statamic/cms/resources/views/widgets/collection.blade.php)**Front-end errors:**
Statamic \ Exceptions \ DuplicateFieldException PHP 8.0.24 9.42.2 Duplicate field [related_collections_section] on blueprint [homepage].My development environment's details:
I'm using DDDEV for local dev environment. Configured as a Laravel project config type. Includes the Statamic CLI tool installed using
ddev composerand this projectddev get mandrasch/ddev-addon-statamic-pleaseI tested that the local ddev environment + Statamic CLI work by doing an install of a default Statamic v3 project before attempting a migration and that worked fine. I was able to
php please make:usersuccessfully and login to the cp and navigate around there. The front end loaded the new Statamic screen too. The I performed the clear site as described in the upgrade docs which also worked.Beta Was this translation helpful? Give feedback.
All reactions