Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2.1.9 upgrade, Projects module shows the number of projects in filter tabs, but "No projects available" to view #56

Open
cleary opened this Issue Feb 27, 2019 · 6 comments

Comments

Projects
None yet
2 participants
@cleary
Copy link

cleary commented Feb 27, 2019

Hi Adam,
I'm testing the upgrade to v2.1.9 - for all our non-admin users, they are no longer able to get a listing of projects in the Projects module:

screenshot_20190227_110330

The filter tabs indicate correctly how many should be visible.

The permissions/roles haven't changed since our 2.1.8 deployment, and look like this (for this particular example):
screenshot_20190227_110509

screenshot_20190227_110536

The Project Worker role looks like:
screenshot_20190227_110812

Is there something I'm missing that's changed in the role?

@ajdonnison

This comment has been minimized.

Copy link
Contributor

ajdonnison commented Feb 27, 2019

@cleary

This comment has been minimized.

Copy link
Author

cleary commented Feb 27, 2019

This is using the docker container config I talked to you about earlier, and pulls the master branch as is - none of the performance enhancements we worked on were included.

@cleary

This comment has been minimized.

Copy link
Author

cleary commented Mar 6, 2019

Hi Adam,
The plot thickens, during the export/import testing I discovered that this is not related to 2.1.9 specifically, it's also affecting the v2.1.8 tag code -
I guess that implies theres a dependency potentially missing, or a bug in the Centos packages I'm using (same as in the docker-compose bundle I sent previously)

@ajdonnison

This comment has been minimized.

Copy link
Contributor

ajdonnison commented Mar 6, 2019

So there was an export and import that caused this? It sounds very much like the permissions cache hasn't come across cleanly. In the change from 2.1.3 to 2.1.4 there was a change to speed up permissions handling by creating a permissions cache table and populating it from the phpgacl tables. If you look at db/upgrade_213_to_214.sql you'll see how it was doing that. It may be you need to run a similar query to re-populate the cache.

@cleary

This comment has been minimized.

Copy link
Author

cleary commented Mar 6, 2019

I just did a mysqldump of our live database (our standard backup procedure) and brought that dump into the new db instance - the dump is completely generic, all tables, no trickery.

I grabbed the sql query you mentioned, replaced the %dbprefix% vars appropriately and ran it against my db. I had to re-login, but the issue is still there

@cleary

This comment has been minimized.

Copy link
Author

cleary commented Mar 15, 2019

Hi Adam,
I did a little more attempted debugging today, devel branch using ubuntu 18.04/php 7.2 instead of CentOS - same symptoms.

I've also tried using the official MySQL docker images - 8.0 and 5.7 had compatibility issues, but 5.5 connected, but still exhibited the same issue -

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.