Issues with CE Phoenix v1.0.8.5 Live site

Open to all! Ask other shopowners for help.
Post Reply
LeeFoster
Contributor
Posts: 263
Joined: Sun Feb 28, 2021 9:41 pm
Phoenix Version: v1.0.8.20
Has thanked: 1 time
Been thanked: 5 times

Issues with CE Phoenix v1.0.8.5 Live site

Post by LeeFoster »

I have a live site https://360wargaming.com/ and am having a few issues with it.

First is when I log into the site as a customer and go to the shopping cart I get this error -
error 500.PNG
I can bypass the shopping cart to get to the shipping page but then checkout payment gives the same error.

Second when I go to the customers page and try to edit a customer I get -
customers error.PNG
This only happens on my live site, my locally hosted site works fine. Any ideas what I should be looking for?
You do not have the required permissions to view the files attached to this post.


Join The Code Co-op to get access to your library in the Code Co-op Forum
ecartz
Core Team
Posts: 3084
Joined: Tue Nov 05, 2019 6:02 pm
Phoenix Version:
Has thanked: 4 times
Been thanked: 208 times

Re: Issues with CE Phoenix v1.0.8.5 Live site

Post by ecartz »

A 500 error should have a log entry of some kind.

Two nav bars normally indicates that something is using two incompatible methods of loading the nav bar. But I would concentrate on the catalog side error, as that has more impact.
LeeFoster
Contributor
Posts: 263
Joined: Sun Feb 28, 2021 9:41 pm
Phoenix Version: v1.0.8.20
Has thanked: 1 time
Been thanked: 5 times

Re: Issues with CE Phoenix v1.0.8.5 Live site

Post by LeeFoster »

ecartz wrote: Sun Aug 14, 2022 9:58 am But I would concentrate on the catalog side error, as that has more impact.
Yeah I can live with the other issue for now, any idea where to start looking with this? Only have the issue if something is in the basket
LeeFoster
Contributor
Posts: 263
Joined: Sun Feb 28, 2021 9:41 pm
Phoenix Version: v1.0.8.20
Has thanked: 1 time
Been thanked: 5 times

Re: Issues with CE Phoenix v1.0.8.5 Live site

Post by LeeFoster »

ecartz wrote: Sun Aug 14, 2022 9:58 am A 500 error should have a log entry of some kind.

Two nav bars normally indicates that something is using two incompatible methods of loading the nav bar. But I would concentrate on the catalog side error, as that has more impact.
Fixed the front end error, it was caused by a combination of legacy order total and payment modules that needed to be remove.

No wo fix the customers page issue, I have turned on error reporting and now get this error -
Fatal error: Uncaught TypeError: Argument 2 passed to Form::hide() must be of the type string, null given, called in customers.php on line 56
LeeFoster
Contributor
Posts: 263
Joined: Sun Feb 28, 2021 9:41 pm
Phoenix Version: v1.0.8.20
Has thanked: 1 time
Been thanked: 5 times

Re: Issues with CE Phoenix v1.0.8.5 Live site

Post by LeeFoster »

LeeFoster wrote: Sun Aug 14, 2022 3:30 pm
Fatal error: Uncaught TypeError: Argument 2 passed to Form::hide() must be of the type string, null given, called in customers.php on line 56
Quick search of the forum tells me this is most likely related to the fact I don't set a default address at customer creation so need to figure a way around that.
ecartz
Core Team
Posts: 3084
Joined: Tue Nov 05, 2019 6:02 pm
Phoenix Version:
Has thanked: 4 times
Been thanked: 208 times

Re: Issues with CE Phoenix v1.0.8.5 Live site

Post by ecartz »

LeeFoster wrote: Sun Aug 14, 2022 5:40 pm
LeeFoster wrote: Sun Aug 14, 2022 3:30 pm Fatal error: Uncaught TypeError: Argument 2 passed to Form::hide() must be of the type string, null given, called in customers.php on line 56
Quick search of the forum tells me this is most likely related to the fact I don't set a default address at customer creation so need to figure a way around that.
Try changing line 56 to

Code: Select all

      ->hide('default_address_id', $customer_data->get('default_address_id', $customer_details) ?? '');
The ?? '' is added.

I'm not sure what you mean by "turn on error reporting". You should not be able to turn off error logging of fatals. You should have a way of viewing logs of those errors. You should not need to turn on display_errors to see the errors, as that can leak information.


Join The Code Co-op to get access to your library in the Code Co-op Forum
Post Reply