Bug en navegación de espacios en WebCenter Portal : Spaces PS5

Recientemente el blog de A-Team ha publicado información acerca del "bug" de WebCenter Portal : Spaces por el cual las navegaciones tanto de páginas como de espacios parece no funcionar.

Enlace al post de A-TEAM

En este post os quería comentar la solución temporal a dicho "bug" hasta que no se proporcione una solución oficial.

Muchas veces las navegaciones de espacios son implementadas en puro JSTL  + HTML donde el enlace se genera mediante un:

- <af:goLink destination="/webcenter/spaces/yourSpaceName"/>
- <a href="/webcenter/spaces/yourSpaceName"/>

En navegadores como IE 7 e IE8, al cabo de una cierta navegación y por cuestiones de caché de estos navegadores, la navegación deja de funcionar sin poder acceder a los espacios.

¿Cómo solucionar este problema?
Mediante el uso de un <af:commandLink> o componente con actionListener.
La solución lo que hace es ejecutar un Manage Bean del propio API de WebCenter para registrar internamente el espacio al que se navega.

Por lo que el enlace quedaría del siguiente modo:

<af:forEach items="{spaceContext.spacesQuery.unionOf['USER_JOINED'].shape['ROOT_LEVEL'].listSpaces}"
                            var="gsNode">
<af:commandLink partialSubmit="true" immediate="true" actionListener="#{o_w_w_sc_i_v_b_communitySwitcherPopupBean.launchSpace}" text="#{WCTruncator[gsNode.displayName]['25']}" id="gil1">
                                     <f:attribute name="spaceName" value="#{gsNode.name}"/>
</af:commandLink>
</af:forEach>

¿Implicaciones de este cambio?
Los indexadores / crawlers entienden solo de enlaces, una navegación programática como la de la solución puede acarrear problemas para los buscadores.

Comments

Post a Comment

Popular posts from this blog

OJET: Inter-Module communication in TypeScript Template

Image
In this post I bring another example on how to Communicate Modules using the Oracle JET - TypeScript Template based on the Oracle JET Cookbook: InterModule Communication From now and so on will create multiple examples using TypeScript for those who are not familiar with it and wants to turn the Cookbook examples into TypeScript :). The example ( ojet-typescript-list-detail ) can be found as usual in my GitHub repository: https://github.com/DanielMerchan/ojet-examples This example is a bit different compared to the Cookbook example where the modules are not running at the same time within a Module. This example is built as described in the following images: Customers module acts as the Wrapper Module. It coordinates when to load the list and detail modules. Customers module makes use also of signals npm module for communication between Customers-List, Customers-Detail. Explanation of the Example customers.js is the coordinator responsible module for: initiali
Read more

OJET: Build and Deploy in an Application Server

Image
There are some other sources where an Oracle JET Application is packaged and deployed as a WAR in Oracle WebLogic Application Server (Arda Eralp) https://blogs.oracle.com/ardaeralp/deploy-oracle-jet-application-to-weblogic-server (Andrejus Baranovski's) http://andrejusb.blogspot.com/2016/07/serving-oracle-jet-application-from.html They may look bit old or maybe because they call directly grunt tasks by using the grunt-cli . In this post I will update a bit these posts in Oracle JET 6.1.0 and the usage of ojet build (instead of calling the grunt tasks) for also building the corresponding WAR file. The example can be found in my GIT repository: https://github.com/DanielMerchan/ojet-examples Let's start... Install grunt-war module in your Oracle JET Application. npm install grunt-war --save-dev Create a war.js (or call it whatever you want) in /scripts/grunt/config folder under your souce files. This is a sample code inside of it, check https://www.npmjs.com/packag
Read more

OJET: Select All options using only Checkboxset

Image
This is an example on how to select all other options by using another oj-checkboxset. GitHub: ojet-checkbockset-select-all The idea is to keep track of the selection and make use of the on-value-changed as described in the following code. self.colorOptions = ko.observableArray([ { id: "blueopt", value: "blue", color: "Blue" }, { id: "greenopt", value: "green", color: "Green" }, { id: "redopt", value: "red", color: "Red" }, { id: "limeopt", value: "lime", color: "Lime" }, { id: "aquaopt", value: "aqua", color: "Aqua" }, ]); self.selectAll = ko.observableArray([]); self.currentColor = ko.observableArray(["red"]); self.selectAllOptionChanged = (event) => { const newSelection = event.detail.value; if (newSelection.indexOf('all')
Read more