-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Solr4 not working after changing enterprise version 5.0.3 #463
Comments
We have just committed the final fix for #461, which should solve the majority of this issue. However, I have tried to reproduce the error you are seeing. I tried creating a 3.0.0 project, set version to 5.0.3.5, and surely enough because of #461 it brought up community edition. However, Solr worked as expected. I also tried overriding my local artifacts to force it to use enterprise, but did not see the issues, no red bars in Share, and verified that tracking works as expected. On top of that I see multiple issues reported in here: Community logo displayed in login: I believe this is a known bug, and I've searched high and low for the JIRA that describes it, but I haven't been able to find it. This has no practical impact, once logged in the footer will display that it is indeed enterprise. This bug is only present in 5.0.x, I have not seen it in 5.1 or 5.2. We are about to release SDK 3.0.1, can I ask that you re-test the Solr issue once 3.0.1 is available? I will give an update here once it's out. |
@ohej Will regress with 3.0.1 and confirm it. |
@ohej I just tested with 3.0.1 and can confirm that no solr issue. Except login screen still shows community but after login dashboard logo all shows Alfresco One. Tried with Alfresco Enterprise 5.0.3.5. |
Closing as this was fixed in #461 |
Ok This issue seems to me a side effect of issue #461.
How to reproduce it
Work around
update web.xml by commenting out the lines by unzipping the war and pack it again keep it in maven local for the sdk to pick it up.
I can confirm it works after doing above step. Hope the fix for issue #461 fixes this issue as well which we should regress.
The text was updated successfully, but these errors were encountered: