Moved Postings disappear after updating core or rebuild permissions
| Project: | Forum Access |
| Version: | 6.x-1.0-beta2 |
| Component: | Miscellaneous |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Hello,
i really hope that the very good Forum Access Module is responsible at all but i have no other clue.
After every core update (6.9 to 6.10 i.e.) i need to rebuild the content permissions what brings a negative side effect to
my advanced Forum content.
All Topics which have been moved form a Forum only "auth. users" can read to a forum "Guest Users" can read are gone for Guests.
When user #1 goes to edit-save it appears again for guests. The posts have been moved month ago by just edit and save into another
forum container.
I already try to to find a "key" within the sql table which still points these posts to a different forum than they are actually saved in but no success.
Can anyone help??
i hope my explanation is clear enough - english is not my mother tongue
thanks
#1
Please follow the directions that were displayed when you posted your issue.
Report the DNA information displayed before and after each step.
#2
Okay. ive done that so far exept that i don't get any DNA results below my forum posting which is still invisible.
But the node_access/summary page told me whats wrong and i am a big step ahead (because of you!! thnx)
Summary:
Legacy Nodes
You have 21 nodes in your node table which are not represented in your node_access table. If you have an access control module installed, these nodes may be hidden from all users. This could be caused by publishing nodes before enabling the access control module. If this is the case, manually updating each node should add it to the node_access table and fix the problem.
i think that might be it...
can somebody tell me how to:
manually updating each node should add it to the node_access table and fix the problem.
also, the "21" is supposed to be a link, but the path it is pointing is wrong
thanks so far
#3
You're not getting the DNA results because the user doesn't see the node, right? Well, the essential parts of the information are independent of the user, so you can gather them with user 1.
"Manually updating each node" means edit and save (without making any actual changes).
But rebuilding permissions should do the same thing, except you're saying that it actually breaks things. This has me puzzled. If rebuilding permissions doesn't work, then your site is not working correctly, and this needs to be fixed.
Please update to the -dev version of FA and try rebuilding permissions again. If it still doesn't work right, then post DNA output for one node (using user 1) before and after manually resaving (and presumably fixing) the node.
#4
(lets call it stage 1) before:
Node Prio Status Bereich gid Anzeigen Aktualisieren Löschen erklärt
307 0 leer acl 0 0 0 0 25: forum_access/57
307 0 Fehlt forum_access 1 1 0 0 Gast
307 0 Fehlt forum_access 2 1′ 0 0 Authentifizierter Benutzer
307 0 leer forum_access 3 0 0 0 Administration
307 0 Fehlt forum_access 4 0 1 1 Moderator
307 0 leer forum_access 5 0 0 0 Full Member
307 0 leer forum_access 6 0 0 0 Stammspieler
(Fehlt = missing)
(lets call it stage 2) after manually saving:
Node Prio Status Bereich gid Anzeigen Aktualisieren Löschen erklärt
307 0 leer acl 0 0 0 0 25: forum_access/57
307 0 OK forum_access 1 1 0 0 Gast
307 0 OK forum_access 2 1′ 0 0 Authentifizierter Benutzer
307 0 leer forum_access 3 0 0 0 Administration
307 0 OK forum_access 4 0 1 1 Moderator
307 0 leer forum_access 5 0 0 0 Full Member
307 0 leer forum_access 6 0 0 0 Stammspieler
well salvis, before upgrading to the -dev, rebuilding the permissions used to reset stage 2 back to stage 1.
I played that game for the core upgrades since 6.4. After every upgrade, i rebuilt the permissions and certain
nodes disappeared. Now, after manually saving, it sets status "missing" to "OK" AND after a permission rebuild it REMAINS AT STAGE 2!! Yeeahhhh
So for NOW it looks very promising to me. As soon as i upgrade to the upcoming core i will let you know!
PS:
i didnt get any DNA results because i missed enabling the devel-block...me stupid...
thanks so far:)
#5
Ah, very good, thanks for letting us know!
#6
BETA4 is out, which should fix this. Please reopen the issue if it doesn't.
#7
Automatically closed -- issue fixed for 2 weeks with no activity.