PHRETS icon indicating copy to clipboard operation
PHRETS copied to clipboard

Fatal error: Uncaught Error: Call to undefined function array_get()

Open beycome opened this issue 6 years ago • 5 comments

Hey, my scripts were working fine but I start having this error few days ago:

"Fatal error: Uncaught Error: Call to undefined function array_get() in /.../vendor/troydavisson/phrets/src/Models/Metadata/Base.php:50 Stack trace: #0 /.../cronTask/mls_rets_egyp.php(46): PHRETS\Models\Metadata\Base->__call('getsystemdescri...', Array) #1 {main} thrown in /.../vendor/troydavisson/phrets/src/Models/Metadata/Base.php on line 50"

My environment is the following: nginx server, ubuntu, php 7.2.19, phrets 2.6 The error looks like is in one of the dependency installed "illuminate" there is the method "array_get" and for reason phrets can't see it. I can't find anything related with this error, I will really appreciate any suggestion about how to fix that problem. Any suggestion will be welcome. Thanks

beycome avatar Sep 19 '19 14:09 beycome

I had the same issue, however this is raised and resolved as per #245

simmonspaul avatar Sep 24 '19 02:09 simmonspaul

Until the PR is merged, use composer require laravel/helpers to pull in all the deprecated helpers to make everything work again.

BrandonSurowiec avatar Oct 02 '19 14:10 BrandonSurowiec

This should be fixed with 2.6.2

troydavisson avatar May 21 '20 00:05 troydavisson

Can you provide more details about where you're seeing this issue with 2.6.2? All references to that function have been removed in preparation for PHP 8.

On Thu, Jul 2, 2020, 1:36 PM Nicholas Maietta [email protected] wrote:

This should be fixed with 2.6.2

It is not.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/troydavisson/PHRETS/issues/247#issuecomment-653136244, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACN32WIB7PWNBHAATAUWHTRZTAMPANCNFSM4IYMEFXA .

troydavisson avatar Jul 03 '20 00:07 troydavisson

I stand corrected. It was fixed alright, but for whatever reason composer kept caching 2.6.1 instead of 2.6.2 even though i referenced 2.6.2 and ran composer update. After trying on a fresh VPS, everything was working again. Sorry to have bothered you on this.

maietta avatar Jul 03 '20 00:07 maietta