EcoPets Posted February 5, 2024 Share Posted February 5, 2024 Pshop 8.1.3 -- I am gettting -- trim(): Argument #1 ($string) must be of type string, array given [TypeError 0] when saving changes in some modules. Any ideas what might be causing the issues? Link to comment Share on other sites More sharing options...
Nickz Posted February 5, 2024 Share Posted February 5, 2024 (edited) 2 hours ago, EcoPets said: Pshop 8.1.3 -- I am gettting -- trim(): Argument #1 ($string) must be of type string, array given [TypeError 0] when saving changes in some modules. Any ideas what might be causing the issues? define in which module it thows that error and we are halfway there After a update I presume? Edited February 5, 2024 by Nickz (see edit history) Link to comment Share on other sites More sharing options...
EcoPets Posted February 5, 2024 Author Share Posted February 5, 2024 It happens on some prestashop one and some 3rd party. It is one a clean 8.1.3 install with a 3rd party theme and included modules. I am waiting for the dev to respond, BUT it also happens on some prestashop modules. Link to comment Share on other sites More sharing options...
AddWeb Solution Posted February 6, 2024 Share Posted February 6, 2024 10 hours ago, EcoPets said: Pshop 8.1.3 -- I am gettting -- trim(): Argument #1 ($string) must be of type string, array given [TypeError 0] when saving changes in some modules. Any ideas what might be causing the issues? Hi, Make sure that all the modules and the theme you are using are compatible with Prestashop 8.1.3 and also you are using the latest versions of the modules and the theme. Developers often release updates to address compatibility issues with new Prestashop versions. Thanks! Link to comment Share on other sites More sharing options...
EcoPets Posted February 6, 2024 Author Share Posted February 6, 2024 That is my assumption. The developer has state the module is compatible, BUT 8.1.3 has had some issues even with a clean install, so there is always a chance for some errors or incompatibility. I have sent them the details and am waiting for a response. I posted here because this particular error comes up on other modules from time to time and I wanted to see if anyone else ran into it before. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now