Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1054173

Summary: Error This portlet does not exist anymore when importing site
Product: [JBoss] JBoss Enterprise Portal Platform 6 Reporter: mgottval <mgottval>
Component: PortalAssignee: Nick Scavelli <nscavell>
Status: CLOSED WONTFIX QA Contact: Dominik Pospisil <dpospisi>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1.1CC: bdawidow, dingham, epp-bugs, mvecera, tkyjovsk
Target Milestone: CR01   
Target Release: 6.1.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-22 14:17:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
error none

Description mgottval 2014-01-16 11:54:27 UTC 
Description of problem:
When new page is created in Page Management portlet and then added into new site, which is exported and then imported again, there are errors "This portlet does not exist any more, please refresh your browser". After refreshing everything is ok. This doesn't happen every time.

Steps to Reproduce:
1.Group - Administration - Page Management - Add new page - page is created in portal classic, layout e.g. Two rows layout. Save and edit this page also in Page Management - add some applications.
2.Site - Manage Sites - Add new portal - Save. In Edit Navigation add some node and select the page created before.
3.In Site, go to this new site
4.Group - Administration - Site redirect and import export - export new site, then delete this site and import again.

When click on this imported site in Site menu, there are errors "This portlet does not exist any more, please refresh your browser".
Comment 2 Boleslaw Dawidowicz 2014-01-22 14:17:37 UTC 
This is expected behavior atm. Portal used to throw exceptions in the log.
Comment 3 mgottval 2014-01-23 15:31:49 UTC 
Created attachment 854447 [details]
error
Comment 4 mgottval 2014-01-23 15:33:45 UTC 
But it appears in the portal page, not the log, for the first time after importing the site. Basically when I click Import button and wait the dialog to close itself.
Comment 5 Nick Scavelli 2014-01-23 17:26:22 UTC 
Yes, what used to happen is you would get stale data or a bad exception would be thrown. Only way to see the new data, or get rid of the exception was to log out. Now the user only has to refresh the browser. If our error pages were a little nicer it wouldn't look as ugly as your screenshot. But it does allow us to import data while the portal is running and the user just has to refresh the page to see new content.