Our alert is unpublishing every time cron runs. I outputted the time passed (time() - $result->created) to the log output and ended up with a really high number (1282950964 seconds in this case). I'm not really sure why this would be, the code seems correct to me, so maybe the result is being returned wrong?
Comments
Comment #1
kevinquillen commentedI will take a look. At first glance it looks correct but will debug it.
Comment #2
kevinquillen commentedCan you give me some more information about this? What is your time limit set to? I tried to debug this but was not able to replicate.
Comment #3
Anonymous (not verified) commentedMy time limit is 24 hours. We are still in the development stage so we're running cron a lot and clearing the cache a lot, but the unpublishing seems rather random. I can't even really say it is happening every time cron is run but it has certainly consistently unpublished before the 24 hour limit. I'll publish a few more today and see what happens. Hopefully I can find out a little more information for you.
Comment #4
Anonymous (not verified) commentedI've narrowed down what's causing this (for us at least). Any time any content is added or updated on the site, the user alert seems to be unpublished. I think user_alert_nodeapi fires every time any node is updated or inserted. So there should be a check in there for the node type user_alert. The following code seems to work for me.
Comment #5
kevinquillen commentedOkay, I see what you are saying. Makes sense now.
Comment #6
kevinquillen commented#4 added to 6.x-.1.3
Comment #7
Anonymous (not verified) commentedAwesome, sounds great.
However, I downloaded 1.3 and this doesn't seem to have made it in.
Comment #8
kevinquillen commentedYou are right. I added the change last night and tagged the release and created it. Odd.
I am new to CVS on Drupal so I apologize. It has been hit or miss for me.
Comment #9
Anonymous (not verified) commentedNo problem, I think you're doing great. I don't have much experience with CVS either so I can't say I'd be doing much better.
Comment #10
kevinquillen commentedComment #11
kevinquillen commentedIt got included in the release that time.
Comment #12
kevinquillen commented