Timeline for How to find which module is causing PHP warning
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 9, 2018 at 15:47 | comment | added | TBJ | Pierre Vriens: I posted a question on StackOverflow and ended up answering my own question. If you use WAMP it could help to get the settings right. Begin by downloading the php-debug package for Atom. here is the link for the question: stackoverflow.com/questions/48109871/… | |
| Feb 9, 2018 at 14:48 | comment | added | Pierre.Vriens | @TBJ merci for the feedback. If you ever find the time, maybe try to replace that field collection entirely with the paragraphs module (if you succeed, the msg might disappear also ...). PS: "integrating xdebug with Atom", sounds interesting (any links to suggest to get started with that?). | |
| Feb 9, 2018 at 14:37 | comment | added | TBJ | Pierre Vriens: No, I am up to my neck in work, so meanwhile I just keep an eye on the log messages. I did succeed in integrating Xdebug with Atom though, and I am pretty sure it's the Field Collection module that is the cause of the messages. I will post an issue with them... thakns for cheking in! | |
| Feb 8, 2018 at 13:20 | comment | added | Pierre.Vriens | @TBJ any other updates? Did you get it sorted out? | |
| Jan 5, 2018 at 7:08 | comment | added | TBJ | Yes, you are right. But I thought of this solution as a last resort. I will try to get Xdebug to work with Atom first, since it can come in handy som other time as well. Thanks for your answer all the same. | |
| Jan 4, 2018 at 21:01 | history | answered | Pierre.Vriens | CC BY-SA 3.0 |