Hybris backoffice not loading in Dev Environment - sap-commerce-cloud

We moved hybris 5.2 to 5.6 version for our customer. Now We were not able to access back office site in Dev environment I am getting CMS site not found Error. but hmc and other cockpits are loading fine. I am bale to load back office in my local initially it was not loading due to 2 attributes newly added by hybris in AttributeDescriptor items after adding those attributes it was working fine in local and i did the same changes in dev but still in dev environment i am getting CMS site not found error .. can any one help me on this.?

Have you added the backoffice extension to your hybris/config/localextensions.xml ?
If you didn't (maybe due to updating), make sure to add it by adding a new line:
<extension name="backoffice"/>
Anyways like Tennyson mentioned, this isn't really a programming related question.

Add <extension name="platformbackoffice" /> too to your config/localextensions.xml
or, if the above solution does not work try below one.
Open up orchestrator mode (F4 in BackOffice), then click on the [y] logo in the upper-right corner and choose "Reset everything". The issue was resolved after doing this for 2-3 times.

Related

Liferay7 - module (portlet-provider) not refreshing

Im working with Liferay 7 and module development.
I created a module of type "portlet-provider" for can change the view of personalBar.
When I deploy it first time, it deploys ok, but after that, new deploys are not refreshing jsp files.
Is important to said that when I deploy the module, via blade or via gradle in Intellij, it deploys ok and also change the OSGI related folder, deleting old version and creating a new one with new jsp ok.
Even with that in a clear browser (recent removed all cache and temp) does no not refresh the personalBar view, related to new jsp file.
I saw this thread: https://web.liferay.com/community/forums/-/message_boards/message/88515142 , and tested the following.
1) Changed the tomcat timeZone, put the same timezone that I had in my desktop. (GMT-3 ) , it didn't work .
2) The only thing that seems to work is to clear all osgi state content and $liferay_home/work content and restart server as David said in above post.
But I need a way to can deploy theses modules without having to restart the server
Any help on this?
Thanks in advance
About my problem, I had a problem with the priority of the module so the module been deployed were not the same showed in portal.
At the beginning I set the "service.ranking:Integer="+Integer.MAX_VALUE , but I don't know why it was removed and for that the portlet showed was the portal default personal bar.

Orchard CMS: Where new theme structure and files get saved when installed from Gallery

I have a couple of general questions please. Just stepping into Orchard CMS. So apology if they look stupid!
Today I installed a theme called Metro from Theme Gallery. It is visible on theme selection page as well. But where the files and folder structure are got saved in Orchard CMS? I looked into Theme folder but it is not there. I want to see how the structure is placed so that I can create one myself
One more thing. Theme .png file shows a nice layout but when I activate it the layout comes up completely different. Why is this?
And finally, I installed my site using Orchard's web interface and it is running fine. But when I tried to run orchard > codegen theme CreditLine, it said Command codegen doesn't exist.
I then run Setup utility from command prompt (orchard >) and it displayed
A previous Orchard installation was detected in this database with this table prefix.
Which clearly says the setup I did through web interface was successful. But still I am not able to run codegen command or even help codegen. The latter command shows Command codegen doesn't exist!
Orchard version: v.1.10.1.0
1) It should be installed under Themes/TheThemeName, or locally, under src/Orchard.Web/Themes/TheThemeName
2) It could be that you installed an old theme. Not sure because you don't give many details over what goes wrong.
3) You first have to enable the codegen module. Do this by starting up your Orchard, go to modules => Codegen => Enable. Or run in the orchard.exe: feature enable Orchard.CodeGeneration
After a lot of Googling and struggle I found a nice community here where I got my answer!
Orchard Repository on Github defaults to dev branch which I overlooked completely when cloned it for the first time! So I removed everything from my local and cloned the source again but from master branch this time.
No more compilation error or Command Line issue popped up. Orchard.CodeGeneration feature got enabled from CLI this time without a problem. Everything else seems to be working fine as well.
Steps:
1. Removed source from my local which I cloned from dev branch initialy
2. Cloned Orchard from master branch
3. Opened solution in VS2015
4. Compiled, run and setup my first site
5. And finally ran feature enable Orchard.CodeGeneration from orchard command prompt.

Liferay not working on WebLogic Server

