I posted about this issue before a few weeks ago, but unfortunately I still have not been able to find a solution.

Here is my web site: http://www.loveacrossborders.com

Anyone can register an account and post their poems. For some bizarre reason new poem nodes stopped being promoted to the front page after the poem I posted about a month ago.

Here is what I've done to try to fix the issue:
I have checked under "Content types" to make sure that "Default options: >> Promoted to front page" is checked. It is. I have double checked to make sure all nodes are published. They are. I have gone through my modules to try to find if one of the modules could be causing this problem. No problems as far as I can tell. I have turned the page and CSS cache OFF.

When I go to edit a node and go to "Publishing options >> Promoted to front page" I see that the box is unchecked. I try checking the box and then hit "Submit". I'm logged in as administrator, however, every time I do that then the page refreshes, but the "Promoted to front page" box is unchecked again.

*sigh*

I can't understand why nodes suddenly stopped showing up to the front page a month ago for no apparent reason. I've been working on and off with Drupal for more than three years, so I don't think I'm a total noob. Does anyone has any suggestion (whether simple or complex) that may help clear up this issue?

Comments

enthusaroo’s picture

*bump*

Please...

moazam’s picture

I just had a similar thing happen to my site. I turned off 'Page Cache' in 'Home » administer » Settings' and it seems to have updated front-page with new content. I have my page cache set to 1 hour, so I assume that if I leave the page cache turned on, after about 1 hour unauthenticated users should be able to see the content.

enthusaroo’s picture

Yeah, I tried disabling the cache, but a month later and the new content is still not showing up for anonymous users. I'm at my wits end here. To be honest, I'm a few days away from just scraping the whole thing and giving up.

:(

enthusaroo’s picture

I found the solution...

Access Control >> Anonymous User >> "Administer Nodes" must must be checked, although I can't understand why.... but at least my site finally appears normal again for anonymous users! Hope this helps someone else who runs into a similar problem down the line...

enthusaroo’s picture

I found the solution...

Access Control >> Anonymous User >> "Administer Nodes" must must be checked, although I can't understand why.... but at least my site finally appears normal again for anonymous users! Hope this helps someone else who runs into a similar problem down the line...

enthusaroo’s picture

I found the solution...

Access Control >> Anonymous User >> "Administer Nodes" must must be checked, although I can't understand why.... but at least my site finally appears normal again for anonymous users! Hope this helps someone else who runs into a similar problem down the line...

vm’s picture

If you do that, anon users will indeed be able to administer nodes, which means any users on your site can edit and delete nodes, i believe.

May have been beneficial to clear your cache tables in the DB to see if that fixes the problem. There is also a snippet in the handbook that allows you to clear cache tables, but I prefer using the devel.module which gives user1 the ability to clear the cache tables with a button in the admin area.

Keep in mind that anon user pages are cached regardless of page cache settings from what I understand.
_____________________________________________________________________________________________
give a person a fish and you feed them for a day but ... teach a person to fish and you feed them for a lifetime

mindyblock’s picture

I've got the problem too. Giving admin node permission clears it up, but I see we were warned not to do this. So I emptied the cache just the cache. Did nothing. What can I do?

Mindy Block

vm’s picture

are you using any other user access modules ? or have you removed any ?
Organic Groups as an example ?

when you goto administer -> posts settings

is there a note at the top stating that your node access table may not be correct ? with a button to fix it ?

Keep in mind that on a default install, there is no button there, it only shows if the node access table is altered. If it is altered, do you know which module has altered it ?

_________________________________________________________________________
This has been a broadcast of the public Drupal Search system. We thank you for watching! : )

mindyblock’s picture

I did install Organic Groups and tested it very briefly, found it too complicated and then removed it. I did notice in the post setting something about rebuilding nodes. I did this and nothing happened.

But then, I started copying the information in a node to a new node to publish it. I did this about three time on nodes in one book and it seemed to have gotten rid of some bad node pointer (what I guess it was). Because all of a sudden the problem cleared. That is anonymous users could gain access to each fixed node starting with the children first and when that cleared the main book page. And when that cleared I got the main page - node 1 back.

This is the best I can do to explain. I have only been using Drupal for a few weeks. But I do have a background in computers....

vm’s picture

does not sound like OG was uninstalled properly.

what I don't understand now is, is your problem fixed ?

in future you test modules on a test site, either on your local machine or in a subdomain of your server. Doing so protects your production environment from this kind of situation.

inspect this documentation see: http://drupal.org/node/64114

run those querries on your node table and see if proper access returns.
_________________________________________________________________________
This has been a broadcast of the public Drupal Search system. We thank you for watching! : )