Main instance changes

RE: Main instance changes

2009-10-09T07:30:21Z

HI

It is actually what I did.

http://issues.liferay.com/browse/LPS-4134?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel

RE: Main instance changes

2009-10-08T19:29:57Z

If you have one, I seriously doubt that anyone will sneer at a bug fix.... Just add your code to the ticket.

RE: Main instance changes

2009-09-29T09:56:51Z

Hi,

I suggested our solution in http://issues.liferay.com/browse/LPS-4134

I don´t know wheter it is the correct proceeding to contribute a solution or not but...

RE: Main instance changes

2009-09-28T19:22:53Z

My personal feeling is that omni-admin ought to be a declared role like Org Owner and not some wierd default thingy that can come unordered.

Main instance changes

2009-09-28T10:09:20Z

Hi There.

I am a bit confused about how to contribute a bug fix and how to communicate bugs. Some months ago I created an issue in the issue tracker:

http://issues.liferay.com/browse/LPS-4134

And answered in the forum about the same issue (forum post)

Now I am dealing with the same problem and I think it is not resolved yet (AFAIK).

Well, the issue is that Liferay considers as main instance, and so its administratos as omniadmin, the first company returned by an SQL like this
...
SELECT company FROM Company company WHERE company.system = true/false

In a beginning it was OK because the companies where selected in the order they where created, but after creating several instances, the order changed and some instances where positioned before the default instance/company.

In the issue I sugested to and add "order by" clause to fix this problem. Another solution, at least for Oracle, could be defining the table "company" as an "index oganized table". But I think I didn´t communicate the issue properly.

Hope This helps to resolve the issue (if not resolved yet) and I will try to find the correct way to communicate bugs and the procedure to collaborate.

best regards,

Aritz Galdos