Ansel gets weird notice error but only on certain pages
Hi there. After upgrading EE from 3.5.11 to 3.5.15, and additionally upgrading Ansel from (I think) 2.11, we are getting a PHP Notice level error on some pages. It’s weird because none of the content has changed at all, only the versions of addons. Here’s a screenshot:
Hi Adrienne. That is weird that the error only started showing up after updating Ansel and EE for those minor version bumps. I don’t see any changes in Ansel between, 2.1.1 and 2.1.4 that would cause that error to pop up.
Line 129 is getting the file extension from a
pathinfo call. It’s probably not great that I’m assuming the file will have an extension, but I think more important is to find out why this file doesn’t have an extension (or why the path does not by the time it reaches this method call).
Do you think it might be possible to get me a stack trace so I can follow the path back through this particular request? In the mean time in any event, I’ll do some testing as soon as I can to see if I can figure out a way in which an extensionless file’s path could make it’s way into that method call.
March 29, 2018, 2:28 pm
I’ll see if i can get it for you!
March 30, 2018, 12:03 am
Your account with the old support system does not carry over to the new support system. The new system is all tied together and connected with your account for purchasing and licenses. If you have a license, you have an account and you can log in with that email address and password. If you have not set a new password yet, you can do so with the forgot password link. Very sorry for any inconvenience.