Debugging of a custom module(code) which basically works (computed field module based)

A programmer has made some modifications on a content type (CCK) so that images are fetched from a remote web site and are stored into calculated fields ([url removed, login to view]) with PHP. The parsing og the remote html is done with the simplehtmldom module ([url removed, login to view]) but i guess you don't have to care for this because the module basically works as it should so the "main program syntax" ,ust be okay.

This means: The images are saved and the node can be viewed, but after some time those images disappear. There is a wring image source then stored in the field. It is a directory then instead of an image ressource.

I have no Idea why it happens and when it happens. It does not seem to be related to cron runs, but it I am not 100% sure.

There are 9 fields that contain this code snippet to be automatically (re)calculated. One of those fields holds the collection of the images that disappear. So the task is to debug the code of this field(s). The strange thing: some nodes do not lose the images although they are of the same content [url removed, login to view] can't recogniza any pattern or dependency. It happens like random. It does not seem to be related to a cron run or anything else. Even old revisions do not show the right content when the images are gone. So the field update must happen directly in the database and not via a drupal compliant way I guess...

Best thing would maybe be some sort of "listener" that dumps the field information each minute into a file to first of all enclose the time when the strange thing happens,......? Maybe you have a better idea.... It is obviously a small bug with big consequences and very unpleasant symptopms for me.....

The task is: Make sure that the data / content / value of the content type is stable and does not disappear....

Maybe its a small bug and done in some minutes.....

Maybe it needs more time to test and investigate.....

What I know is that the module is not large (not many lines of code).....

This has to be done in a drupal compliant manner to make sure that it does not happen again.......

Drupal MySQL PHP

Projekt-ID: #2541641

Über das Projekt