I'm running Drupal version 5.1, along with several modules: Organic Groups, CCK, Views, TinyMCE, IMCE, and Advanced Front Page. I'm having a small issue getting revisions to function inside of blogs.
In order to enable revisions by default on blog entries I have gone into Content Types and put a check mark next to the "Create new revision" option of the "Blog Entry" type. Additionally, under the "Access Control" menu, I have a check mark next to "revert revisions" and "view revisions" for the "authenticated users" type.
The above settings seem to work fine as the administrator user, the revision box is checked when I attempt to create a new blog entry and I submit it and a new revision is created. Unfortunately this is not the case when I am logged into my normal user account, it's as if the option is simply being ignored for normal users.
To make matters more interesting, the "Log entry" field is displayed when I'm editing a blog entry as an authenticated user, this indicates to me that the revision setting is being properly acknowledged by the form.
I've also taken a look at the node_revision table on the database itself and verified that revisions are NOT being created. So this is a creation issue of some sort and not a display issue after the fact.
I attempted to get some support on this issue in the forums, but nothing that was suggested cured the matter. It's a small problem, but would be quite helpful if I could get it working properly. Thanks so much for a wonderful product.
Comments
Comment #1
Flu commentedNot sure it's necessarily relevant in this instance, but wanted to add that Drupal 5.1 is running on a Fedora Core 5 server with the following software revisions:
Kernel: 2.6.18-1.2257.fc5
Apache: httpd-2.2.2-1.2
PHP: php-5.1.6-1.2
MySQL: mysql-5.0.27-1.fc5
I've tested the above issue on Internet Explorer, Opera (Linux) and Firefox (Linux & XP) and the same problem occurs on all three browsers. I've also reproduced this issue on two separate themes: Garland and Bluebreeze.
Comment #2
webernet commentedDuplicate of: http://drupal.org/node/114822
Comment #3
Flu commentedThe patch located here: http://drupal.org/node/114822 does appear to resolve this issue for me.
--God speed.