Hi,

Sorry if this is not the correct place to ask this. I made a search in these forums, but could not find an answer to this problem. I have a Drupal 7.14 site with a role for an author and its permissions. So, only one user in this role is obtaining access and permission to publish a content without approval, while the normal workflow would be to post a content (without being able to publish it) and wait for an admin user to approve it. The users with author role are not able to see and change the publish settings. The default content type settings is "not published". So, something unusual is happening. Unfortunately, it happened before the latest entries in Drupal logs, so I cannot see how this thing happened. Have anyone had an experience like this?

Comments

VM’s picture

per: https://www.drupal.org/node/643758 please edit the opening post and move it to the 'post installation' forum. Thank you.

Based on the version of Drupal is use the site has likely been hacked. Using google, search 'drupalgeddon' read and rebuild your site.

amarcanth’s picture

Hi,

Thanks for your answer. Sorry it took me a while to answer back. Well, I have applied the patch in /includes/database/database.inc file as mentioned here. Indeed, there are some more details to add. My fault... The user who published his content is a registered user so there would be no reason to force a login to publish a content. IMHO, a cracker would publish any kind of ofensive content or damage to the site, to show-off, which did not happen. Apparently, this seems more like a bug or something I cannot reproduce even with different browsers and operating systems. Although the site could have been compromised, this doesn´t seem to be the case here. Files are ok, database seems to be ok, nothing uncommon... Any ideas?

VM’s picture

no more ideas. I can't reproduce on a new installation. If you find a method which produces steps to reproduce on a new install please make them known.

amarcanth’s picture

Hi, thanks for answering. Yes, if I find a way to reproduce this error on a new installation, I will make them know.