AEM 6.5 xf page not self-refreshed after authoring is done - aem

AEM Version : 6.5.12
Problem
Where : at experience-fragment page
When : Authoring any component(insert/update/edit/delete)
What happens :
(1) POST xhr request sent from AEM editor is not getting any response.
(2) Editor Page is not changed automatically, but when I refresh it manually, authored contents are updated.
Note : This problem only occurs in Experience-fragment editor page(even with we.retail xf pages), NOT in sites editor.
I need help with this problem. thanks.
I think POST request is sent correctly to AEM server, because Authoring jobs are done. I guess response is not correctly sent back to browser, so editor callback function is not fired.

I solved this problem myself.
What I checked :
AEM > Tools > Operations > Health Reports > Asynchronous Indexes
It was "Critical" Status, with this message "The 'async' indexing lane is failing."
At crx/de, under "oak:index" node, there was 3 nodes had "corrupt" property.
I reindexed those nodes -> corrupt property removed
AEM > Tools > Operations > Health Reports > Asynchronous Indexes Status became "OK" and problem solved.

Related

Error while opening extended Fiori app

I have extended Manage journal Entries app in Web Ide. Haven't added any extra code. Just saved it and run to check whether the app is opening as expected or not. But I am facing error " Could not open app, Please try again later".
Come across few threads regarding similar issue but my issue is not while launching, It is when extending manage journal entries app.
Fiori : Could not open App
Pre Requisite which I have checked:
SICF Service is Active.
component UIS4HOP1 200 SP 0000 is installed in my FrontEnd Server.
Thanks,
Srilaxmi
From the error message in the commments section it seems like you have problems with the namespace of the component. Did you check that the path and the namespace for your extension project matches the deployed app? This can very easily mess up the component loading mechanism in FLP and lead to the described result...

Error with Orbeon Forms

We have an older application based on Orbeon forms 4.4. Out of the blue, we started having a problem where various links and buttons on certain forms are not functioning correctly. The forms impacted seem to be Orbeon's built-in Forms Builder and a few of our forms that use the Orbeon "Wizard" view...the initial page displays properly, but navigation from one section to another seems to be broken.
The only unusual thing we see in the log files is this message:
WARN XmlLibraryChecker - Looking for a valid Parser...
Checking for Xerces, found version Xerces-J 2.11.0 needed version Xerces-J 2.9.0
Warning: Failed find a valid Parser!
Please add an appropriate Parser to the class-path, e.g. in the 'endorsed' folder of the servlet container or in the 'endorsed' folder of the JRE.
In the Orbeon webapps/orbeon/WEB-INF/lib directory, we see a xerces-2.11-orbeon.jar all of the JAR files in this directory are dated November 2013 and have not been changed best we can tell. I understand this is a "Warn" message, but there doesn't seem to be any other sign of problem.
In the case of Form Builder, we go to the listing of all the current forms, and are unable to page through the list. When we click on the paging control at the bottom of the page, we see an HTTP request to "xforms-server" from "connection.js:467". The data sent on this request is:
<!DOCTYPE xxf:event-request [<!ENTITY nbsp " ">]>
<xxf:event-request xmlns:xxf="http://orbeon.org/oxf/xml/xforms">
<xxf:uuid>a3a297feb1356b5190ce1050fdc165bfadae85e3</xxf:uuid>
<xxf:sequence>2</xxf:sequence>
<xxf:action>
<xxf:event name="DOMActivate" source-control-id="xf-432"></xxf:event>
</xxf:action>
</xxf:event-request>
This seems to work (HTTP response code 200) and we seem to get a response that has the next page worth of values in a long XML format. The display at the browser is unchanged however...the list of displayed items in Form Builder doesn't move or change in any way.
The pattern in our "Wizard View" forms is similar...we see the same HTTP transaction sent to the server, get a similar XML response, but no display update occurs.
Clients are Chrome 58 and 60, plus Safari 10.1.2.
Server side is Tomcat 7 with Java 1.7.051 and MySQL as the persistence layer.

