panel visibility not being saved
ultimike - December 9, 2009 - 19:19
| Project: | OG Panels |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
I believe I've found a bug with pane visibility not being saved when working with an Organic Groups panel.
Here's how to reproduce the bug (using the 2009-Sep-05 dev release with Panels 3.2):
1. Create an OG Panel
2. Add a block
3. Add a new visibility rule (I used a role-based one)
4. After you hit "save" on the popup window, but before you hit "save" on the panel, click the popup menu for the block and you'll see that your rule was added.
5. Save the panel
6. Click "edit content" to go back to the panel editor.
7. See that your rule was never saved.
The visibility settings work fine on non-OG Panel pages on the same site.
Thanks in advance,
-mike
#1
Hi Mike,
I tried your steps but found that the visibility works fine for me.
What I did is:
1. Create an og_panel
2. Click on edit content, add a block, and then select a role-based visibility rule.
3. Save the panel.
When I come back , click on edit content and it works for me.
I will do further testing.
Best regards,
Jim
#2
Jim,
Thanks for the quick reply - I'll give it a shot on a clean site and see what I find...
-mike
#3
I don't think og_panels is particularly involved in that particular piece of code either, so this is almost certainly a bug in Panels itself. THere is already an issue for it, though last I checked I thought we had it all straightened out in the latest versions.
#4
I went ahead and tested it on a clean install and it worked fine, which means that something odd is going on with my particular site.
I just updated the site with the latest Drupal core and module releases.
Any thoughts on where I should start looking? Are there any types of modules that I should try disabling to see if they're interfering?
Things I've already tried:
- switched the theme to garland
- tested it on a new, empty group within the application
- installed the latest 6.x-3.x-dev version (2009-Dec-16) of Panels
-mike
#5
I solved the issue with some help from this thread.
Here's exactly what I did:
1. Backup my DB
2. login as the admin (UID=1) user
3. went to update.php
4. selected and ran Panels update 6290
That's it! It appears that as part of running Panels update 6290, Drupal actually goes back and runs not only 6290, but all the updates after 6290 to get everything up-to-date.
-mike