Very general question here:
I have Liferay 6.1.1 ga2 set up on my Oracle WebLogic 12c.
It works fine on my local, but when I deploy it onto our development server, I lose all write permissions.
E.g., changing the theme/color scheme, creating web content, pages, and saving changes to most things
I try to import LARs however it is saying it is not permitted
I'm not seeing any errors in the logs, and the control panel messages are even telling me my content was created or change successfully (besides the LARs0, but everything stays the same.
Any reason(s) why my changes aren't showing up? I'll surely give a bounty if I can get pointed in the right direction here
Given your description, I'd recommend checking OS issues, like write access to various folders, like temporary folders etc.. I guess that Liferay has proper permissions to the whole database (it's rare to have incomplete access) and can write to all tables. And you're operating on a portal-wide admin account, right?
Unrelated to LAR import, changes will not show up if you have workflow enabled - then you'd find the changes in the list of tasks that need approval.
As staging has quite an obvious UI in 6.1, I assume you don't have staging activated, otherwise you just need to publish. In order to see new portlets, make sure that the "Edit Controls" checkbox in your dockbar is checked. This has bitten me more than once.
if you're running a cluster, make sure that you have set it up correctly, e.g. that you don't see cached content on your node.
Can you confirm that you can see the options to change on the UI, just that your changes aren't persisted?
Also, please note that Weblogic 12c is not on the "supported Appservers" list for Liferay 6.1, it's there for Liferay 6.2 only (probably due to release date). This doesn't mean that it shouldn't run, just that it's not tested for your version. Further, there's a GA3 release for 6.3 already, so you might want to check if it's a problem that's fixed in GA3.

Unable to view deployed Liferay portlet in the add >> more option

I have created a sample Liferay portlet and it has successfully deployed. But, the eclipse console didn't say "1 portlet is ready for use". And, I couldn't find this portlet in the Add >> More.. option on a Liferay page.
As Mark mentioned, it is undeterministic and it sometimes happen. I usually follow the following steps and after this it works normally.
Steps:
remove all the references of the portlet from webapps.
stop the server
deploy the portlet's WAR
restart the server
check the logs if the portlet is deployed.
If possible try to build the WAR again and deploy the new WAR, and follow the previous steps.
Also if this doesn't work try to clear the temp and work directory and again try the previous steps.
Hope this helps.
I have been fighting with this problem for a day. For me it was two things: wrong property of
liferay.home
inside
portal-setup-wizard.properties
Only after correction I was able too see in tomcat logs that my liferay-plugins had higher version than liferay itself. I redownload plugins with correct version and new plugin deployed correctly.
If you've done all the cleaning etc. and it still does not work, there may be another reason for not showing. If you have - for some reson - deactivated the portlet in Liferay, it will remember the setting even though you have undeployed it several times.
So, you must go to Control Panel > App Manager > All Apps > Your portlet name and activate it again!
That is undeterministc but usual error. Try to undeploy the portlet - delete portlet directory under tomcat/webapps and try to deploy again.

Internal system error when opening Lotus Notes XPages database

I have downloaded sample XPages database http://www.jmackey.net/groupwareinc/johnblog/johnblog.nsf/d6plinks/SurveyToolSample
and deployed it to server. I can open it without problem with my Lotus Notes 8.5.3, but my colleague cannot open it on his Lotus Notes 8.5.2 Standard Configuration.
He gets the following error:
**This Page Cannot Be Displayed**
Internal system error when processing the request for the page ( http://127.0.0.1/xsp/JHGNES!!Major %5CSurvey.nsf/HomePage.xsp?OpenXPage&xspRunningContext=Notes ).
Please retry this request.
Enforced by host JHGMELWEB01
If this condition persists, please contact your corporate network administrator and provide the code shown below.
Notification codes: (1, INTERNAL_ERROR, http://127.0.0.1/xsp/JHGNES!!Major %5CSurvey.nsf/HomePage.xsp?OpenXPage&xspRunningContext=Notes)
I have Recompiled all lotusScript in the database using my 8.5.3 client.
Any ideas what can be the problem?
Recompiling all Lotusscript does not re-compile XPages.
Try doing a clean of the project by opening the database in Domino Designer and then use Project - Clean in the menu. Clean removes all built code and then re-builds the code.
In your 853 Designer, try recompiling the app to support 852 as the minimum release?
Launch the Application Properties in Designer, go to the XPages tab, then under 'Minimum Supported Release' select to compile this application to run on 'Release 8.5.2'.
For the vast majority of cases, apps built or compiles on current releases will work fine on previous releases without needing to do this step. Though in some cases, changes in the new release, like a new property for example, may cause failures in previous releases. This is what I'm guessing what is happening in your case.
Thanks for your quick responses. I have done more testing after I tried suggested solutions and it seems like the problem is not in the database itself but in this colleague's PC configuration, as it works on 5 other PCs running 8.5.2 and 8.5.2FP2.
Actually when you change "Minimum supported Release" on the xpages tab of app properties it prompts you to rebuild all the code.
The problem was in the location settings of that particular machine. After we removed contents of "Proxy configuration" it worked like a charm.

Resources