The visibility rules are not being saved for panes either in pages content nor in mini panels.
However, they work fine for "selection rules" and "access control".

I made a custom plugin as recommended in this thread: #453882: Block Visibility. Same thing happens. (By the way, thank you very much on that issue, the two times I asked for help here the answer was excellent)

Things are the same both on a local test machine with wamp and a server.

There are no errors or warnings. The visibility rules just disappear when saving the changes.

Thank you.

Comments

Sancho Panza’s picture

Title: Visibility Rules » Visibility Rules not Saved
Sancho Panza’s picture

Please, disregards by now. I have two sites running the same code.
In the one with problems I just updated the database from alpha4 to beta1.
In the other one, I unistalled panels and ctools, and installed again and things are working properly.
I will uninstall, rebuild the pages and if it works will post it here to close the issue.

merlinofchaos’s picture

Interesting. Even if it works ok with a fresh install this *could* indicate an issue with the upgrade path (the 'access' field did change!) so it is worth taking a second look at if an upgraded site can't save access control on panes.

Sancho Panza’s picture

I have finished the update and everything is working fine. The visibility setting are being saved correctly.

What I did to make it work was

1) Unistalled everything (panels and ctools)
2) Deleted two remaining tables manually in the database: panels_object_cache and panels_page_router_store.
3) Installed the modules again and rebuilt the panels and mini_panels

Again, thank you very much for the support.

pixelpreview@gmail.com’s picture

yes same issue for me
I will do the same than sancho
clean all and install the modules ctools and panels

dawehner’s picture

did you enabled clean urls?

i had the same problem when i disabled clean urls.

Sancho Panza’s picture

Derein:
Yes, the site has clean urls enabled.

Pixel:
Regarding what I did, I must tell that I am not an expert in Drupal, nor nothing near that. I am posting so someone more knowledgeable can provide a better insight.

So if you are going to do the same as me, please consider at least backing up everything.

pixelpreview@gmail.com’s picture

thanks sancho,

I have uninstalled all modules (ctools, delegator, panels, views panes...) and after i must destroy two tables like you in your post
after i have enabled all modules and it works fine
it seems that my passage from the version 2 to the version 3 was not perfectly done :-)

great work merlin, it's more easy now for choose a view or a menu ... and i like very much the previsualisation !

thanks

merlinofchaos’s picture

I think a fix I just checked into the update path fixed this. At least, I can't replicate it on a donated site I updated.

rfay’s picture

Version: 6.x-3.0-beta1 » 6.x-3.0-beta2

I can confirm that this is still an issue in 6.x-3.0-beta2 when upgrading from 6.x-3.0-beta1. I tried also a fresh upgrade from 6.x-3.0-beta1 to 6.x-3.0-dev (2009-Jun-14) and got the same results. So this remains an issue on the upgrade path.

I went through the export, uninstall, delete tables, reinstall, import dance in #4 and the fix works.

I can provide a complete db dump and file install for debugging if you want one. It's pretty easy to demonstrate. Just let me know.

rfay’s picture

Title: Visibility Rules not Saved » Visibility Rules not Saved after upgrade from 6.x-3.0-beta1; re-import required
merlinofchaos’s picture

Status: Active » Postponed (maintainer needs more info)

rfay: Could you provide that please? If i have to install beta1 and create some stuff and update it that could take awhile.

rfay’s picture

merlinofchaos: I have it staged for your eyes only. Just catch me on IRC or I can email you the details, whatever you'd like. The database dump is not sanitized, so I can't put it here for all to see. The administrators of the d.o. might not like me either.

merlinofchaos’s picture

Status: Postponed (maintainer needs more info) » Closed (won't fix)

Ok, the problem here is one I can't fix. But you can.

What happened with rfay's database, and I presume this happened with other people's as well, is that you updated to Panels 3 from Panels 2 at a time when the update process wasn't working well. At beta1 you were well past that, but an important Panels update never ran.

With rfay's database, and I presume with others, you can geta round this by visiting update.php and going back to Panels update 6290 which will properly update the database.

merlinofchaos’s picture

Thanks for the database, rfay, so I could figure out what was happening here.