-
Notifications
You must be signed in to change notification settings - Fork 1
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
Catalog contains no sources #233
Comments
I confirm that this is the case. Nothing was apparently upgraded on frontend, but this functionality stopped working. There are some errors in JS. Could you check @burnout87 , @motame ? |
the link does not work, how can I reproduce it? just any request ? |
why? probably some permissions missing? What is needed to view this submission, @motame ?
Yes. Try with the default. |
ok iI can see it now, just rushed in replying |
I did some testing locally as well as on the production. It's weird but it works properly locally. The So I suspect that that object (built on the backend side, PHP, to hold some configuration and settings, and read on the frontend side, javascript) is built with n older approach but read with a newer one, causing the issue. Did the way the |
I confirm that it's working properly on dev instance. |
And then why the |
I suppose on dev instance you have a recent version of the code? |
Yes, the latest one but as mentioned above, this part of the code did not change from a while (~2 years) |
Locally I am also testing with the latest one |
The version in the production frontend did not change since a while. Is there a way to know reasonably easily why it broke? |
In both places it's in fact an array indexed by the instrument short name. However on prod, the array is indexed by numeric values (0,1,2 ...) !! |
That object is built in the backend starting from the
mmoda-frontend-module/mmoda.module Lines 362 to 363 in dc104ff
Where is that variable loaded? |
It's an object storing all mmoda config, core and modules. |
May be reinstalling the modules will fix the issue.
In addition to that the "drush pmu" command should respect the module dependency. |
I uninstalled and re-installed all modules. Does this log look right?
But it still does not help. |
https://www.astro.unige.ch/mmoda/node/383/submission/147
reported by @jywoo0116
The text was updated successfully, but these errors were encountered: