Leaderboard

I was able to resolve my issue by having made a new working directory, since whatever it was making the errors appear was ousted upon a new instance. So first I removed the old file I was working in, which had this anomaly. Then when working in the new one, the error came back. Thanks to paying attention where Stef explains what the underscore does I was able to realize that whatever was being done was pointing to specific directory/files, depending on if you are working on it or not. So to fix it I re-ininitialized that pointed file so whatever is being done there is stuck there so then I could work without those errors telling me I'm wrong but then the code runs. So I had to fix this because if I deploy a PHP site and that could happen, then I would be very concerned if I were running a business. I was thinking maybe have a method that had a bucket that traps prototype pollution; not to say that all of those are bad, that's how social-media fetches data for ad-campaigns. The concern is the potential for malicious activity to hide in the mix, that could range out to anything. Given the nature of the cyber world, that is a rational concern to have, in my opinion. I do hope this helps anyone encountering the same and/or similar issue! Have a great day everyone!