Magento 2.1 internal server error for specific category when full page cache enable

I had FPC (full page cache) enabled
There is one category containing subcategories and 900+ products. it was working fine but suddenly it started pushing 500 internal server error.
i have not add any new product or any major change. so now when i disable the FPC, the category start working and when i re enable FPC, again internal server error 500.
i have already applied couple of solutions but no success.
tried with removing cache at all, re indexing, crons, have check the htaccess also all things are fine, i had try with creating new category but when i assigned the same block to load on that category, again same issue started.
log is saying that
The problem is in the function getIdentities()
can anyone help with this? thanks in advance.
i resolved this issue.
Here is the solution:
When we will have a bulk products in a category we can either enable Varnish cache or Full page cache. we cannot enable both simultaneously, otherwise it will through internal server error if both caches will be enabled.

Page is not loading properly with editor.html in the url AEM6.1

My page is not loading properly with the url having "editor.html" (http://localhost:4502/editor.html/content/mypage.html). But when I remove editor.html, it loads perfectly (http://localhost:4502/content/mypage.html).
I am using AEM6.1. If I open the page in classic UI, its looks good. But when I open it in touch UI, its not loading properly.
I already have a property "sling:resourceSuperType = wcm/foundation/components/page"
Some of the content is coming on the page.
It can be a JS issue, but even if I remove all the js files from my component, the issue is still there.
Anyone experienced the same issue?
This issue might be due to the 'Apache Sling Main Servlet' default configuration.
And also we can observe the error message 'components could not be loaded' or 'out of memory' in browser console when we are in Touch UI editor Mode.
By default 'Apache Sling Main Servlet' is configured with 1000 calls per request. If we increase this limit then the issue will be resolved.
For updating this follow the steps.
1. Go to the http://<host>:<port-number>/system/console/configMgr (ex: http://localhost:4502/system/console/configMgr)
2. Ctrl + F and Search for "Apache Sling Main Servlet".
3. Change the value of 'Number of Calls per Request' from 1000 (defaulut value) to 1500 or 2000.
4. Click on Save.
5. Now you can go to Touch UI edit mode and can be able to edit the components.
Check in your CRXDE under the folder /libs/wcm/core/content and look for a folder called "editor.html" with the sibling of just "editor". If you delete the editor.html folder and keep "editor", then your page will start working again.

Persistently Filtering Out Application Traffic in Fiddler

Whenever I start Fiddler, I see traffic from all of the applications on my system but it's very rarely the case that I want this. Usually what I want is to only see requests made by applications I am debugging. In order to achieve this, I leave Fiddler running all the time and whenever I want to see what happened with a request I can just open it up and see.
I can filter requests by right-clicking on an entry -> Filter -> Hide '<application name>'. Although this works fine, it is cleared when Fiddler is restarted.
How can I persist filters that filter out traffic from a certain application?
I tried using the Filters tab but this is very limited and one of the missing features is what I detailed above.
This can be achieved by creating custom rules. In order to do this, in Fiddler, go to Rules -> Customize Rules. You can choose Yes to install the FiddlerScript Editor plugin if you want but this is not necessary. Just click No when asked and a file named CustomRules.js will be opened using Notepad.
This file allows you to program all sorts of rules into Fiddler, from adding headers to outgoing requests to monitoring the time taken for a response to be received. Further details on it can be found here.
In order to filter out a certain application, scroll down to the OnBeforeRequest method and paste the following code in:
if (oSession["X-PROCESSINFO"] && (
oSession["X-PROCESSINFO"].StartsWith("firefox") ||
oSession["X-PROCESSINFO"].StartsWith("outlook") ||
false))
{
oSession["ui-hide"] = "FiddlerScript> Hiding unimportant process";
}
This piece of code tells Fiddler to hide all requests coming from Mozilla Firefox or Microsoft Outlook. If you want to add / update / delete any application here, all you need to do is copy / update / delete lines that contain the StartsWith method.
The first condition will filter out all the requests that do not come from an application. This is the case for requests made from Fiddler's Composer tab.