Welcome Guest, Not a member yet? Register   Sign In
Upgrade from 4.2.10 to 4.2.12
#1

(This post was last modified: 01-09-2023, 10:08 AM by serialkiller.)

I ran the update with composer and everything went fine, then I went to see the various files that need to be updated, and I updated them, having also updated the composer.json file, I ran a second composer update, from nothing works here anymore, i made a copy, so i can go back, but i don't understand why this happens.
Reply
#2

(This post was last modified: 01-09-2023, 12:42 PM by captain-sensible. Edit Reason: added text )

i'm still on 4.2.10 but noted "BREAKING CHANGE" here : https://codeigniter.com/user_guide/insta..._4211.html


https://github.com/codeigniter4/CodeIgni...ANGELOG.md

So sometimes you need to update things; one i remotely remember ( & i don't remember much lol ) was to drag new index.php to be found lurking in /srv/http/webDevDirName/vendor/codeigniter4/framework/public , to web root public dir
CMS CI4     I use Arch Linux by the way 

Reply
#3

(01-09-2023, 10:08 AM)serialkiller Wrote: I ran a second composer update, from nothing works here anymore

What did you get exactly?

What do you mean by "nothing works"?
Reply
#4

(01-09-2023, 05:07 PM)kenjis Wrote:
(01-09-2023, 10:08 AM)serialkiller Wrote: I ran a second composer update, from nothing works here anymore

What did you get exactly?

What do you mean by "nothing works"?

I ran composer update and went from version 4.2.10 to version 4.2.12.
Once this was done I looked at what the changes were in the two versions, reading the documentation I checked and updated the files that have undergone changes in the project space.
As reported in the documentation, most of them were just formatting or changes you have comments, among these files the composer.json file is also listed, so I also updated this and subsequently re-ran composer update, after this I find a blank page and the files in the vendor folder are different and as a result nothing works.
I then tried to instantiate a new structure with composer, just to see if the composer.json file had changed, and it actually remained what it was before.

So, either I didn't understand, and therefore the composer.json file shouldn't be updated with the one in the vendor folder, as for all the other files listed, or I don't know.
Among other things, now I see that there is a new update with several files to be updated outside the system folder
Reply
#5

Did you copy vendor/codeigniter4/framework/composer.json to composer.json in your project root ?
vendor/codeigniter4/framework/composer.json is composer.json for the framework, not your app.
Please don't do.

If you update your project composer.json, check the latest composer.json in https://github.com/codeigniter4/appstarter
Basically your composer.json is yours. You need to update when you really need.

I recommend you learn how to use Composer. Because it is industrial standard package system.
Reply
#6

(01-10-2023, 04:24 AM)kenjis Wrote: Did you copy vendor/codeigniter4/framework/composer.json to composer.json in your project root ?
vendor/codeigniter4/framework/composer.json is composer.json for the framework, not your app.
Please don't do.

If you update your project composer.json, check the latest composer.json in https://github.com/codeigniter4/appstarter
Basically your composer.json is yours. You need to update when you really need.

I recommend you learn how to use Composer. Because it is industrial standard package system.

OK, I found the reason I didn't see in composer.json an http was changed to https in the "support" root, I thought other changes had been made as in the other files listed and by my mistake I didn't compare the files because they seemed the same to me, everything else is clear, sorry for the confusion
Reply




Theme © iAndrew 2016 - Forum software by © MyBB