Fórum
6.2 - Can't sort or filter web content in display portlet picker on Oracle
Michael Hartman, modificado 9 Anos atrás.
6.2 - Can't sort or filter web content in display portlet picker on Oracle
New Member Postagens: 24 Data de Entrada: 26/04/13 Postagens Recentes
After upgrading to 6.2 we found that we could not sort or display web content in either the control panel or the web content display portlet. Attempting to do so just threw an ORA-00918 error in the logs. See LPS-43952, LPS-46701.
We applied the fix mentioned in the first comment on LPS-45113 and it fixed most of the issues. Sorting and filtering now works in the control panel. It still does not work in the web content display portlet, but it doesn't throw the ORA-00918 errors anymore either. It generates no log output at all, it just returns no results.
This is going to be a problem for us. We have a lot of web content, and it's not going to be practical for our business users to just page through it all every time they want to change out the content of a web content display portlet. They need to be able to search.
Does anyone have any idea what the problem could be? Why would the display portlet not be using the same SQL as the control panel? It seems like it must be using the same basic finder functionality since the SQL fix we applied did at least make the exception disappear.
We applied the fix mentioned in the first comment on LPS-45113 and it fixed most of the issues. Sorting and filtering now works in the control panel. It still does not work in the web content display portlet, but it doesn't throw the ORA-00918 errors anymore either. It generates no log output at all, it just returns no results.
This is going to be a problem for us. We have a lot of web content, and it's not going to be practical for our business users to just page through it all every time they want to change out the content of a web content display portlet. They need to be able to search.
Does anyone have any idea what the problem could be? Why would the display portlet not be using the same SQL as the control panel? It seems like it must be using the same basic finder functionality since the SQL fix we applied did at least make the exception disappear.