Greetings. I am very new to Drupal, and am in the process of helping our web librarian set up an Extensible Catalog instance for our library. See http://drupal.org/project/xc
If I have posted in the wrong place, please let me know.
Our test instance is Drupal 6.26, running on PHP Version 5.3.10-1ubuntu3.4 under Ubuntu 12.04.
It lives on an Ubuntu KVM guest within another Ubuntu 12.04 host.
Our current site is hosted using Plone/Zope. The primary reason for migrating to Drupal 6 is the existence of the eXtensible Catalog (XC) Drupal Toolkit.
For the most part, I take care of the server-side and she administers the content, so I only know a little about the design workflow, what I have seen her do, basically.
She reports that some nodes do not stay published. She says she cannot perceive any pattern as to which ones revert to unpublished or what causes it. At first, I suspected the cron job might be involved, but testing doesn't bear that out so far. Then I found a vaguely similar situation in http://drupal.org/node/634002 where the hardened PHP extension suhosin needed to have permitted file limits increased. But, for one thing, there were no file uploads made to the affected nodes, and for another, no suhosin parameters appear in any of the php.ini files in /etc/php5/ apache2, cgi or cli directories . I hesitated to add them because, while I suspected they need to be in the apache2 php.ini, I wanted to make sure first. Is this correct?
In the process of looking for answers I came across http://drupal.org/node/423478 which refers to FileField issues, which caught my eye because we do have it enabled for CCK, but again this seems to only affect nodes with uploaded files.
I'm at a loss how to proceed diagnosing this behavior. Does anyone have some ideas for things for me to read up on or check?
Thanks very much for your help,
Doug Simmons
SIUC
Comments
As part of the
As part of the troubleshooting process, you may want to send an email (or change it to trigger a log message) when a node is unpublished. This will help you determine when & how often the unpublishing is occurring, which may help you match it to what behavior is triggering the unpublish.
Information on how to do this is here
You can alter the process to provide additional information as well. Hopefully, the logs and/or emails will narrow down the cause of the problem.
thanks for your help. I
thanks for your help. I looked to see if there were any rules governing timing publication of content, but I don't think we have any rules at all. At least, I couldn't find anything under admin/build/trigger/node or admin/settings/actions but are these the right places to look? I looked in the log entries and I see where I ran the cron job manually (which is what I suspect triggers the unpublishing events, though it doesn't seem to happen every time) and then at the top of the snippet I see where I tried to hit the page from another browser and got the unexpected page not found, but nothing in the middle - would the change of state show up in this log? Oh and incidentally, the distance from when cron was last run in this log is completely bogus...
Thank you very much for helping me figure this out,
Doug Simmons
SIUC
access denied Dec 19 2012 - 12:32pm node/117 Anonymous
page not found Dec 19 2012 - 12:32pm sites/all/themes/siuchorizontal/css/arrow-right.png admin
page not found Dec 19 2012 - 12:32pm xc-1.1-test/sites/all/themes/siuchorizontal/css/bloc ... admin
page not found Dec 19 2012 - 12:32pm xc-1.1-test/sites/all/themes/siuchorizontal/css/bloc ... admin
page not found Dec 19 2012 - 12:31pm xc-1.1-test/sites/all/themes/siuchorizontal/css/bloc ... admin
page not found Dec 19 2012 - 12:31pm xc-1.1-test/sites/all/themes/siuchorizontal/css/bloc ... admin
cron Dec 19 2012 - 12:29pm Cron run completed. admin
harvester Dec 19 2012 - 12:29pm Distance from last ran of cron is 372 days 21:49:41 admin 12:29:11.590 oaiharvester.batch.inc:27 (oaiharvester_cron())
harvester Dec 19 2012 - 12:29pm cron started admin 12:29:11.588 oaiharvester.batch.inc:15 (oaiharvester_cron())
In this case you'd be
In this case you'd be creating a new rule to help track down the issue. In rules, do the following:
-create one that responds to the event: "After updating existing content"
- In "Conditions", choose "content is published", then enable the "Negate" checkbox so it response to unpublishing
- In "Actions", add a "Send Mail" action.
- In the settings for "Send Mail" you can include a wide range of data in the email. If you have the Token module installed, you can easily include the time the node was unpublished, the title of the node, the logged in user that triggered the unpublish, and all sorts of additional data.
The data in these emails may help you narrow down what behavior is triggering the unpublishing, and serves as a way of notifying you when the problem has occurred.
Thank you for your help. I am
Thank you for your help. I am embarrassed to say that I discovered I had to install the Rules and Tokens modules in order to even try your suggestion. No wonder I could not find these controls.
I have created a rule set for (NOT "when unchanged content is published" -> send email to arbitrary address) which oddly is triggered when unchanged content is published, so of course I removed the negation chekmark and now I get no notification at all. I may not be reading your instructions correctly? In any case, it seems that content that I, as admin, publish is able to survive a cron job run, but content published by others does not and ends up unpublished again. Which makes me wonder if the cron job is not running as the right user, as in this thread: http://drupal.org/node/1450672 - is this even relevant to my situation?
Thank you so much!
automagically fixed?
I wish I knew why this problem seems to have suddenly resolved itself. The only difference between the drupal instance now and the drupal instance before is that I installed the Rules and Tokens modules. But immediately after installation, when I first reran this test, the system was still un-publishing content upon cron job execution. All attempts to reproduce the problem since I checked back in here at the forum have failed. Which is to say, my content has stayed published. Sigh. Is there any reason to think that the update process I initiated while installing these two new modules could have had some effect which would have fixed this behavior?
Just curious. Color Me Baffled.